best practices for building ethereal apps - boulder startup week 2015
Post on 12-Aug-2015
72 Views
Preview:
TRANSCRIPT
Examples of Ethereal Apps• Sporting Events
• Masters
• Olympics
• World Cup
• Conferences
• WWDC
• BSW
Web Views
• Exist inside of your app, maintaining the experience
• HTML can be changed dynamically without App Store approval
• Caching, storage limits, and offline access can make this difficult
Configuration
• Powered by an API
• Externally update configuration via REST endpoint
• PRO TIP: Use a single endpoint that has all of your configuration information. Save to a plist and use this throughout the application lifecycle.
• Burning down the (TestFlight) house
Persistance
• Keep the “master record” outside of your application
• Be prepared to tear it all down
• Load from memory first, update from an API
Oh, and also…
• East Coast Joe’s backed out
• Knotty Tie and Sons of Scullery are switching booth spots
• When the app launches, the ‘News’ tab should be active until the day of the market. Then the ‘Vendors’ tab should be active. After the market closes, the ‘News’ tab should be active again.
Summary• Dynamic configuration should be leveraged as
much as possible
• Use web views where an API request is too difficult or not possible
• Keep the “master record” outside of your application
• Save your expedited app review for when you really need it. Like, when you really really need it.
Jordan StoneChief Software Architectjordan@getnotion.com
@cheddz
http://getnotion.com
@notion
Thanks!
top related