In a fragmented mobile landscape, developing mobile applications can be challenging, especially when creating enterprise mobile applications. Targeting the wrong audience, lack of security and a good integration can introduce surprises and pitfalls along your enterprise mobile journey. During this session, we will cover those enterprise mobility challenges by explaining and exploring MADP with its benefits, such as delivering fully native apps with 60-90% re-use of code across device platforms, decreasing test time by 90% and app project costs by 40% and the possibility of building fully reusable components in JavaScript.

1. Creating Enterprise Apps
with MADP
Yakup Kalin
mobile@aca-it.be
mobile.aca-it.be

2. Yakup Kalin
Mobile Solution Engineer
@YakupKalin
mobile.aca-it.be

3. How to determine the best mobile
solution within scattered mobile
landscape?

4. I want to watch TV

5. Check our Philips TV with
Ambilight, 3D sound system, Micro
Dimming Pro and a built-in
camera.

6. Watch TV

7. Why, where, when?

8. Everyone is so busy with the HOW that
they completely forgot about the WHAT.

9. Move a company
process to digital?
Increase
productivity?
Enter the
market fast?

10. Asking the right questions.

11. Define Mobile Solution

12. Hold on!

13. Native, Hybrid, Web?

14. Asking the right questions.

17. A tailored solution

20. A satisfying solution

21. For example (company A):
Target Android and iOS devices, good UI,
awesome UX, Secure and full device API.

23. Native

24. Lets start!

25. Oh we almost forgot:
Enter market fast, and I don’t have a lot of money to
spend.

26. Native experience
Not so expensive
Deliver fast
Enter the market fast

28. MADP

29. Mobile Application
Development Platform

30. Rapidly build,
test and deploy
mobile apps

31. Appcelerator
Titanium

32. Titanium
open source
cross-platform apps

33. Appcelerator
Enterprise level
MDM/MAM/MBaaS/Analytics

34. Write once,
adapt everywhere

35. 1 x codebase

36. 1 x learning curve

37. 1 x maintenance

38. 1 x backend integration

39. 1 x error handling

40. 1 x bugfix

41. 1 x new feature

42. 1 x test coverage

43. 1 x knowledge transfer

44. 1 x repo

45. 1 x jenkins build

46. 1 x analytics

47. 3 x adaptation

48. 3 x UI/UX

49. 3 x validation

50. JavaScript,
XML,
TSS.

51. Native apps
Native components

55. Cross-platform

57. 1 x codebase

58. For multiple platforms

59. Disadvantage

60. if tablet and android,
else if phone and iOS
else if tablet and portrait
…

61. Reusability

62. Modules
Widgets
Libraries

63. Modules & Widgets

64. Widget & Module

65. Module

66. Implementation

67. Widgets

68. Full reuse of code

71. Libraries

72. Algorithms, calculations, backend
and storage interaction, helper
methods, analytics, logging, …

73. Third party modules, widgets
and libraries

74. 60-90% re-use of code across
device platforms

75. Testing
Unit Testing, UI Testing, Device testing, …

76. Jasmine
Calabash (Cucumber)
Recorded UI tests (iOS)

77. 1 x test coverage

78. Behaviour-driven
development (BDD)

82. BA/PM developers

83. Decreasing test time by 90%
and app project costs by 40%

84. Continuous integration (CI)

86. Continuous quality check

88. MADP covers
Mobile lifecycle

89. MADP elevates
Reusability

90. Key takeaways
1. Ask the right questions
2. Satisfying fit (solution - technology)
3. Cover Mobile lifecycle
4. Reuse and automate

91. 2 days : Business identification
2 days : Mobile Discovery
1 day : Strategy Report
Your Mobile HealthCheck : 4.000 Eur
Howto transformyour business ?

92. Creating Enterprise Apps
with MADP
Questions?
Yakup Kalin
mobile@aca-it.be
mobile.aca-it.be