|
Maybe I'm in the minority but it seems like tying the action Back to the Back Button would be most intuitive. I'm sure if it isn't, I'd be exiting the app every time I finished a thread. I like the way the xda app handles forum navigation, have you looked at the way it does it? Basically it works like any tapatalk client does, but the gist of it is that: -Replies are done by a menu option within a thread -Quotes are done by long-pressing a post (I don't believe there's multiquote functionality) -Next page is at the bottom of a thread, kind of as though it's the last post -Back to thread list is done with the menu option ("Exit thread"), but you can also use the Back button to work back to it.
|
| # ¿ Feb 20, 2011 19:58 |
|
|
| # ¿ May 24, 2013 01:16 |
|
Ferg posted:The backbutton won't exit you out of the app if you've opened other activities while using it. Currently the way navigation is working is it fires off another request for a thread's posts, and then repopulates the list. What it could do is re-launch the same activity which would mean that hitting the back button would pop the current activity (say the one showing page 2) and it would bring the previous activity (the one showing page 1) back up. So basically Back once refreshes then Back again takes you back to the last thing you did (either to the thread listing or the previous page in a thread)? Sounds pretty good, though I don't know that the refresh would be necessary although it does free up a menu spot.
|
| # ¿ Feb 20, 2011 20:18 |
|
clamiam45 posted:If you're adding them as features as well, you may want to also hide the other post-specific links (Profile, Message, Post History, Rap Sheet, Report) under a long press along with Quote.
|
| # ¿ Feb 20, 2011 23:34 |
|
PlaneGuy posted:On touchscreens, I don't use the quick nav... my fat sausage fingers can't handle it.
|
| # ¿ Feb 21, 2011 18:43 |
|
1997 posted:I'm no graphic designer, but I made an icon with everyone's favorite emoticon:
|
| # ¿ Feb 21, 2011 20:22 |
|
Vertigus posted:"SA Forums" might be a better name for the app, since the text under the icon wouldn't get cut off.
|
| # ¿ Feb 23, 2011 09:22 |
|
So much quoting to do:1997 posted:Karanth posted:Agreed on failure feedback, but putting up a "post in progress" notification is pretty nonstandard. Even the stock gmail app just puts up a "sending" toast and that feels like a little much. ![]() brosmike posted:I love me some quickactions Long-pressing on the post is a much better place for Quote. Mainly because on a small screen posts are going to look long, usually longer than the screen. It's going to suck to have to scroll back to the top of the post to quote it. Long-press on the post should bring up Quote, Mark Read to Here, and if Ferg is feeling froggy, maybe Share Post that could do the usual thing were it puts the thread at that post (the # button) on the clipboard and opens the usual app (GMail, Talk, etc). I know I do a lot of sharing of threads with people and it's very common to link to a great post in a thread and this would be convenient and easy. BluDiE posted:
|
| # ¿ Feb 24, 2011 00:43 |
|
big mean giraffe posted:Alright well pretend this frog is a well-done frog with his mouth open: If it's set to automatically login, make a "Loading" splash screen while it does so and if it's set to require a password make it throw a prompt over the splash.
|
| # ¿ Feb 24, 2011 08:02 |
|
brosmike posted:To clarify a bit on how login works: Although right now the app DOES store your username and password unmodified in an android-managed SharedPreferences ( Thanks for the clarification, I'm very interested in the nuts and bolts but know nothing about development.
|
| # ¿ Feb 24, 2011 09:06 |
|
Alright then gently caress if there has to be a login screen, make it the frog with his mouth open on the SA blue field. Make a white, rounded speech bubble coming out that says "Awful App". Below put the Username field and the Password field and a login button. When you enter the data and submit, if it's successful the frog changes to , if you enter the wrong data and it fails, change the text to
|
| # ¿ Feb 24, 2011 14:11 |
|
I Dont Like You posted:I'm really into that first one without the title as well.. drat. The one without the title owns owns owns.
|
| # ¿ Feb 24, 2011 22:33 |
|
Sunblood posted:The only feature I really *need* at the moment is Mark as Last Read on long-press. Everything else is just beautiful frosting on the most amazing cake. Fantastic work Ferg. Surprisingly full-featured for a 1.1 release.
|
| # ¿ Mar 5, 2011 17:43 |
|
Ferg posted:
After the last post (perhaps even in a different color), it should say "1/4, Click for next" or "4/4, End of thread". Anything to move that Next Page button. One change I'd like to propose: In the forums listing, the click area to expand the subforums should be small on the left (the area around the arrow indicating there is a dropdown) and the area to select that forum should be the rest of the bar (and there's no need for the blue arrow). This is how other Android apps that use the expanding tree model operate, i.e. the music player. It would also be nice to have a visual cue that you touched the correct forum/subforum. Right now you get a flash of color when you select the box to expand it, but when you select it, nothing visually happens to show what you picked. This is the opposite of how it should be.
|
| # ¿ Mar 10, 2011 09:55 |
|
JazzFlight posted:This is like in school when a teacher would tell you that you had to "show your work" on a math test. (Although I love reading changelogs--like more than a person should.
|
| # ¿ Mar 13, 2011 20:24 |
|
Karanth posted:Seconding this. The page indicator should be a footer view with next/prev buttons. The floating display is too much. Also, avatars still get moved around. I'll try clearing cache and seeing if that helps. Edit: No cache to clear so I cleared data; avatars still completely wrong most of the time. LastInLine fucked around with this message at Mar 20, 2011 around 05:53 |
| # ¿ Mar 20, 2011 05:48 |
|
Skeezy posted:How do I go about changing defaults on this thing?
|
| # ¿ Mar 21, 2011 06:57 |
|
Ferg posted:I hate it too. I'm going to swap the background image for the actionbar in the next release which will conserve a bit more screen real-estate and fix that ugly rear end fade.
|
| # ¿ Mar 23, 2011 07:11 |
|
big mean giraffe posted:I discussed this with Ferg a while ago and I don't remember why but he didn't like it and I ended up agreeing.
I struggle to think of any positives at all with the current placement of the next page button, although I'll concede that everyone uses their phone differently and I might not be thinking of how everyone would like it. I'm genuinely curious as to the reasoning behind its current placement as I've found it baffling from the beginning.
|
| # ¿ Mar 31, 2011 07:47 |
|
Iananan posted:the g1, some magics. it depends on the carrier as well as the manufacturer most of the time whether you'll get the updates.
|
| # ¿ Apr 3, 2011 15:28 |
|
deep square leg posted:This is an awesome app and I'll continue to use it regardless, but I do have one request: Would it be possible to make the whole "Page X of X" bar at the bottom also a button that goes to the next page? When using my left hand (while holding a bag or tram pole) it's difficult to reach the next page button at the top-right; I often press the new post button instead. Lowen SoDium posted:I kind of agree, except I would rather see it have a button on it, rather than the whole thing be a button.
|
| # ¿ Apr 13, 2011 07:35 |
|
hatersg2haet posted:Sad how this is better than the xda app. Reading threads is also much easier on the xda app with better UI, better handling of pictures, and better access to thread tools. You can do things like see the title of the thread you're in, the total number of posts in the thread, the page you're on and how many there are and all while consuming less real estate than the Awful app does. Granted the xda app is mature, has backend support, and doesn't have to deal with some hosed-with non-standard implementation of forum software so it's understandable it'd be better. I'm genuinely curious in what ways you feel it's inferior. The only advantage the Awful app has over the xda one is that it can browse these forums instead of those. I'm not trying to disparage Ferg and the others' work, so far I really like it and it seems to only be getting better all the time. I am just saying that there's still a ways to go before I'd call it "better than the xda app".
|
| # ¿ Apr 18, 2011 12:12 |
|
brosmike posted:Ferg has final say of course, but I really hate the idea of hard-coding certain forums in. What would people think about being able to bookmark forums in addition to just threads? Obviously the forum bookmarks would only exist within the Awful app, but it would mean people could C2P a link to the forum in question once, bookmark it, and then be able to access it even if it doesn't show up in the main listing the app parses.
|
| # ¿ Apr 23, 2011 21:22 |
|
Maker Of Shoes posted:I'm guessing that's a newer VBulletin feature.
|
| # ¿ Apr 23, 2011 23:45 |
|
Meander posted:The other thing is I haven't upgraded it to the 2.1 release of Android yet since I've had no reason to yet - would that make the Awful App downloadable for me?
|
| # ¿ Apr 28, 2011 12:01 |
|
Kazy posted:Just a suggestion: Can we get a dead zone or something on the auto-page load on forums? More often than not I find I'm stuck in a loading screen because I wanted to click a thread near the bottom of the page. Though I guess this is only a real issue on large-screen devices like my Nook Color that can display more threads at once. The dropdown for subforums needs to be all the way on the left, with the majority bar leading to the main forum.
|
| # ¿ May 10, 2011 11:01 |
|
Glimm posted:I'd kind of like to have arrows on the bottom footer for this similar to what the forums already does, << < > >> - although this will probably look too crowded.
|
| # ¿ May 11, 2011 08:54 |
|
Hadlock posted:Oh right, and having the display turn off where it's black gives you amazing contrast. I can't wait for cheap, super amoled 42" displays. Add to it the fact that it's susceptible to burn-in (now that we're used to cheap, high-quality LCDs) means that it's just not a good technology for larger displays.
|
| # ¿ May 26, 2011 08:08 |
|
brosmike posted:I always thought it was a neat idea, but a bit out of place - I couldn't think of a way to integrate it with the thread view that I liked (nothing I could think of solved the "requires ludicrous amounts of scrolling anytime you'd use it" issue), and I didn't like that the forum and thread views acted differently.
|
| # ¿ Jun 4, 2011 13:29 |
|
brosmike posted:Although I agree with this, it has nothing to do with what you quoted.We were talking about how the current market build's forum view does an endless scrolling technique like the market instead of pages like the thread view.
|
| # ¿ Jun 4, 2011 14:18 |
|
Geekner posted:That was me, actually.
|
| # ¿ Jun 6, 2011 16:17 |
|
crazysim posted:This is quite a hellquote but I gutted the original always focus marquee hack that I did in response to Ferg's post and made it possible to scroll the TextView horizontally by touch. I guess this will probably spark off another few posts discussing the merits and demerits of this but I like the manual method more because it is not as distracting and you can go back and forth on your own accord so this works for me.
|
| # ¿ Jun 11, 2011 10:29 |
|
In the thread view, the Menu was never changed to 2x3. Aside from that this is great.
|
| # ¿ Jun 14, 2011 19:50 |
|
Dumb thing that doesn't matter (that only Ferg can fix): In the Market on the phone, the picture is the app icon in a huge white field rather than something that looks nice.
|
| # ¿ Jun 17, 2011 08:32 |
|
Archduke posted:Pretty self-explanatory, if crude. Underneath the page number, there'd be a page 1, previous, next, last page navigation bar. I also think that tapping on the page # should open up the ``jump to'' box. It wouldn't be too hard to implement, I'd imagine, and it'd make it a bit easier to use, in my opinion. This is something I've wanted since the advent of the app but now I'd be against it for two reasons. One, this isn't xda and I seldom if ever need to refer to the OP; likewise I seldom want to jump to the last page (although I sometimes do). Two, in portrait mode space for the Next Page button is already tight, making the user aim around a second button would complicate things. The compromise I'd offer would be to leave the footer as it is (I love it so much) except make the middle "Page x/y" do as you describe and call up the page selector. Then drop both Previous Page and the Page Selector from the menu. In the times you want to go to the OP or last page you can use the page selector.
|
| # ¿ Jun 19, 2011 11:51 |
|
Shanakin posted:I kind of agree here, but what if you just made the forward/back buttons and then had a longpress for start/end on the appropriate button? I'm not sure if the standard button UI element supports longpress though. What about you hit the "Page x/y" part to bring up the page selector, but the page selector dialog has both << and >> buttons along with the number field? Still a two-press solution, not as crowded in the UI.
|
| # ¿ Jun 19, 2011 17:10 |
|
I tend to agree with the others: I'm happy regardless of what order things happen but thread features (highlighting, UI improvements, SALR features) would help more in the day-to-day than PMs in my use case.
|
| # ¿ Jun 24, 2011 20:04 |
|
Geekner posted:Pretty sure it's running out of memory in those cases, but I haven't really looked into it. I remember seeing a few out-of-memory errors when browsing really image-heavy threads. Is there any way to have the app build a cache that won't grow to an obscene size but not have low memory devices show almost no images?
|
| # ¿ Jul 7, 2011 07:57 |
|
Fuzz posted:I'm on a Thunderbolt running BAMF 1.6 or so, and my issue is that a good 80% of the time when posting, if I try to click around within my text to, say to fix a word swype hosed up on, it will instead jump up about 5-7 lines. It's consistent and will do this for the rest of that post attempt, and I have to use the hold-zoom dealy to place my cursor. Right now as I write this it's okay, but the last 3 posts were having the issue. loving annoying. Love the app otherwise, it's the bee's knees. And yes I'm on the latest beta of swype.
|
| # ¿ Jul 24, 2011 15:09 |
|
I like the concept but I'd have to see it in practice before I could say how intuitive and usable it is. Is there a list of feature requests where we can upvote/downvote things? I think it'd be neat to see everything we've got, everything we'd like, and what the developers think is doable.
|
| # ¿ Aug 24, 2011 07:06 |
|
|
| # ¿ May 24, 2013 01:16 |
|
We really need to get a list of feature requests along with developer comments on them. I like long press thread/post for links, but it might be nice to make the option Send to... and allow it to open Talk, Messaging, Browser, etc. (along with just "clipboard") because if you're copying it you're doing it to paste it in another app, why not have a way to directly go to it? vvv Bookmarked, and I added the issue. Thanks! vvv LastInLine fucked around with this message at Sep 2, 2011 around 11:01 |
| # ¿ Sep 2, 2011 06:33 |













, if you enter the wrong data and it fails, change the text to 