Mobile Development
•Télécharger en tant que PPSX, PDF•
5 j'aime•1,789 vues
Mobile Development faces many challenges. Using the right mobile architecture and development tools and using a DevOps process mitigates the risks.
Recommandé
Contenu connexe
Tendances
Tendances (11)
Similaire à Mobile Development
Similaire à Mobile Development (20)
Mobile Development
- 1. Mobile Development Edwin van Schaick
- 2. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 2 Agenda Mobile Development Process Mobile Trends Challenges in Mobile Development Mobile Architecture & Development
- 3. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 3 Agenda Mobile Development Process Mobile Trends Challenges in Mobile Development Mobile Architecture & Development
- 4. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 4 Context Awareness is Key Context Awareness is Key
- 5. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 5 Mobile Payment evolves Mobile Payment evolves “9.9.2014 – Wish we could say more.” – Apple (announcement event for iPhone 6 reveal) “The end of the wallet” – Vodafone (Introduction Vodafone SmartPass)
- 6. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 6 Internet of Things is coming Internet of Things is coming
- 7. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 7 Carefully engage Social Media Carefully engage Social Media
- 8. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 8 Services from the Cloud Services from the Cloud
- 9. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 9 Analytics on Big Data Analytics on Big Data
- 10. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 10 Agenda Mobile Development Process Mobile Trends Challenges in Mobile Development Mobile Architecture & Development
- 11. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 11 FPalasttf oTermch naonldo gDye vInicneo vFaratigomn entation
- 12. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 12 FFaasstt TTeecchhnnoollooggyy IInnnnoovvaattiioonn
- 13. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 13 Security
- 14. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 14 IInntteeggrraattiioonn
- 15. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 15 UUnnrreelliiaabbllee CCoonnnneeccttiivviittyy
- 16. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 16 FFaasstt TTiimmee ttoo MMaarrkkeett ffoorr MMuullttiippllee PPllaattffoorrmmss
- 17. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 17 OOppttiimmaall UUsseerr EExxppeerriieennccee
- 18. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 18 SSccaarrccee RReessoouurrcceess
- 19. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 19 Agenda Mobile Development Process Mobile Trends Challenges in Mobile Development Mobile Architecture & Development
- 20. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 20 Mobile Solution Reference Architecture Mobile Device App App Operating System and Device Hardware MDM Interface Device Password Device Identifier Certificates Encryption App Policies Provisioning Remote Wipe Enterprise Backend Services MDM / MAM Device Management App Management Enterprise App Store Secure Communication Push Notifications Mobile Access Layer Authentication / Authorization Business Service Integration Mobile Web API Services Analytics Data Sync Notification Provider
- 21. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 21 Mobile App Reference Architecture App Business Logic iOS UI MDM Signing iOS Tablet / Phone Android Tablet / Phone Windows Tablet / Phone Presentation Logic Reusable Non Reusable Android UI Windows UI Service Interfaces Domain Entities Common Sensors Local Storage Encryption Globalization Connectivity More… Resource Services Platform Services
- 22. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 22 Mobile App Development Native Applications Hybrid Applications Mobile Web Applications Native Development Multiplatform native Development Multiplatform Framework Development Mobile Web Development
- 23. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 23 Native Development Multiples development environments Objective-C, Java, .NET Separate code bases and expertise needed for iOS, Android and Windows platforms Optimal user experience, performance and access to device features
- 24. Multiplatform Native Development Shared code base for iOS, Android and Windows platforms Mobile Development | 9 Sep 2014 One development environment .NET, Xamarin and Visual Studio or Appcelerator and JavaScript Copyright © Capgemini 2014. All Rights Reserved 24 All advantages of native development still apply Shared design patterns and way of working across multiple platforms and applications
- 25. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 25 Multiplatform Framework Development One development environment .HTML5, Eclipse or dedicated environment Shared code base for iOS, Android and Windows platforms Shared user interface across platforms Optimized for backend integration
- 26. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 26 Mobile Web Development One development environment .HTML5, Eclipse, Visual Studio or other environment One code base for iOS, Android and Windows platforms Shared (responsive design) user interface across platforms Direct deployment
- 27. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 27 Choosing the right development method Feature Native Development Multiplatform Native Development Multiplatform Frame-work Development Mobile Web Development Development Cost High Medium Medium Low Code Sharing None High High High Device Integration High High Medium Low Advanced UI High High Medium Medium Deployment App Store App Store App Store + Web Server Web Server Development Language Native C# HTML5, JavaScript HTML5, JavaScript Performance High High Medium Low (network dependency) Security Full Control Full Control Container Dependency Browser Dependency Innovation Fast Fast Medium Slow
- 28. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 28 Agenda Mobile Development Process Mobile Trends Challenges in Mobile Development Mobile Architecture & Development
- 29. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 29 DevOps App Center Concept Design Create Monitor Publish Verify Organization Process Architecture People Technology
- 30. write code prepare test environment make automated functional tests make unit tests Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 30 Agile Mobile Development Process review continuous integration dashboard execute automated functional tests perform manual tests perform acceptance tests craft solution UX design adapt architecture technical design write test cases analytics social media user feedback and reviews app store ratings create deployment packages make release notes publish to app stores release support Design Create Monitor Publish Verify
- 31. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 31 craft solution UX design adapt architecture technical design write test cases Design Design Create Monitor Publish Verify
- 32. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 32 Design Innovative mobile use stories Use personas and scenarios to identify relevant contextual value Use style sheets and responsive design for all digital channels Use and adapt reference architecture Include testing from the start Design
- 33. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 33 Create write code prepare test environment make automated functional tests make unit tests Design Create Monitor Publish Verify
- 34. Use subset of most used devices for development and test Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 34 Create code and automated tests in parallel Automate everything from creation to publication Create Create
- 35. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 35 Verify review continuous integration dashboard execute automated functional tests perform manual tests perform acceptance tests Design Create Monitor Publish Verify
- 36. Verify Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 36 Verify Use a peer code review tool Automatically perform functional and unit tests upon code changes Use a continuous integration dashboard Consider a mobile test cloud solution for broad device verification Consider network emulation software Consider cloud testing
- 37. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 37 Publish create deployment packages make release notes publish to app stores release support Design Create Monitor Publish Verify
- 38. Publish Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 38 Publish Automate packaging and if possible publishing Take App Store deployment time into account (one or two weeks) Arrange certificates for publishing
- 39. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 39 Monitor analytics social media user feedback and reviews app store ratings Design Create Monitor Publish Verify
- 40. Monitor Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 40 Monitor Monitor the stores and social media Use mechanism to retrieve info about production issues Use analytics
- 41. Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 41 Questions
- 42. Contact | Capgemini Netherlands http://www.capgemini.com/experts/embedded-and-mobile-solutions/edwin-van-schaick Mobile Development | 9 Sep 2014 Copyright © Capgemini 2014. All Rights Reserved 42 Architect Embedded & Mobile Solutions Capgemini Edwin van Schaick Edwin.van.Schaick@capgemini.com eschaick
- 43. www.capgemini.com The information contained in this presentation is proprietary. © 2014 Capgemini. All rights reserved. About Capgemini With more than 120,000 people in 40 countries, Capgemini is one of the world's foremost providers of consulting, technology and outsourcing services. The Group reported 2011 global revenues of EUR 9.7 billion. Together with its clients, Capgemini creates and delivers business and technology solutions that fit their needs and drive the results they want. A deeply multicultural organization, Capgemini has developed its own way of working, the Collaborative Business ExperienceTM, and draws on Rightshore ®, its worldwide delivery model. Rightshore® is a trademark belonging to Capgemini
Notes de l'éditeur
- Offer the right functionality depending on situation and environment in the broadest sense. Examples: Relevant apps for frost only when it’s freezing. iBeacons in store to offer products. Offers retailers Big Data about the public. Some Enterprise Apps only usable on premise. Personal advertisements. Recognize customer emotions in call center.
- Near Field Communication (NFC). Mobile Payment Platform on iPhone 6? Google Wallet? Use Biometrics to authenticate.
- Think of any device as a potential sensor. Think about how to make the dialogue with the consumer more intelligent. At home: smart energy meter, cameras, lights, smart smoke detector, washing machine. Smart vending machine. Surroundables: Things surrounding you like your car Enchantables: Ordinary things like the coffee machine or umbrella Augmentables: See-through things like glasses Wearables: Garment, Ornaments, things you wear Swallowables: Things you can swallow Biohackables: Things injected or added into your body.
- With social data, you can predict the wants and needs of your customers. Employees are social workers. Social Media offers the tools to interact with customers and to collaborate with colleagues.
- Services no longer coming solely from on premise servers. SaaS solutions and cloud services are part of the new IT landscape. The cloud should be the default scenario, only then to be “softened” by pragmatic considerations around integration, security, legislation and manageability. Many benefits like cost reduction, time-to-market, scalability, flexibility and usage-based pricing. Still, there are many uncertainties as well, caused by topics such as performance, security and privacy, legislation, integration challenges and governance.
- More and more devices and sensors are online, producing Big Data. Cloud is more and more the preferred platform to provide (cheap) storage for this. Analytics in real time to offer customers the best experience.
- Bring Your Own Device (BYOD), Choose Your Own Device (CYOD), consumer market Multiple platforms (iOS, Android, Windows) Multiple OS versions: iOS 6, iOS 7, iOS 8 Multiple form factors: smartphones, tablets, PC, TV, Wearables Screen resolutions Limited capabilities of devices (memory, resources, permissions, battery) / older devices Fragmentation in features: NFC Impact on development and test environment.
- Is NFC the next payment method? Google Wallet and Google Bank? What about smart watches or Google glasses? What are the possibilities of iBeacons? What will the Internet of Things bring us? How can we apply voice control?
- Data on mobile devices out of the office. Devices lost or stolen. Hybrid identity at on-premise and in the cloud. Big Data everywhere. Apps Network cannot be trusted. What data is accessible when the device is in the wrong hands (also in case the device itself is still unlocked). Services Consider the services known and accessible. User of service cannot be trusted.
- Integration with back office services on premise and in the cloud.
- Support offline functionality when needed. Robust handling of failing communication.
- Different deployment procedures for the different App Stores.
- User experience is critical. Increasing demands for user experience, performance, security, availability. Mobile presence is relevant (regular updates). Touch vs Click. Social media integration.
- Mobile development resources are difficult to find in the market.
- Mobile Access Layer (REST, API First approach). Security (device, server, application, network, data (stored, communication) Data qualifications Risk (Exposure chance and impact) Older devices more vunerable Client Security Sandbox Memory (platform API’s, keep sensitive data in memory as short as possible) Local Storage (encryption (expensive!), store on server) Obfuscation Platform abilities restriction Component signing Security Audit Log Functional security (clear profile after wrong login) MDM policies and certificate enrollments Secure communication TLS TLS/SSL Certificate Pinning Session Layer Encryption Network Security (WiFi, 2G, 3G, 4G, Bluetooth) Enterprise Security Mobile Access Layer Authentication Authorization Etc. MDM/MAM MDM: provisioning, enforce device policies Data protection: enforce encryption; device selective wipe, locate; lock risky features such as cameras , Bluetooth, SD card readers MAM: prevent or allow use of apps Mobile Device Security: blocks malware and malicious web sites
- Model-View-ViewModel pattern most suitable for high code sharing. Dependency Injection pattern ideal to realize extendable architecture.
- 3 Key Platforms (iOS, Android, Windows) and 3 Application Architectures (native, hybrid and mobile web). Native Applications: best user experience and performance, distributed via app stores Hybrid Applications: cross-platform app running in a container on all supported platforms, distributed via app stores Mobile Web Applications: web application with responsive design to support many devices, runs in browser, hosted on web server, direct deployment More info: http://www.nl.capgemini.com/bronnen/mobile-development-think-to-the-future-today
- Native Development: multiple development environments, results in higher development costs, expertise may be hard to get Using the tools and development frameworks native to the platform an organization is using. It means that the code is optimized for the platform and normally enables the client to use rich tooling assets that make advanced techniques and animation possible. This ensures that users get greater freedom in how they perceive and use it.
- Multiplatform Native Development: one development environment, shared .NET codebase with Microsoft (Windows platforms) and Xamarin (iOS and Android platforms) technology A multiplatform mobile architecture offers the possibility to create mobile applications for multiple mobile platforms and at the same time offer the flexibility to use all native functionality of the mobile operating systems to realize an optimal user experience. Combined with a powerful development environment and a comprehensive programming language it offers an excellent way to develop and maintain rich mobile applications. Core of application is shared, while navigation differs between platforms. More info: http://www.slideshare.net/eschaick/multiplatform-app-architecture
- Multiplatform Framework Development: one development environment, eg. PhoneGap (supported by IBM Worklight, SAP Mobile Platform) or Kony, shared HTML5/CSS/JavaScript codebase ‘Write once, deploy everywhere’ is the promise here, and it is one of the more popular frameworks due to its oven-ready offering. For example, it could be one UI design tool, one programming language (like JAVA), and a set of ready-to-use middleware to connect to back-end ERP systems. Another key selling point of a cross-platform strategy is that it helps to avoid technology ‘lock in’ by only providing an application for one or a few mobile platforms.
- Mobile Web Development: one development environment with shared HTML5/CSS/JavaScript codebase, UI frameworks for responsive design The key difference here is that mobile web applications are not packaged as an App for Android or an App for IOS. Instead, they are accessible via a URL in the browser bar. As you would expect, they are optimized for Mobile screen resolutions and feature detection means the Mobile Web Development can ‘see’ what platform and device it’s on and adjust itself accordingly.
- Development type determined based on requirements.
- DevOps helps in handling the Agile vs Quality paradox. Organization => Mobile Office Process => Scrum, CM, Agile People => Skills, Training Architecture => Reference architecture Technology => Tools, Frameworks, Reusable Building Blocks Reuse knowledge and components across projects and customers.
- + Collaborative development + Stability through small changes instead of avoid changes + Automation is needed for testing, cm, release management, infrastructure provisioning, deployment, other delivery steps (“Automate everything”) + Development and test in the cloud
- Innovative mobile use stories don’t redo mobile web as-is, mobile first. Define scope and requirements using sketches and mockups. Use personas and scenarios to identify relevant contextual value Collect user feedback in target groups using prototypes.
- Test cloud: DeviceAnywhere (http://www.keynote.com/solutions/testing/mobile-testing) Perfecto Mobile (http://www.perfectomobile.com/articles/deployment-options#public) Network emulation: iTrinegy (http://www.itrinegy.com/index.php/products/network-emulators/) GL Communications Network Lab (http://www.gl.com/telecom-test-solutions/communications-networking-2G-3G-4G-lab.html/)