I like to go from a UI backwards because it means I am focusing on the user experience rather than the implementation details.
I don't think there is a right answer here, though. I usually look at it from a UX perspective, think about the implementation details, then change the UX requirements to make implementing a version 1 easier. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Wed, May 18, 2011 at 4:24 PM, Paul Meehan <[email protected]> wrote: > Hi all, > > I'm embarking on a fairly large scale and ambitious GAE app using JDO and > GWT(UI). My previous entrepreneurial spirit led me to develop ZoeOS, a > desktop Java/Swing based front-end and management tool for E-MU E4 hardware > digital samplers (http://www.zuonics.com) . I designed that product from > the bottom up i.e worked on the remoting layers first, then designed a > database/cache layer. From there I developed the business logic and finally > the Swing GUI evolved from there. > > My question is this: > > For a web app based in GAE, should I follow the same approach, working from > bottom up, and develop a domain model first? Or should I design a UI in GWT > first and work downwards from that UI specification? > > Any input appreciated. > > thanks > Paul C. Meehan > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
