Hey,
I'm a little confused at the response here. Cited is "Reason 10.6": "Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good it may be rejected."
Feeling is a data capture app, so the implementation of the act of capturing data is very intentionally designed. I could have designed it for capturing as many events per day as desired, but I chose not to – that's an implementation and design detail that I feel strongly about. Besides, if a user feels like their previous rating of the day is inaccurate, they can go back and change the rating later with no consequence.
Can you explain to me why you feel that this is a example of poor user experience? As far as I can tell, this has nothing to do with user experience; if, hypothetically, you could record multiple events per day, they would appear exactly the same as five days' worth would in the graph view and table view. The experience would essentially be identical, as would the UI representation of that data.
Like I've said, I could very easily have designed multiple events per day - it's a checklist of two items:
- Allow add button to be clicked on same day
- Calculate the average for a group of ratings on a day to display on the graph
Regardless, it's not the design that I chose and that I believe in. I'll be submitting an appeal to the App Review Board today, as I feel like this the reason for the rejection is, to say the least, inaccurately categorized.
Kristian