Mobile platform assessment Content Mobile platform objectives Scope

Mobile platform assessment

Content • • • Mobile platform objectives Scope and requirements Solution alternatives identification Solution assessment and comparison Summary Appendix

Mobile platform objectives Aalto-wide mobile app development and lifecycle management • Mobile platform enables rapid creation of both official and unofficial (“Beta”) mobile apps • Full life-cycle management from app development to retention Aalto mobile app ecosystem and collaboration • Supports different developer group needs such as Aalto ITS, researchers, students and mobile development partners • Single mobile platform enables efficient collaboration around mobile apps Mobile app distribution for Aalto users • Distribute Aalto apps to Aalto campus users (Aalto App store, App Store, Google Play)

Mobile platform scope Developer groups App architecture In-scope Type of apps Life-cycle management Aalto ITS Mobile app i. OS native apps Learn Mobile partners API / integrations Android native apps Develop Researchers Back-end systems / services Hybrid apps Integrate Web apps Test Students Externals Out-of-scope Distribute Iterate Retire

Requirements • • • Android (Java), i. OS (Swift), leading hybrid development languages Easy-to-use – supports the needs of different development groups Supports both official and unofficial (beta) apps development & management Integration to Aalto API management system (3 Scale) Alignment with current technology and architecture • Alignment with current technology and architecture (Red. Hat already in use extensively, 3 Scale/Open. Shift) Distribution channel (Aalto app store, Google Play, App Store) – TBD if own app store is needed Full life-cycle management from development, integration, testing, iteration to retention App pricing capability Compliance with Aalto Security User management (integrates to Aalto user management) Documentation (e. g. , how to implement Aalto SSO) Timeline – target is to start mobile app development during Q 3/2018

Solution alternatives identification • • • We have identified the following mobile platforms as they are aligned with Aalto strategy and IT architecture and do not require tendering process Red. Hat (on-premises and cloud solutions) Microsoft (Xamarin + Mobile Apps in Azure App Service)

Mobile platform assessment Assessment criteria Redhat on-prem Microsoft (Azure + Xamarin) Comments Development capability (tools, frameworks, build/deploy, collaboration) Life-cycle management Xamarin doesn’t have any life cycle management built-in, depends on Git App distribution & app store Xamarin doesn’t have built-in app distribution channel or an app store, depends on official app stores, eg. Play Store & App Store Integrations capability (API and data access to back-end services) RHMAP works with 3 Scale Enterprise-level control (user mgmt, security, etc) Costs (investments, run costs) Xamarin by itself is free Contracts & tendering considerations Timeline Maturity, references, active community Alignment with Aalto digital strategy and IT RHMAP runs on Open. Shift a platform which Aalto already has

Appendix

Mobile development lifecycle (Microsoft)

Red Hat Mobile App Platform

Assessment considerations • • • • Type of apps: Native apps (i. OS, Android), web apps, hybrid apps Mobile app development capability Tools, frameworks Testing Build & deploy Mobile back-end services & integration capability API management / integrations, authentication, micro services, data sync, storage, security Lifecycle management capability App store & distribution capability Analytics, reporting, notifications capability User management (internals, externals, partners) capability Costs (licensing model, user amounts, investments needed) Current contracts & Avoiding tendering process (mobile development partner tendering impact and preferences capability) Maturity, references, active community Alignment with Aalto IT and environment (on-premises, public cloud)