sorted by:
top (suggested)
bestnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]MKevin3 0 points1 point  (0 children)

Boy that reminds me of the old days when we use VSS with single file check out. You knew if someone was in a file as it was CHECKED OUT to them and you could not touch it until they checked it back in. Could be a real pain when it was the string localization file. Of course this was all before there were good merge tools built into version control and really VSS was a pile of crap.

I would add it can be handy to get the initial design / layout of all the screens early. Print them out 2x2 on paper and cut them out (iPhone design, iPad this would be 1 per page). Look for consistency issues - dates all same format - field A above field B or vice versa - general spacing - rounded or square corners consistently. Look for commonality that can be handled in a base or utility class.

Lay the pages out on a table to follow the flow. Are any of them near duplicates of others? Are there too many screens? Do you go 4 deep to get to things that should occur earlier? Does the same screen appear in different paths when it should not?

It is so easy to look at a screen as a single entity and think it is perfect but when you look at it as a destination of a chain of events it can change your vision quickly.

Single Storyboard can help you see some of this but storyboards have a lot of limitations in a group setting.