Mobile Apps the Smart WayJoe Keuler – Innovation Center

1) Envision the need formobile

– Use cases2) Practical ways to implement mobile

– Business Side considerations– Development considerations

• Architecture• Toolset

3) Demo of mobile application for gov’t2

Citizen Use Cases for MobileHappy Holidays!

3

Citizen Use Case• Growing up mobile

4

Citizen Use Case• Mobile is moving toward becoming a

primary computing device

5

Mobile Markets• Facebook’s Mobile Moment

6

Digital Gov’t Use Case• Government Service

– Home Energy Plus Program: heating assistance and bill pay

– Complex program requirements

– Use Case: A loss of independence and on-site customer service

7

Practical Ways to go Mobile• Business Side

– Identify use cases for mobile prior to new development

– Design concurrently• Best if treated if NOT an after-thought

– If adding mobile, modernize the entire solution

8

Practical Ways to go Mobile• Development Side

– Architecture

• Fitness of platform: COTS, aPaaS, Traditional (n-tiered) Development

• Avoid developing the mobile and desktop pieces as two disparate projects

9

Practical Ways to go Mobile• Development Side

– Toolset • Current Architectural framework(s): MVC• Allows you to develop data and logic as one

project and then different screens• With Bootstrap and other tools design is inherently

responsive

– Current Example Projects: Energy and Charitable gaming

10

Practical Ways to go Mobile• Development Toolset Continued

• aPaaS: application Platform as a Service

• Has all of these practical mobile strategies baked-in

– Concurrent design process– Concurrent mobile and desktop development– Conforms to best practices – Immediate App deployment

11

Application Platform as a Service(aPaaS)

• Definition: a cloud-based application development ecosystem to support rapid application development

• Capabilities: provides the full technology stack to support modern applications: deployment, security, database, integration, mobility, analytics, social components, scalability

• Benefits: accelerated delivery, higher application development capacity, support of iterative development, reduced costs, quicker ROI, reduced TCO

• Shift Cost from infrastructure to delivering applications in a subscription based, pay-as-you-go model

12

13

Market Leaders

Demo• Use Case: Energy Assistance worker

visits assisted living facility to take an application– Worker gathers basic data

• Name, DOB, annual fuel costs, 3 month income, family size

– Data is used to determine program eligibility– A benefit is immediately calculated on-site

after the data is saved

14

But wait there’s more…• (These programs can be complicated)

– If they make too much money their application is denied

– If their income is too low, further investigation is warranted and will need supervisor approval (to prevent fraud)

– Otherwise, they’ll simply get a benefit

15

Gov’t programs require customization

• In aPaaS, the simple things are simple (and fast)

• but the complex and highly customizable things are possible while using all of the modern web standards and best practices.

16

aPaaS can handle complexity• Benefit formula = (1-(3 month income/max income

limit(family size))*(fuel cost/fuel cost coefficient)

• Higher income; lower portion of fuel bill paid…

17

Welcome Screen

18

Navigation Window

19

Recent Apps

20

App Entry

21

App ViewSent for Approval

22

NOTIFICATIONS!

23

MORE NOTIFICATIONS!!!

24

Approve or Rejectwithin the App

25

Communication

26

Communication

27

Mobile Dashboards

28

Pre-made functionality• User creation• Customizable email templates• Complex logical workflows• Mobile app deployment• Mobile browser experience• Dashboards and Reports• Field and object level security

29

Time taken to develop• Data-model:• Permissions

App Configuration:• Business Logic:• UI and Reporting:

• TOTAL:

30

1 hour

2 hours3 hours1 hour

7 hours??????

Summary

• There is a desired and a need

• aPaaS is a tool to quickly create mobile applications that adhere to modern standards and development best practices

31

• Hold for applause

• Remember to take this slide out

32