• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

A NeoGAF iPhone Web App

Status
Not open for further replies.
This should be part of the web app.

It is part of the web app, in that neogaf.com links get changed to secondapps.com links when you click on them.

You were asking about links from outside the site though, like from Google searches. Obviously the web app has no reference to those, but a simple Android app should be able to convert them. Dunno about iOS.
 
I don't know if this has been discussed before, but is the only way to have badge notifications is if the webapp went to the iTunes store. I would love to get notifications when I get PM's ect.
 
All I want really is the ability to direct link specific replies to other people.

Icing on the cake would be any neogaf links from outside of the webapp linking to the webapp instead of the real deal and vice versa. Meaning, all links are the same, it just loads differently depending on if I'm on a pc or on iOS.
Yes! This would be killer.
Guys.. this is already in place. It was added in the last update I think. All you do is tap on the "post xx" link in someones reply bar, and it takes you to that single post. Then you just copy that link..

When everything is done and merge, with GAF redirecting to the mobile version, the same will work vice versa, I imagine. Test it out, it works fine.

I don't know if this has been discussed before, but is the only way to have badge notifications is if the webapp went to the iTunes store. I would love to get notifications when I get PM's ect.
Yeah, I don't think there's any way this could happen. But ckohler, would the only way to know if we have a new PM be to check the front page? I would like a little badge on the drop down options PM icon.
 
It is part of the web app, in that neogaf.com links get changed to secondapps.com links when you click on them.

You were asking about links from outside the site though, like from Google searches. Obviously the web app has no reference to those, but a simple Android app should be able to convert them. Dunno about iOS.

That's something that has to be handled on gaf's server, which will probably be implemented since evilore and ckohler are working together.
 
That's something that has to be handled on gaf's server, which will probably be implemented since evilore and ckohler are working together.

That has nothing to do with converting links, though. That would just be a redirect based on user agent, and of course they'll do that when the app becomes official. It's not like we have to ask for that.

But as for redirects in the app's current state, the only way to do it is to have a third party app that detects neogaf.com links, converts it to secondapps.com, and sends it to the browser.
 
That has nothing to do with converting links, though. That would just be a redirect based on user agent, and of course they'll do that when the app becomes official. It's not like we have to ask for that.

But as for redirects in the app's current state, the only way to do it is to have a third party app that detects neogaf.com links, converts it to secondapps.com, and sends it to the browser.
I'm not understanding the need for an native app to do that.
 
That has nothing to do with converting links, though. That would just be a redirect based on user agent, and of course they'll do that when the app becomes official. It's not like we have to ask for that.

But as for redirects in the app's current state, the only way to do it is to have a third party app that detects neogaf.com links, converts it to secondapps.com, and sends it to the browser.
Already does this on the non-mockup version. example (redirects): http://secondapps.com/neogaf/showpost.php?p=35668436

It just hasn't been implemented into the mockup site yet.
 
I have a feeling this will be an unpopular opinion, and I'm not even sure I'm sold on it myself, but has there been any interest in a floating footer with page navigation buttons, similar to that on the Rootzwiki mobile formatted site? Basically it has page navigation buttons always visible on the bottom of the page but they don't take up screen space, they just float over posts. Could also have return to top button for us non-iOS users.
 
I have a feeling this will be an unpopular opinion, and I'm not even sure I'm sold on it myself, but has there been any interest in a floating footer with page navigation buttons, similar to that on the Rootzwiki mobile formatted site? Basically it has page navigation buttons always visible on the bottom of the page but they don't take up screen space, they just float over posts. Could also have return to top button for us non-iOS users.

Not a fan of floating elements.
 
I have a feeling this will be an unpopular opinion, and I'm not even sure I'm sold on it myself, but has there been any interest in a floating footer with page navigation buttons, similar to that on the Rootzwiki mobile formatted site? Basically it has page navigation buttons always visible on the bottom of the page but they don't take up screen space, they just float over posts. Could also have return to top button for us non-iOS users.
It was discussed a while back, but I think it'd be a waste of pixel space tbh. Also, from what ckohler said earlier, it seems like it could be finicky across different mobile browsers, so not really worth it in general.
 
Mockup has been updated. Please clear cookies/cache before reporting problems.

Changes
  • Searching enabled
  • Member profiles enabled
  • Pagination buttons redone
  • Other minor fixes/changes I can't remember

To Do
  • Compose Threads/Posts
  • Private Messages
  • Subscribe to Threads and view Thread top posters
 
Mockup has been updated. Please clear cookies/cache before reporting problems.

[*]Pagination buttons redone
Very, very nice. I like how it's inline now, and with the drop down last/prev. page buttons. The best part is the numerical keyboard popping up instead of the standard one, saves a lot of time and errors.

Oh and searching is great, keeping a tab open for adv. search so I can view my response like a twitter feed. :lol Good stuff!

[edit] Oh wait, when I click on a search result, it doesn't take me to where the searched query was located or highlight it like prime does. Am I doing something wrong?
 
Very, very nice. I like how it's inline now, and with the drop down last/prev. page buttons. The best part is the numerical keyboard popping up instead of the standard one, saves a lot of time and errors.

Oh and searching is great, keeping a tab open for adv. search so I can view my response like a twitter feed. :lol Good stuff!

[edit] Oh wait, when I click on a search result, it doesn't take me to where the searched query was located or highlight it like prime does. Am I doing something wrong?
Just getting the normal qwerty keyboard on Android.

I really like the new page controls though. One tiny nitpick would be that pressing the 'Go to Page' button expands the current page number and total page number just off the bottom of the screen. Could the extra controls expand over the advert, like the quick jump menu in the page header? That would stop the length of the page increasing so you could see the numbers without having to do an extra scroll down.

Also noticed that the subscribed threads list is now working. Been waiting for this. Yay!
 
I really like the new page controls though. One tiny nitpick would be that pressing the 'Go to Page' button expands the current page number and total page number just off the bottom of the screen. Could the extra controls expand over the advert, like the quick jump menu in the page header? That would stop the length of the page increasing so you could see the numbers without having to do an extra scroll down.
I don't even think we know for sure if tapping on the more options button up top is supposed to hide the ad?

Not sure if that's how it'll actually be in the final version or not, i'd like evilore to chime in on that bit. But yeah, if the top gets hidden, so should the bottom.

PS. I never use the subscriptions feature, but I just might start using it as a mobile-only type of helper. Cool. :D
 
Hiding the top ad when the menu was open was deliberate. It doesn't have to be that way but it looked nicer and it shouldn't impact the impressions negatively since the ad always appears anyway. If it's an issue, Evilore can tell me to change it prior to when it goes live. No biggie.
 
Probably shouldn't be hidden when the menu is open, just asking to be a ToS violation for some company.
 
  • Searching enabled
  • Member profiles enabled
  • Pagination buttons redone
  • Other minor fixes/changes I can't remember

Searching is awesome, easy to access and seems to work great. Member profiles are also pretty rad.

The new pagination stuff seems slower to me than the previous; it was easier to just tap and get an alert box. I like the big next/previous buttons, though.

  • Subscribe to Threads and view Thread top posters

There are some per-thread and per-post options it'd be nice to enable for mods, if such a thing is possible. :D
 
Definitely agree, but you could argue that the menu 'pops up' over the ad temporarily when engaged.
I guess it'd be better to play it safe. Especially when hiding it really doesn't make a huge difference, since you wouldn't really care about pixel space at that point since you'll be navigating elsewhere.

There are some per-thread and per-post options it'd be nice to enable for mods, if such a thing is possible. :D
I'm just waiting for an error to be made giving everyone running mobileGAF access to these options. :p
impossible i know i know
 
Mockup has been updated. Please clear cookies/cache before reporting problems.

Changes
  • Searching enabled
  • Member profiles enabled
  • Pagination buttons redone
  • Other minor fixes/changes I can't remember

To Do
  • Compose Threads/Posts
  • Private Messages
  • Subscribe to Threads and view Thread top posters
Nice little update... Jump to page now works on Windows Phone. :D
 
The new pagination stuff seems slower to me than the previous; it was easier to just tap and get an alert box. I like the big next/previous buttons, though.
I switched away from using the alert box because some browsers (IE9 on WP7) don't support Javascript Prompt() for security reasons. The input box solves that. The side benefit is that I can now use the numeric only keyboard for some (not all) devices. But yes, it is one additional click.

There are some per-thread and per-post options it'd be nice to enable for mods, if such a thing is possible. :D
I assume it's possible but let's table that for now. I can't add those features now anyway because I can't even see them.
 
I switched away from using the alert box because some browsers (IE9 on WP7) don't support Javascript Prompt() for security reasons. The input box solves that. The side benefit is that I can now use the numeric only keyboard for some (not all) devices. But yes, it is one additional click.

Ah, that makes sense. Who should get a numeric-only keyboard if the feature is working correctly? I didn't, but I'm using Swype -- should it work with the Android stock keyboard, or only on iOS?
 
Been using the mockup to read threads while using the original version to post.

I'm very impressed with the progress of the mockup and get depressed when I have to use the original to post in threads. :lol

Can't wait to see what the next update will bring as the mockup just keeps getting better.
 
I switched away from using the alert box because some browsers (IE9 on WP7) don't support Javascript Prompt() for security reasons. The input box solves that. The side benefit is that I can now use the numeric only keyboard for some (not all) devices. But yes, it is one additional click.

As a Windows Phone user, I find it really awesome how you try to cover all platforms. Thank you.
 
Ah, that makes sense. Who should get a numeric-only keyboard if the feature is working correctly? I didn't, but I'm using Swype -- should it work with the Android stock keyboard, or only on iOS?
It was just giving me the normal keyboard before on Android, but ckohler seems to have fixed it. I think it should work with any keyboard that has a numeric input mode, Swiftkey and stock ICS both work.
 
It was just giving me the normal keyboard before on Android, but ckohler seems to have fixed it. I think it should work with any keyboard that has a numeric input mode, Swiftkey and stock ICS both work.

Still no dice. I guess Swype doesn't support that feature. Oh well!
 
the latest mockup is looking awesome ckohler :D

Can I make a small suggestion? When viewing on tablets and clicking the menu button, is it possible to have the icons all on one line? If the buttons are simply an unordered list is should be easy to have them dynamically adjust according to screen size.

No biggy either way, I know you've got more important aspects to cover anyway :)
 
How do you contribute?

Dreweyes designed like fifty awesome NeoGAF t-shirts, Timan co-designed and coded the current NeoGAF.com layout, and ckohler is obviously creating NeoGAF Mobile. Just some special additional recognition for people important to the site.
 
Btw Chris, contributors to the site get a special image tag of their choice, as with Dreweyes and Timan, so feel free to design something 100x30 to wear ;b
Thanks! I'll give it some thought and let you know if I come up with something.

Btw, this was posted using the new version. I'm going to test it some more before making a part of the working mockup. Next I'm going to add multi-quote.
 
Thanks! I'll give it some thought and let you know if I come up with something.

Btw, this was posted using the new version. I'm going to test it some more before making a part of the working mockup. Next I'm going to add multi-quote.
4k2Ja.gif

& congrats on the pic tag!
 
Two things:

One:
I've got multi-quote to work however it's behavior will have to be a little different from the main website. The reason is that mobile browsers pretty much keep the same session open all the time, so the cookie never expires. Also, it's harder for me to detect what quotes belog to what threads using screen scraping. So, to keep it simple and put the logic on vBulletin, here's how I suggest to make it work:

You'll be able to multi-quote within-in the same thread only. No cross thread multi-quoting. Once you press the compose button, your multi-quotes will appear in the message body. Once you submit a post (same thread or not), your prior multi-quote selections are cleared. Also, your multi-quote selections will automatically expire after 24 hours.

Thoughts?

Second:
I have a design decision to make. Space is already tight in those grey bars above each post. To put both a "Quote this post" button and a "Multi-quote this post" button will be tricky. It can be done but here are the various options:

  1. Have only one button for each post that only marks for multi-quoting. You then have to click the Compose button at the bottom.
  2. Have only one button that when clicked prompts if you want to either select that post for multi-quote or quote and compose immediately
  3. Try stuffing two separate buttons in that bar, one for immediate quoting and another for multi-quote marking.

Thoughts?
 
Would it be possible to have another setting field to "enable" multiquote? Then just leave the single quote button in the postbit if its off/default.
 
Two things:

One:
I've got multi-quote to work however it's behavior will have to be a little different from the main website. The reason is that mobile browsers pretty much keep the same session open all the time, so the cookie never expires. Also, it's harder for me to detect what quotes belog to what threads using screen scraping. So, to keep it simple and put the logic on vBulletin, here's how I suggest to make it work:

You'll be able to multi-quote within-in the same thread only. No cross thread multi-quoting. Once you press the compose button, your multi-quotes will appear in the message body. Once you submit a post (same thread or not), your prior multi-quote selections are cleared. Also, your multi-quote selections will automatically expire after 24 hours.

Thoughts?

Couldn't HTML5 local storage help here? User wants to quote a post, that post gets saved to local storage (it's a simple key/value pair), then when user hits reply the quotes get cleared from LS into the text edit field. It's supported by every browser, too (even IE above v8).
 
Status
Not open for further replies.
Top Bottom