Managing Native App Builds

Ryan Schaefer, Digital Project Manager

February 14, 2020

The Plan

01. Let’s Talk About Apps

02. PM Tips for Mobile Builds

03. Conclusion

01. Let’s Talk About Apps

Hybrid Apps

A hybrid application is a single product built to run on multiple

operating systems.

Hybrid Apps

HubSpot

Hybrid Apps

● Hybrid Web: A combination of web technology and native device implementation

○ Run on a mobile device within a native container, using a WebView

● Hybrid Native: Also a combination of web technology and native device implementation

○ Key differences are they render components native to devices and do not use a WebView

UI Components

Bits and Pieces

Hybrid Web Apps

Single codebase

Design parity

Customization

Non-native UI

Performance

Pros Cons

Hybrid Native Apps

Native UI

Performance

Framework universality

Framework dependent

Fragmented codebases

Inconsistent design

Pros Cons

Native UI Components

Muzli

iOS picker Android picker iOS control Android control

Examples

● If you have a mid-sized budget

● If you want to get something to market quicker

● If you prefer one design pattern across all devices

● If you want to support multiple OSes

● If you don’t fear relying on third parties

● If your app isn’t too performance-intensive

Business Case for Hybrid Apps

● Built for multiple operating systems

● Use web languages like HTML, CSS, Javascript

● Use an abstraction layer

● Single codebase

● Can run on browsers and PWAs

● Framework-dependent

Hybrid Apps

What is a native app?

Native Apps

A native application is a mobile product built for a single operating system.

Native Apps

DevTeam.Space

Examples

Native App Key Differentiators

Tooling

Performance

Security

System UI

Distributed Codebase

Cost to Build

Maintenance

Pros Cons

● If you have the money

● If you have the time

● If you prefer native OS components over a shared library

● If you only care about supporting one OS

● If you want less technical overhead

● If you have a game or performance-intensive app

Business Case for Native Apps

● Built for a single operating system

● Seamlessly incorporate device features

● Use specialized languages like Swift or Kotlin

● Platform-specific tools

● Fast, secure, and reliable

Native Apps

Mobile Comparison

Native Hybrid Native Hybrid Web

OS Single Multiple Multiple

Performance Great Good OK

Cost $$$ $$ $

Device Integration Great Good OK

Tooling Great Good Good

Security Great Good Good

Maintenance LOE OK Good Great

The Plan

01. Let’s Talk About Apps

02. PM Tips for Mobile Builds

03. Conclusion

02. PM Tips for Mobile Builds

So, you’ve become the PM for

a mobile build...

Learn.

T I P 1

Learn

● Different languages

● Cost of failure

● Edge cases

● API integration

● Memorization != understanding

● From your team

viget.com/articles/understanding-native-apps-for-non-developers/

Articulate the mobile UX and design constraints.

T I P 2

Articulate UX and design constraints

● System controls

● Offline behavior

● Device features

● User error

Viget

Don’t count on designs being 100 percent Approved™.

T I P 3

What is an “approval”?

● Unexpected behavior is magnified

● Get to 90 percent

● Prototyping is key

Digital Synopsis

Set up continuous integration as soon as possible.

T I P 4

Set up continuous integration

● Automates build process

● Reduces errors

● Cuts down QA

Viget

Test early and often.

T I P 5

Test early and often

● Automated vs. manual

● Bugs are a bigger deal

● Utilize run-time or remote feature toggles, if available

● Worst-case scenarios

● Don’t forget the data

Performance Management Co.

Consider OS updates and different devices.

T I P 6

OS updates and different devices

● Device fragmentation

○ Hardware

○ Software

○ Feature variations

○ User preferences

● Older browsers, OSes, and devices

Yahoo Finance

Spearhead the App or Play Store submission process.

T I P 7

Lead App or Play Store submission

● Know your screenshots

● Gather URLs

● Store optimization

viget.com/articles/submit-to-app-play-store/

Apple Developer

The Plan

01. Let’s Talk About Apps

02. PM Tips for Mobile Builds

03. Conclusion

03. Conclusion

Tips for Mobile Builds

1. Learn.

2. Articulate the mobile UX and design constraints.

3. Don’t count on designs being 100 percent Approved™.

4. Set up continuous integration as soon as possible.

5. Test early and often.

6. Consider OS updates and different devices.

7. Spearhead the App or Play Store submission process.

Thanks!

ryanjschaefer.com

viget.com

@ryanschaefer41

/in/ryanjschaefer