2. Mobile Apps And The Cloud?
App
?
“The Lost Art Of Client/Server”
3. Mobile Clients And Web PaaS
Why does building
an app that runs on
App
the client require
you to write a bunch Web PaaS
of code that runs on
the server?
4. Web PaaS Are Still About Web Pages
Web PaaS are
optimized for web
apps spitting out web
pages from a
monolithic stack built
on the server-side PHP, Ruby, Java, .NET
App Engine, Heroku, Azure,
language and DotCloud, etc.
framework of the day
5. Mobile Apps Run On The Device
(Surprise!)
Services And Data Mobile is about
delivering rich
interaction from client
apps running on the
device with services
Native
HTML5/JS and data on-demand
Flash from the cloud
6. Rich Clients Need Rich Services
User Management
Access Control, Groups, Roles, Graphs
Connected & Social Interactions
Activity streams, linked profiles
App
Application Objects & API Integration
Base & Premium Functionality, 3rd Party Services
Content & Data
Personalized, Highly scalable, Deeply indexed
Data Processing & Analytics
Real-time, tied to specific user actions
INTERNAL AND CONFIDENTIAL
7. Requirements Of A Solution
We need to enable application developers to:
• Focus on client development
• Manage their users (customers) across multiple devices and
applications
• Build highly data-rich applications that are socially-
connected and can leverage both existing and mobile user-
generated content and media assets
• Monitor and analyze data to drive both application
functionality and business intelligence
• Not have to worry about server side infrastructure at all
13. Spot-On Trendspotter
Mobile application for real-time audience reaction
User response data is collected, transmitted to server via websocket,
correlated and transmitted back to all connected clients
14. Live Audience App (cont.)
App Objects And Features Used:
• User Management
• Friends & Colleagues “Graph”
• Schedules
• Realtime Data Streams