This document discusses several topics related to mobile app development for e-commerce/marketplaces including whether to use native or hybrid apps, tools for data analytics, payment integration, push notifications, handling downtime, and following a scalable release process. It provides examples of analytics tools like Flurry, Google Analytics, and Mixpanel and payment services like MOLPay, iPay88, and PayPal. It emphasizes testing releases internally before publishing publicly and communicating with users about maintenance to avoid bad reviews.

1. Mobile Development
for E-Commerce / Marketplace

3. Native vs Hybrid
What is your main product? The app or the content?

5. Network speed
LTE, 3G, Edge

6. Tools for Data Analytics
flurry, mixpanel, GA, crashlytics

7. flurry
GA
Mixpanel
Aggregator
(e.g:
Segment)
Mobile App

8. Payment integration
molpay, ipay88, paynamics, paypal

9. Payment
Gateway
Mobile App Payment Service
CC
token
token
Tokenisation

10. Push Notifications
no spam, almost real-time notification

11. Keep configurable in the
backend

12. Cloudbox
service
- versionized
- simple json file
- Mobile app requery new version every N minutes
API Service

13. Downtime / Maintenance /
Major upgrade / Backward
compatibility

16. Tell user what happened
Otherwise it leads to bad review, less rating

18. Release process

19. - Essam just added a new feature
- He build the Test App against
production, and internal release with
fastlane (uploaded to S3)
- Manual and automation test is
being run
- Passed the test, then publish to itunes
store. Beta release to internal, find
bug etc.
- If none, publish to public.
Example of release process.

20. Scalable App
Refactor well your code, make it modular

21. Questions ?