Professional Documents
Culture Documents
Mobile Apps Governance Basics
Mobile Apps Governance Basics
Mobile Apps Governance Basics
Presented by:
Kevin Bertholio – Kevin Castel - Gregory Brunet - Emmanuel Chabani -
Christine de Changy - Ashwath Desai – Peter Mo -Thierry Rutgé – Priya Shekar
• Mobile apps governance for customer facing apps, co-led by IPO/CE & GM/DCE with strong support from DCES,
IPO/EA, PSO, GM
• with low consistency in terms of UI, branding, architecture, poor cybersec, and too many publisher stores
mySchneider
Wiser
We are simplifying our We are creating names We have identified We have a future
Portfolio of Brands and to build multi-screen untapped marketing proof naming
Ranges – not only for the experience. opportunities on App Store architecture for all the
apps but also for our Offer and Google Play. future offer.
and Services for Partners.
mySchneider
Wiser
We are simplifying our We are creating names We have identified We have a future
Portfolio of Brands and to build multi-screen untapped marketing proof naming
Ranges – not only for the experience. opportunities on App Store architecture for all the
apps but also for our Offer and Google Play. future offer.
and Services for Partners.
mySchneider
Wiser
We are simplifying our We are creating names We have identified We have a future
Portfolio of Brands and to build multi-screen untapped marketing proof naming
Ranges – not only for the experience. opportunities on App Store architecture for all the
apps but also for our Offer and Google Play. future offer.
and Services for Partners.
mySchneider
Wiser
We are simplifying our We are creating names We have identified We have a future
Portfolio of Brands and to build multi-screen untapped marketing proof naming
Ranges – not only for the experience. opportunities on App Store architecture for all the
apps but also for our Offer and Google Play. future offer.
and Services for Partners.
Before After
User interface
design
guidelines
The ergonomics and
graphic rules
to apply
• Tech Stack
• Requirements
• Recommendation
• =S= Architecture pattern SCHNEIDER ELECTRIC
Contacts:
elia.reininger@schneider-electric.com
kevin.bertholio@schneider-electric.com
PRIVACY
SECURITY
Code Scanning
Penetration Testing
Final Testing
SERVICES PROVIDED BY GSL (PENTESTING)
Penetration Test for
Web/Cloud Applications
Mobile
PC Software
OT
http://pso.schneider-electric.com/wiki/index.php/Global_Security_Lab
FULL SPRINT (6 WEEKS)
understand the product, testing the product with methodology consolidating results +
meeting with dev team + writing word document making presentation
final results
kick-off first run intermediary report final results
(meeting)
Information
Vulnerability Analysis
Gathering
Forensic
Static Analysis Dynamic Analysis
Methods
Exploitation
The first step is to define where you mobile application must be published.
It depends of the phase in which your application is:
HockeyApp is a good way to collect live crash reports, get feedback from your users, distribute your betas, and analyze your test coverage. It
makes it the Schneider Electric choice for the tests made during the development phase of your application.
- User Acceptance Testing *: Apple App Store & Google Play Store (Through the Beta & Alpha dedicated areas)
The UAT phase must be done with real users, not only Schneider Electric employees.
The application will be published on the official public store accounts. Each account (iOS AppStore & Android Google Play Store) have a place
allowing you to push a build and invite users to test it.
It remains private and your application is not visible to all during this phase.
The public productions are the official Apple and Google Stores, it makes your application visible by all.
Schneider Electric own an official publisher account in both.
- B2B Production *
- iOS: Apple Volume Purchase Program (https://developer.apple.com/programs/volume/b2b/)
- Android: Google Play for Work https://developer.android.com/distribute/googleplay/work/about.html
Distributing mobile applications for B2B means distributing the apps privately to an SE customer that will make this application available
internaly for his organisation, in that case Schneider Electric is the Developer.
The targeted account must be owned by the SE customer, created with his own DUNS Number.
Prerequisite:
In any case, your application must be signed with a certificate and a provisioning profile (mainly for iOS apps).
Depending on the purpose and on the targeted publisher account, the files and user accounts will be different.
To make sure the publication will be accepted, please provide the following to Gregory Brunet:
Necessary time:
- Please refer to the two previous slides. The time to plan will be different depending the targeted publisher account,
to summarize it will be between 2 to 10 working days.
Downloads number is important, but is not enough to tell us if our apps are really adopted by our customers!
MY APP ANALYTICS:
• Info for >400 SE apps (Android
and iOS)
• Download
• In-app analytics (if connected)
such as usage and sessions
MARKET INTELLIGENCE:
• Competition analysis
• App positioning & ASO
• Portfolio management
• App reviews & ratings
Christine de Changy