Open rbarman opened 10 years ago
I agree for using a toast only if the user swipes when there are no more previous quotes. To solve the issue of responsiveness, we could do this:
What do you think?
So that is all currently done for specific search. We COULD do something like that for random quote..... pull all quotes from a random page and random topic, but the consecutive quotes technically wont be random.
I'm not really sure how what you were saying for (2) deal with responsiveness though
For (2), I mean responsiveness in the sense that quotes can be displayed instantly, since they are already stored in a list. Yea, pulling quotes consecutively from a random page isn't 100% random. What if we pull all quotes from a random page and then use a random number generator with a range of the max number of quotes pulled from that page? If the same number has been generated, generate another number (otherwise the user would see the same quote).
Consecutive quotes still wont really random. We can connect to page from a random keywoard (age) and display various index values, but the user is only seeing quotes about age. The user would have to relaunch the random quote activity to get a random quote from a random keyword
Ah, I see. Never mind then.
A general principle for Apps is that it must be responsive to user touch. We currently have a toast message every time the user swipes left and right which does show some sense of responsiveness to the user. However the toast message is very bland and should be used sparingly. If the user were to swipe through quotes very quickly, there would be toasts overlapping the previous toasts and the user would see a toast message for t * n seconds where t is the time per toast and n is the number of toasts. The user could just click anywhere on the activity page to get rid of a toast but they would have to do it n times. This is not a good experience for the user.
I think we should have some sort of animation or transition between new quotes. We can however keep a toast message stating "there are no previous quotes" if the user attempts to get a previous quote on the first quote, but all other toast messages should be removed.