Get your mobile app in production in 3 months: Native and Reactive Mobile Apps
-
Upload
ackee -
Category
Technology
-
view
247 -
download
1
Transcript of Get your mobile app in production in 3 months: Native and Reactive Mobile Apps
This is our CEO with our Mascot
Which has been stolen on SpaceShack opening party
We take Unicorn rights seriously see www.whostolemyunicorn.com
What we use(d) for mobile success
Native languages for development
FRP principles
CI with automatic builds
Sketch graphics
Merge Requests
Experience
Why alternatives like RN or Xamarin aren’t there?
Might look like a speed up but you might hit few roadblocks
Missing functionality / features
Locked with libraries
Human resources limitation
FRP Principles
2.5 years of experience in Ackee
both iOS and Android
now even on backends
this part will be very brief … topic is very complex to be covered
Imperative vs Functional programming
map, reduce, filter, flatMap
If a pure function is called with the same arguments, the same
result will be returned. Implicit parameter is time
declarative, "Pull-based", eliminates side effects, avoids
changing-state and mutable data
Advantages
Streamlined dataflow
Same implementation across all platforms
Reusable blocks
Less bugs
Faster for development
Error handling
How we use it
Reactive Extensions - available on github
Network
Data
UI bindings
Modern architectures (MVVM / MVP)
Continuous Integration
Time efficient
Testers and clients get their builds without programmer
For white-labeled app it’s must have
Completely build on Fastlane
Lint (static code analysis)
Git workflow & MR
Branches makes development easier
Merge requests are very useful tool to learn from and how to find bugs
Key outcomes
Development is complex process, each part it makes difference
Choose good technologies and team
Applicable on each app not only our festival app