• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: iPad: UI Implications
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: iPad: UI Implications


  • Subject: Re: iPad: UI Implications
  • From: Ricky Sharp <email@hidden>
  • Date: Fri, 26 Nov 2010 10:34:27 -0600

On Nov 26, 2010, at 9:02 AM, Phillip Mills wrote:

> I don't have any specific questions or problems associated with this but I'm curious about attitudes, techniques, patterns, or tools that others have found helpful going from Mac to iOS.

At a high level, you don't "go from Mac to iOS".  i.e. you don't attempt to port, clone the UI, etc.

Start with a mission statement of what you want to do with the iOS app.  Keep it simple.  Perhaps start with the mission statement of your Mac version, then trim it down to what makes sense to have in a mobile environment.

Then, storyboard your app.  Do not even reference your Mac version; think about the best possible ways to provide your features.  Trust me, don't get hung up on how the Mac version presents itself.  Rethink everything.

There is room to share though, but leave that to your business logic.

FWIW, here's my setup for all my apps:

(1) A set of "foundation" classes (utilities, common models, etc.).  These are shared* between all apps for Mac OS X and iOS.

(2) A "shell" app.  There's one for Mac OS X and one for iOS.  All apps I write sit upon one or both of these.

(3) Business logic for each individual app.  These are shared between Mac OS X and iOS.

(4) Individual projects for Mac OS X vs. iOS.  Here, they sit upon the appropriate "shell" and reference all common code.  Graphical assets, nibs, etc. are then unique to each individual project.


* sharing has had its downsides.  The original Mac version was baselined to Mac OS X 10.4 (pre Objective-C 2.0).  Thus, that set of code isn't yet using things like the newer property syntax.  My newer individual projects though do.

Also, know that in iOS, there is no GC.  So either create "dual" code to handle both cases (you can then drive things with compile-time macros), or stick with non-GC code everywhere.

___________________________________________________________
Ricky A. Sharp         mailto:email@hidden
Instant Interactive(tm)   http://www.instantinteractive.com



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: iPad: UI Implications
      • From: Phillip Mills <email@hidden>
References: 
 >iPad: UI Implications (From: Phillip Mills <email@hidden>)

  • Prev by Date: Re: Radio dial buttons [iOS] -sheesh
  • Next by Date: Re: Scroll/Position Image in Scrollview that is smaller than the Scrollview
  • Previous by thread: iPad: UI Implications
  • Next by thread: Re: iPad: UI Implications
  • Index(es):
    • Date
    • Thread