The different business modelsRevenue = hardware Revenue = software license Revenue = advertisementHigh margins High volume High volumeConsumer focused Enterprise and Consumer Consumer
Building apps for the Mobile Space User DeveloperExperience Distribution: productivity Public or private Security & Corporate? privacy Which platforms? Application Lifecycle Management
User interface designGraphical design– How does the app look?Interaction design– How do I create an effective and efficient user interface?– How do I create a natural experience that people understand without training?
User ExperienceEmotionSenseSometimes almost areligion!Must closely match thenative device experience!
Building native apps, the options C / C++ Different CPU architecturesObjective-C C# / Silverlight 3+ C / C++
Building native apps, the optionsReally?Write an app for each device?I need to master Objective C, Java and C#?Any alternatives?
Building the right user interfaceUI technology changes more rapidly then yourservicesSo what UI technology do I choose?General rule of thumb:– Reach: Web– Rich: Native OSSeparate lifecycle of client and services– Services are stable– Uix changes more rapidly
Code sharing is possible! Android Per App Reusable 16% 20% Specific WP7 35% 12% iOS Shared Shared app 18% logic 65% 20% Windows8 14% ...and that’s without the back end!
How target size influences error rate usability research 1/25 1/100 1/1000
Use touch target sizeRecommended size – 7x7mmOptimized for accuracy – 9x9mm Microsoft: 9x9mm Apple HIG: 44x44pxOptimized for small size – 5x5mmEach target has 2mm padding
What about other input methods? > Command output > more command more outputCommand line interface Graphical user interface Metro style user interface• Text commands • Click, double-click, right click • Slide/right click to select • Zoom/scrollbar to jump • Hold/hover to learn
Windows 8 touch interactionsPress and hold to Tap for primary Slide to drag Swipe to selectlearn action Swipe from edge for Pinch to zoom app and system UI Rotate to rotate
Cloud implications on architectureCloud introduces a new phenomenon– Pay as you go cost modelThis can have major implications on your architecture– Which cloud specific features do I useHard questions– Pay based on I/O or Compute cycles • How many I/O’s to storage of my service? • Algorithms can make a difference!– How much data am I going to store • Price differences based on storage models
SummaryMobile trend is just taking offThe game is on!, not overNew user interface concepts will influence theway we build appsEach form factor requires unique interfaceCloud is there to support our massive computingdemandPay as you go model – Game changer for new business models!
Next session:20:15 Marcel MarcelTrack 1 (Seminarruimte 1) Meijer de VriesNext Generation User Interfaces SDN Regional DirectorTrack 2 (Seminarruimte 2) @marcelmeijer @marcelvGebruik van MVVM en Maps op Windows Phone Dennis Vroegop Thank you! DotNed @dvroegop