This document discusses options for building mobile applications and presents Ionic Framework as a solution. It notes that building native mobile apps for multiple platforms is difficult due to different styles, code bases, teams required. It considers building fully native, compiling to native, and using web technologies. While building native has highest fidelity and performance, it has downsides of multiple languages/teams. Compiling to native has cross-platform UI but is not truly native. The document argues that using web technologies like Ionic Framework is easier and future-proof, giving developers access to native device capabilities through plugins. Ionic provides pre-built UI components, gestures, animations for a native look on each platform while developing with open web standards.

1. Mobile Delivery
Run Through
Mike Hartington
@mhartington

2. Mobile Delivery
Run Through
Mike Hartington
@mhartington

3. Who Am I?
Mike Hartington
Developer/Advocate
GDE for Angular, Firebase, Web Technologies
https://twitter.com/mhartington
github.com/mhartington

4. Building for
Mobile is Hard
Multiple Platforms styles to design for
Different code base to maintain
More developers to hire
Steep learning curve
What about PWAs?

5. What are our
solutions?
Build Native?
Compile to Native?
Web Technologies?

6. Build Native?
Pros
Highest Fidelity (1:1 of platform design)
Performance improvements with each update
Power from low level languages

7. Build Native?
Cons
Multiple languages to learn
Multiple code bases to maintain
Multiple teams to coordinate
What about the web?

8. Build Native? ❌
Compile to Native?
Web Technologies?
What are our
solutions?

9. Compile to Native?
Pros
Flexibility of JavaScript, performance of Native
"Standard" Library for API access
Cross platform UI

10. Compile to Native?
Cons
Uncanny Valley of “Native” and not native
Difficult to work around complex abstractions
Still need to know native development tools
What about the web?

11. Build Native? ❌
Compile to Native? ❌
Web Technologies?
What are our
solutions?

12. Web Technologies
It runs everywhere
It’s easy to work with
Open Standards
Future-proof
Accessible
(and you probably already know it)

13. Build Native? ❌
Compile to Native? ❌
Web Technologies? ✅
What are our
solutions?

14. But...
There's no SDK
for the Web
Native is made "easy" with these SDKs
Components, Animations, Gestures
The Web has to reinvent these concepts.

15. Enter, Ionic
👋

16. Ionic Framework
UI Components for native mobile apps, PWAs, and even Desktop
Pre-built Gestures and Animations
Platform Continuity for iOS and Material Design
Full access to all Native APIs and Plugins
A large, vibrant world-wide community

17. UI Components (100+)

18. Gestures & Animations
Swiping gestures between views
Sliding items for reveals
Automatic Animations for Modals and overlays

19. Platform Continuity
A N D R O I D I O S
Platform-aware components
Look-and-feel at home
Up to date with latest UI design

20. Native Access
Official and Community plugin ecosystem
Capacitor to integrate with Ionic
Can integrate with custom needs and APIs

21. Framework/components are open source (MIT)
Native layer (Capacitor) also open source
Open Web Standards - available to everyone
Open Source
everything

22. Real example

23. Angular Material can handle this
Clarity Design System
Roll your own!
Not alone in this
space

24. Building for
Mobile is Hard
But it doesn't have to be
Multiple choices for how you can build products
Different choices for different teams
The web can cover a lot of use cases
Evaluate with your team

25. Thank you!
</presentation>