hong kong 2018 - blackberry...london, uk 2017 hk205: managing the application development lifecycle...

Hong Kong 2018

London, UK 2017

HK205: Managing the Application Development LifecycleDavid Arnold

Principal Enterprise Solutions Manager

Hong Kong | 2018

© 2017 BlackBerry. All Rights Reserved. 3

Setting the Scene


4

Setting the Scene§ Developers need to lead by example - business and admins have completely no idea !

§ Business Stakeholder want to see results fast

§ Apps need to exist in several ”states” – Dev, QA, UAT, Prod

§ QA, UAT and Prod groups are likely dispersed globally

§ Successful testing is vital for maintaining your reputation

§ Good Reputation = Further Projects


5

Agile Methodology and MVP§ MVP = Minimum Viable Product§ Agile is key to delivering successful results in Enterprise§ Stakeholders are often new to mobile§ As ideas make their way to product, expect stakeholders to change their minds§ Agile allows for continuous improvement of your product§ Prevents your project from going ”dormant”

§ Provisioning Profiles§ Certificates§ iOS / Android SDK Releases (+ Testing against new OS’s and Beta’s)§ Dynamics (and other) SDK Releases


6

Groups in Development and Testing

§ 4 Key Stages in Each Agile Development Cycle§ Important to include all these steps, and to separate them§ UAT users will also be Production users - key to allow them to still use Production App§ Development Team – will deploy from their development environment§ QA, UAT and Production users should receive their build from UEM

Development QA UAT Production


7

Build Targets – Key to Success

§ Leverage Build Targets / Build Variants § Use different Application IDs (App and Dynamics) – allows unique icons…

§ Eg. com.mydomain.myapp.dev com.mydomain.myapp.qa com.mydomain.myapp.uat com.mydomain.myapp.prod

§ Build different Icon Sets for each Build, and Names – simplifies testing§ Remember to test the ”update” process

§ Useful Links§ https://developer.android.com/studio/build/build-variants.html

§ https://www.appcoda.com/using-xcode-targets/


8

Whitelisting for Development


9



10



11


Do not add a binary !!


12



13

Publishing QA, UAT, Prod etc


14



15



16



17


This time we add a

binary so that

qa/uat/prod users can

download from the

”App Store”


18



19

App Store – End User Experience (no-MDM)§ Apply the Entitlement to Users – “Feature – BlackBerry App Store”

§ End user will see the ”Apps” link in their launcher


20

App Store Experience - MDM§ No need for ”Entitlement” as App Store is supplied as an iOS WebClip§ This WebClip can be customized for your business

§ Settings > App Management > Work Apps app for iOS§ Change Name, Icon and Full-Screen status

§ For Android MDM, recommend Android Enterprise. UEM integrates with ”Managed Google Play” to present your apps as part of the Enterprise Google Play Store (private)


21

Updating your Apps


22

Updating your Apps


23

Updating your Apps


24

Updating your Apps§ Work Apps Store – Notifies Users of Updates Available§ Recommend – Users in charge of when to update§ Internal Marketing / Email Promotion

hong kong 2018 - blackberry...london, uk 2017 hk205: managing the application development lifecycle...

Documents