Thanks so much for your detailed feedback! I'll try to address it point-by-point: > You should disable selections on these since they do not actually drill in

Thanks so much for your detailed feedback! I'll try to address it point-by-point: > You should disable selections on these since they do not actually drill in anywhere. I'll definitely do this in both the calendar and schedule views. > I would suggest for upcoming events, you look into making the dates more readable. This sounds useful - and suggestions for libraries that can handle this? > Finally, the Feedback button doesn't really belong here. I agree - but I wanted an easy way for students to report bugs they found. I don't know if they would find it if I hid it away somewhere. Any suggestions on where else I can put it? > But, a better approach might be to ask the user when they first visit this tab what grade they are in, save that, and then provide a button in the navigation bar to change that setting. (You can try using an action sheet for this.) Good point - I'll probably implement this. One thing, though - for teachers that teach multiple grades, it might make it harder for them to find the different schedules at a glance. Then again, I'm not sure they really check the schedule in between each class. > But, even more importantly, just like your grade, you probably don't change your schedule type very often! In fact, as you noticed since you put it at the top, unlike your grade (where everyone is probably evenly split between grade), most people all are on a normal schedule, and then everyone changes to weird ones once in a while. .... A better format for your schedule screen might be something along the lines of the weather app, where you flick to page between the different schedules. Well, we have a PM activity schedule every Friday - but pagination might still be a better option. > I might be wrong here, but I don't see the point of moving assignments around. This allows for prioritizing - whenever you add an assignment in, it goes to the bottom of the list. However, if it is, for example, due before something that is above it, I like to move it up. > I think the help text said I should be able to delete things, but I couldn't get that to work. In regular mode (not manage mode), you can press and hold on an assignment to bring up the edit/delete menu. The modes are confusing - but I want to keep reordering and have it separate from the regular mode. > Make it so I can check off an assignment by tapping anywhere in the entire table cell. Good point - I'll do this. > But, don't move anything around when you tap on them, just leave them there checked or unchecked. Good idea - I think I'll remove the sectioned table view but move the completed assignments to the bottom (much like Clear). > First, my guess is most of the time, people are going to get hall passes for one of the options in the "List" view. Not really, actually - I usually use a hall pass to go see teachers, and I have to type their names in. > I like the design of your custom "List" box, similar to your "Jump" view, but it's very different than the rest of the app and remember: if you're being clever like this, you probably need to simplify! iOS already has controls for this type of problem: the spinner. I don't really like the look of spinners, but the list box might be a bit of an overkill. I'll look in to replacing it. > Instead, they need things at 5-minute precison. This is probably correct for times longer than, say, 10 minutes. However, for shorter times, 5-minute precision might be too limiting. > I would move "clear" and "submit" to the left and right corners of the navigation bar. I have them at the bottom to follow the natural flow of view - you fill out the form from top to bottom and hit submit. > Also, its weird that you have two ways to "clear" a hall pass, though this might be a quirk with your school. Now that I think about it - the clear button seems kind of useless. I'll get rid of that. > Red isn't bad, but I'd dial down the saturation a bit since bright red is a danger color. Red is our school's color. The saturation might be a bit high, though, so I'll change that. I just used the default red navigation bar that came with PrettyKit. Overall, though, I'll work on trying to come up with a single color scheme. > I'm not sure where your buttons came from for Hall Pass but they are a little weird and are not standard iOS-styled buttons. Yeah - they're BButtons (https://github.com/mattlawer/BButton https://github.com/mattlawer/BButton). I saw them on CocoaControls and thought they would be kind of cool. They may be overboard, though. > I think it is a little too small as the "Tap here" text is up too far against the edges of the control. I do think it is too small - I'll try to make it larger while still fitting in the toolbar. > When users launch the app they will see the calendar tab as the app opens and the table view will "pop in". I'll look in to doing this. > Think about what your users will actually use. Great point - I was hoping that the feedback feature would be useful for this. > How did you get into this? After 6th grade, I developed a simply prototype of an app to handle the hall passes. My technology-education teacher saw it and asked me whether I would be interested in developing a much broader app to replace the agendas. This kind of got me started - I asked my classmates for what they would like to see and started developing those features. > Were your parents involved? Not really - they gave me some feedback and encouragement, but not any help with developing the app. > How could we get more kids like you to try hacking on their iPhones? I think startups like makegameswith.us (and CodeCademy to some extent) are helping with this. Having a computer science class (or teaching programming in, say, tech-ed) as early as middle school would be great. > Great work and keep it up! Finally, here's a short bibliography if you are interested in reading more... Thanks! The App Design Handbook looks really great... Again, thank you for taking the time to go through the app and come up with this feedback. I'll definitely implement some of your suggestions...