What steps can be taken to prevent rejections from Apple or Google ? What are the best solutions for companies wishing to create their own application? During this webinar, you’ll learn about what to consider and mistakes to avoid when publishing your own app on the App Store or Google Play. cc Rakuten Aquafadas

1. How to publish an App:
tips and mistakes to avoid!
Webinar, Thursday 26th April 2018
• Stéphane Dayras, Pre Sales Director
• stephane.dayras@rakuten.com
• www.aquafadas.com

2. 2
How to publish an app: tips and mistakes to avoid!
• Apps creation & publishing workflows
• Developer accounts, administrative data & business model
• Multiple information & materials to collect (Starter Pack)
• Deployment methods
• Content regulations / Apple & Google
• Mobile OS: main updates (iOS 11, Android 8)

3. 3
• Apps creation & publishing workflows
Apple case

4. 4
• Developer accounts, administrative data & business model
• 2 developer accounts types at Apple (5 to 10 days validation):
• C A ,EEA . $ )) L
• > C I DC !/CI E $ ()) L
• . 2 C 9
• > A CI IL 9 C > A 9 C C> I D IL
• 9 I ! D C C
• Google developer account: 25$ once only (2 to 3 days validation)
• Valid developer account (payed or renewed)!
• Administrative data and pricing information (Apple)
• -DCI :I $ E D :I E : + C -DCC :I
• ,EE .$ ADE : I : I $ E D DC C> E D A
• - I D I CI E C : C CDI 9 D DC: 9 II
• Business model (free, in-app purchase, in-app subscription…) to define upfront with care!

5. 5
• Multiple information & materials to collect (Starter Pack) 1/2

6. 6
• Multiple information & materials to collect (Starter Pack) 2/2

7. 7
• Deployment methods
• Apple
• - > B > LA GM A MFB M> B >FLB B>
• / - > B > , BEMDL:F>GM DP ) :P DBEBL > :DB :LBGF
L> LA GM A , D> BF (A ML : >D> :L> LA> BF:D :DB :LBGF L> G LA> , M EB BGF
• MFDBEBL> > MB > :DB :LBGF GE , D>
• - MFDBEBL> FG M EB BGF
• GDME> M A: > G :E G > M :LBGF D: > >FL> B > LG > G E:F: >
B L B MLBGF LA GM A 4/4 LGGD
• Google
• D:P LG > > > L .ABF: 9B:GEB -:B M 4>B M
• ,DL> F:LB > LG > 1 / GB , LGB > , 4: C>L 2 E: L G D ,E: GF , LG >
• 4:F: > G B :L> , 044 4:F: > D:P LG >

8. 8
• Content regulations / Apple
• Preferred focus: entertainment, games, highly interactive and animated content…
• No commercial & marketing content, no product catalog, no price...
• Training & technical content more tolerated
• No explicit content (sex, violence, racism…)
• Secure URLs (https) recommended
• Do not mention Android or display an Android device or logo
• Do not show Apple devices in your content (iPhone, iPad…), only screenshots of the App content
• Push certificate can be applied after the App publication (has to be renewed!)
• Paid products have to be manually entered, one by one (batch processes can be created)
• Apple can change the rules at any time!

9. 9
• Content regulations / Google
• No explicit content (sex, violence, racism…), but less strict than Apple
• Content classification based on standards (PEGI, ESRB…), more restrictive, but easy
content categorisation process (the submission form will calculate the rating automatically)
• Subscriptions hard to change or delete -> need to create new ones for any update and wait
for renewals dates to apply
• Push notifications must be applied before the App submission!
• Unique KeyStore key for authentication or content cryptography generated at the first App
submission time only! To store safely, no way to gather it again after.

10. 10
• Mobile OS: main updates (iOS 11, Android 8)
• iOS 11
• ( :B
• 1 4 : B: 6 2 4 :B: B 6 : 2G6
• 9BB
• ,2B2 :D24G -, 0
• Android Oreo 8 (API level 26)
• 6 : : 6 2 96 6
• 6BB6 64 :BG 6 2 46
• 6 B 6 62 6 & ) ( :B 2B:D6 : 2 :6 : 6 B -6
• Update your App at least once a year!