Collin, Good thoughts. Let me qualify...I am definitely not saying that every iPhone app needs to use the edge to edge navigation list UI and needs to only use UI designs implemented already in the built-in apps (edge to edge, cover flow, etc.). As you point out, there are examples in which a different sort of look-and-feel do work best for what that app is intended to do. However, I do think that the design choices a developer makes needs to complement the overall iPhone UI standards and not clash with it. There are already too many examples of apps that do their own thing rather than trying to fit well inside of the iPhone environs.
- Rich On Sep 3, 2:17 pm, Collin Miller <[EMAIL PROTECTED]> wrote: > I disagree. > > I can quickly toss out examples of iPhone web apps with distinct look- > and-feel yet fit perfectly to the task at hand. > > Meebo.com > iPhone.facebook.com > > (the mobile version of google reader works great on the iPhone too) > > All these apps have distinct looks. And the similarities in their feel > stem from good choices in mobile design. > > Don't make me think and I won't care what colors you used or if your > buttons are buttons or tabs. > > Limit my choices to what I really want to do. > > And for goodness sake, remember that people will judge the book by > its cover. > > On Sep 3, 2007, at 10:30 AM, shelly <[EMAIL PROTECTED]> wrote: > > > > > I agree, but is iui , which is basically a clone of the youtube > > interface the best interface for media, I think other designs need to > > be explored before we start talking standard ui designs. Coverflow > > comes to mind. > > > On the other had iui is the easiest to implement and it looks good. > > > On Sep 2, 2:17 am, rich_wagner <[EMAIL PROTECTED]> wrote: > >> Here's some thoughts for new developers just starting out with iPhone > >> app design... > > >> Because the underlying guts of iPhone apps are based on Web > >> technologies (CSS, XHMTML, JS, Ajax, etc.), it is tempting for a Web > >> developer to come to the iPhone platform and consider the apps that > >> they create as a special, customized breed of Web app. After all, > >> from > >> a technology perspective, that is exactly what they are. > > >> However, we need to look beyond implementation. We should have the > >> mindset that we are creating iPhone applications, not Web > >> applications > >> that run on the iPhone. The difference is significant-no, not from a > >> technology standpoint, but definitely from a UI design perspective. > > >> On the Web, users expect every Web site/app design to be unique. > >> Developers naturally have embraced that freedom. However, when > >> working > >> on a platform, the user expectations are far different. That's why, > >> in > >> many ways, I would suggest that iPhone applications are far more like > >> Mac or Windows desktop applications than Web apps. Like on their > >> desktop, users will come to expect a common look and feel-whether > >> they > >> work with a built-in Apple app or a third-party Web app. Since we do > >> not have an API that we have to write to, it is up to the developer > >> to > >> understand the unique design needs of the platform and build an > >> application based upon it. (That's why frameworks like iUI can be so > >> helpful.) > > >> - Rich --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" 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/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
