Ok guys, here we go
Sorry that i weren't able to respond in the past two days, you already know why
It was hard to find the time to fix that annoying FC bug when opening the questions list but i thought that was more important at that time then responding here since it renders the app useless.
Ok let's start
FC on clicking questions.
Should be fixed in the current version
good concept for an app, will probably be pretty fun when its finished, but right now the app is extremely unstable, sometimes it just exits right after I opened it, it always force closes when it tries to load the "by date" list in the "list of questions" section. The "by potsize" list usually works though that sometimes crashes too, in addition to all that the app seems to sometimes crash at completely random times.
There was an additional bug in the update code for the header of the main screen. Hopefully that is fixed now too and you won't experience those random FCs.
ps: on the registration part of the app, you only ask for the password once, its pretty common to ask for the password twice to avoid people mistyping the password, this does't really bother me that much but when you are typing on the android virtual keyboard it pretty easy to mistype something and not notice it, before you try to login to your app account.
Good idea, will definitely integrate it
If you don't mind me asking, I'm a bit curious about how you store account information, do you store the email & password in plain text? or do you hash & salt them? I'm just curious because I don't like to use services that doesn't protect their user data properly.
The password is hashed on your phone so that it never get's transmitted over the network in plain text and i can't see your plaintext password either. The email is stored as plaintext so that i can send you a mail if anything important is going on (like yesterdays mail about that critical bugfix). The backend of the app is hosted on GoogleAppEngine by the way. Feel free to suggest any other strategies on storing or transmitting values. The values that are stored for a user are: your activation token, an active flag, answer count, question count, key of your avatar in the gae blogstore, mail, nickname, pass (hash), and your QZRs.
It allowed 0 QZR for a bid.
damn, thanks for the note.
Admob area's size need to be fixed.
What do you mean?
gmail seems to categorize your emails as spam, just thought you would like to know.
damn, will have a look at this. They arrive just fine in my gmail inbox.
And a question from my side:
I have also implement a function for sending mass in-app notifications (appear on your notification screen in the app). Which way to be informed about critical updates do you prefer? mail or in-app notification. In one of the next versions i will add an optional background service that shows incoming notification on the phone's notification bar, too.
Looking forward to read your responses