Skip to main content

I show you mine if you show me yours first - Our current Android and iOS Stack

Something from our internal WeltN24 native apps lab:
We just setup a new app from scratch, which puts us in the nice position of incoroporating the latest frameworks an pattern.

We go for a Reactive and MVP approach. Please find below some details.
I would be happy to hear about your choices - please leave a comment!

Android iOS
OS Android 4.1 (4.0.3+) API Level 16 iOS 8
Language Kotlin 1.0, with fallback to Java where necessary Swift 2.1.1
Pattern Reactive & MVP Reactive and MVVM
Libs AndroidRx
Dagger 2
Retrofit 2
Dbflow
Glide
Crashlytics
JW-Player Gson
Interstellar
Dependency Injection (custom)
JW-Player
Alamofire
JW Player
realm.io
Carlos
BrightFutures
ObjectMapper (custom)
Testing

JUnit
Mockito/PowerMock & Hamcrest
Espresso
Stetho
Quick & Nimble
Performance Tests (custom)
CI Android Studio Analysis
Lint
Jenkins
Sonar
Dashing
Jenkins
Dashing
Crash Analysis Crashlytics Crashlytics
Code Review Enforced Code Reviews via Stash Enforced Code Reviews via Stash
Dependency/Build Gradle fastlane
Carthage
IDE Android Studio Xcode
Beta Testing Google Play Beta TestFlight
Documentation In-Code where possible
JavaDoc
Confluence
In-Code where possible
Jazzy for Documentation Generation
Confluence

Comments

Popular posts from this blog

Pattern: Riblets vs. VIPER

Engineering the architecture behind Uber's new rider app

Not being held back by our extensive codebase and previous design choices gave us the freedom where we otherwise would have made compromises. The outcome is the sleek new app you see today, which implements a new mobile architecture across both iOS and Android. Read on to learn why we felt the need to create this new architecture pattern, called Riblets, and how it helps us reach our goals.

The platforms share:

Core architectureClass namesInheritance relationships between business logic unitsHow business logic is dividedPlugin points (names, existence, structure, etc.)Reactive programming chainsUnified platform components
Each Riblet is made up of one Router, Interactor, and Builder with its Component (hence the name), and optional Presenters and Views. The Router and Interactor handle the business logic, while the Presenter and View handle the view logic.

Uber

Stetho - A Chrome debug bridge for Android applications

Stetho is a sophisticated debug bridge for Android applications. When enabled, developers have access to the Chrome Developer Tools feature natively part of the Chrome desktop browser. Developers can also choose to enable the optional dumpapp tool which offers a powerful command-line interface to application internals.

Facebook Github

WireMock

WireMock is a flexible library for stubbing and mocking web services. Unlike general purpose mocking tools it works by creating an actual HTTP server that your code under test can connect to as it would a real web service.

It supports HTTP response stubbing, request verification, proxy/intercept, record/playback of stubs and fault injection, and can be used from within a unit test or deployed into a test environment.

Although it’s written in Java, there’s also a JSON API so you can use it with pretty much any language out there.

WireMock.org