api oriented development and web mobile apps to conquer multi platform world
DESCRIPTION
App developers today face challenges that they rarely had to confront until not too long ago. Gone are the days where simply having a website was enough – consumers now expect to be able to access content and services from anywhere, using their mobiles and tablets in addition to their PC, and they expect their optimal experience in each device. API-oriented principles combined with mobile web platform come to the rescue, enabling efficient and quick creation of flexible and easy to maintain cross-platform products. This session will highlight the benefits of API-oriented mindset, explain why it’s worth investing in web mobile apps, and give a brief overview of new tools and initiatives supporting best practices.TRANSCRIPT
API-oriented development and web mobile apps
to conquer multi-platform world
Natalia Bartol
The Company
The Company
The Company
How
API-oriented development
and
web mobile apps
can help to overcome the challenges of
mobile development ?
Mobile = multiplatform
Different contexts:
Mobile - speed of access
Web - researching, exploring
3rd party access - integrations
Mobile = multiplatform
Mobile = multiplatform
frontend = Android, iPhone, Windows
Phone; Java, Objective C, C#... specialised developers
needed; it’s costly to maintain different stacks for platforms
Mobile = multiplatform
frontend = Android, iPhone, Windows
Phone; Java, Objective C, C#... specialised developers
needed; it’s costly to maintain different stacks for platforms
backend = how do I know my server API is good and
suitable for my app on different platforms
API 1st!
Think about your API first, then create client
apps.
Model your domain in a device-agnostic way.
Use well-established RESTful (hypermedia)
design model.
API 1st!
• reusable
• evolvable/extensible
• helps with continuous deployment
• scaling only what you need
• smaller applications are easier to test and
maintain
...API 1st!?
Caution: Can we design good API without
thinking of what clients actually needs?
...API 1st!?
Caution: Can we design good API without
thinking of what clients actually needs?
Use quick prototyping!
Client prototype should be developed in parallel
to API.
Mobile = multiplatform
Can I avoid writing frontend many times for
different platforms?
Solution known from desktop world:
portable platform
Portable platform What we’ve learnt about UX from Java?
emulated vs. native controls
Mobile = multiplatform
Why does the Web as a portable platform
work?
Different expectations
Users already know the web style on mobile devices
Device builders do the work of porting the web platform
native vs. hybrid vs. web apps
Affordability
User experience
Hybrid Web Mobile apps rule
● write once run everywhere - web is the only real
multiplatform
● independece from screen resolution and form
factor
● transferable skills of web developers
● low costs
● short time to market
● analyse the demand and then decide which
platform to target
Web Mobile apps rule… but are a
trade-off; native experience and
performance is still better.
Mobile development with Zend Cloud Connected apps in Zend Studio
API 1st
Mobile development with Zend Cloud Connected apps in Zend Studio
Quick prototyping
Mobile development with Zend Cloud Connected apps in Zend Studio
integrated Apache Cordova and native tools
Hybrid apps
Mobile development with Zend Zend Server
Mobile development with Zend
Apigility = streamlined interface for API-
enabling your code
http://www.apigility.org
/
Thank you!
Natalia Bartol
@nataliabartol