• Overall design could be improved - I guess you already know that, though. What especially annoys me is the icon.
  • adamw : Oh, I know - especially about the icon. But damnit Jim, I'm a programmer, not an artist. And despite the plethora of open source code for people who can't/don't have the time, there's very limited decent "open source" art. I also don't have any budget to pay for someone to make a nice icon.
• Instead of showing an alert when opening the app the first time, why not direct the user to the view to setup a site immediately?
  • adamw : Hmm, I could do this. I erred on the side of an explanation - a big UI popup with no context can be scary. I shall consider this.
• Why not allow users to choose multiple sites at once to setup?
  • adamw : This is a good idea, and I'm looking into it. Alas, it makes life complicated with respect to the "user tracking" feature. If you select a site then track a user, it would have to whittle this list down to just the sites that can be tracked. If you've already selected more than one site, what happens to the UI if the user is found on one but not the other? I need to ponder on the best way of doing it.
• Questions/answers per minute shows 0.0 on Stack Apps. Is there really so little going on here or is this a bug?
  • adamw : Not a bug, it's just that quiet around here. We get less than a half dozen posts a day, in my experience, which the API is rounding down to 0.
• Why not show the question text when tapping the question title, instead of wasting space with a big button?
  • adamw : Good idea. I shall be improving the initial "Question view" in 1.1 to give more context about the question itself.
• It's not really obvious to me that hitting the blue arrow opens the author's profile. Maybe you could just split the list item and create a second one for the author, which open his page when being tapped regularly?
  • adamw : I thought this was a pretty standard iPhone convention for detail disclosure in list items? I'll ponder :)
• On the answer page, the author's profile is opened by tapping on the author's name. This is inconsistent.
  • adamw : Agreed, but this is a deliberate choice, for space expediency. To make it UI consistent, I'd have to fence off a lot more UI space there to be consistent with the detail disclosure button. There's a redesign of the entire header section of the post view coming soon though, which might help me do this.
• When you scroll through a user's badges or a question's answers, only part of the view can be scrolled. It would be nice to see the whole page moving, so one can use the maximum space for viewing the content one wants to, when the list is long enough.
  • adamw : I actually prefer it the way it is. Seeing the user name and question title persistently is, in my opinion, more useful.

• Overall design could be improved - I guess you already know that, though. What especially annoys me is the icon.
  • adamw : Oh, I know - especially about the icon. But damnit Jim, I'm a programmer, not an artist. And despite the plethora of open source code for people who can't/don't have the time, there's very limited decent "open source" art. I also don't have any budget to pay for someone to make a nice icon.
  • eWolf : I almost assumed that. Just wanted to give all possible feedback.
• Instead of showing an alert when opening the app the first time, why not direct the user to the view to setup a site immediately?
  • adamw : Hmm, I could do this. I erred on the side of an explanation - a big UI popup with no context can be scary. I shall consider this.
• Why not allow users to choose multiple sites at once to setup?
  • adamw : This is a good idea, and I'm looking into it. Alas, it makes life complicated with respect to the "user tracking" feature. If you select a site then track a user, it would have to whittle this list down to just the sites that can be tracked. If you've already selected more than one site, what happens to the UI if the user is found on one but not the other? I need to ponder on the best way of doing it.
  • eWolf : You're right. I'm just criticising and you gotta take care of the details, haha :-P
• Questions/answers per minute shows 0.0 on Stack Apps. Is there really so little going on here or is this a bug?
  • adamw : Not a bug, it's just that quiet around here. We get less than a half dozen posts a day, in my experience, which the API is rounding down to 0.
• Why not show the question text when tapping the question title, instead of wasting space with a big button?
  • adamw : Good idea. I shall be improving the initial "Question view" in 1.1 to give more context about the question itself.
• It's not really obvious to me that hitting the blue arrow opens the author's profile. Maybe you could just split the list item and create a second one for the author, which open his page when being tapped regularly?
  • adamw : I thought this was a pretty standard iPhone convention for detail disclosure in list items? I'll ponder :)
  • eWolf : It is. What I don't find clear is that the opened view refers to the author, and not the question which is represented by the list item. I just noticed that you placed the blue arrow on the height of the author name - but still, I don't like it :-/
• On the answer page, the author's profile is opened by tapping on the author's name. This is inconsistent.
  • adamw : Agreed, but this is a deliberate choice, for space expediency. To make it UI consistent, I'd have to fence off a lot more UI space there to be consistent with the detail disclosure button. There's a redesign of the entire header section of the post view coming soon though, which might help me do this.
• When you scroll through a user's badges or a question's answers, only part of the view can be scrolled. It would be nice to see the whole page moving, so one can use the maximum space for viewing the content one wants to, when the list is long enough.
  • adamw : I actually prefer it the way it is. Seeing the user name and question title persistently is, in my opinion, more useful.

Thanks for letting me try out the pre-release! Here is my feedback:

• Overall design could be improved - I guess you already know that, though. What especially annoys me is the icon.
• Instead of showing an alert when opening the app the first time, why not direct the user to the view to setup a site immediately?
• Why not allow users to choose multiple sites at once to setup?
• Questions/answers per minute shows 0.0 on Stack Apps. Is there really so little going on here or is this a bug?
• Why not show the question text when tapping the question title, instead of wasting space with a big button?
• It's not really obvious to me that hitting the blue arrow opens the author's profile. Maybe you could just split the list item and create a second one for the author, which open his page when being tapped regularly?
• On the answer page, the author's profile is opened by tapping on the author's name. This is inconsistent.
• When you scroll through a user's badges or a question's answers, only part of the view can be scrolled. It would be nice to see the whole page moving, so one can use the maximum space for viewing the content one wants to, when the list is long enough.

I hope my feedback helps you. Oh, and asides from the flaws listed in my answer, your app is pretty awesome! ;-)

Thanks for letting me try out the pre-release! Here is my feedback:

• Overall design could be improved - I guess you already know that, though. What especially annoys me is the icon.
  • adamw : Oh, I know - especially about the icon. But damnit Jim, I'm a programmer, not an artist. And despite the plethora of open source code for people who can't/don't have the time, there's very limited decent "open source" art. I also don't have any budget to pay for someone to make a nice icon.
• Instead of showing an alert when opening the app the first time, why not direct the user to the view to setup a site immediately?
  • adamw : Hmm, I could do this. I erred on the side of an explanation - a big UI popup with no context can be scary. I shall consider this.
• Why not allow users to choose multiple sites at once to setup?
  • adamw : This is a good idea, and I'm looking into it. Alas, it makes life complicated with respect to the "user tracking" feature. If you select a site then track a user, it would have to whittle this list down to just the sites that can be tracked. If you've already selected more than one site, what happens to the UI if the user is found on one but not the other? I need to ponder on the best way of doing it.
• Questions/answers per minute shows 0.0 on Stack Apps. Is there really so little going on here or is this a bug?
  • adamw : Not a bug, it's just that quiet around here. We get less than a half dozen posts a day, in my experience, which the API is rounding down to 0.
• Why not show the question text when tapping the question title, instead of wasting space with a big button?
  • adamw : Good idea. I shall be improving the initial "Question view" in 1.1 to give more context about the question itself.
• It's not really obvious to me that hitting the blue arrow opens the author's profile. Maybe you could just split the list item and create a second one for the author, which open his page when being tapped regularly?
  • adamw : I thought this was a pretty standard iPhone convention for detail disclosure in list items? I'll ponder :)
• On the answer page, the author's profile is opened by tapping on the author's name. This is inconsistent.
  • adamw : Agreed, but this is a deliberate choice, for space expediency. To make it UI consistent, I'd have to fence off a lot more UI space there to be consistent with the detail disclosure button. There's a redesign of the entire header section of the post view coming soon though, which might help me do this.
• When you scroll through a user's badges or a question's answers, only part of the view can be scrolled. It would be nice to see the whole page moving, so one can use the maximum space for viewing the content one wants to, when the list is long enough.
  • adamw : I actually prefer it the way it is. Seeing the user name and question title persistently is, in my opinion, more useful.

I hope my feedback helps you. Oh, and asides from the flaws listed in my answer, your app is pretty awesome! ;-)

• adamw : All feedback is great, and thanks for taking the time to give it :)