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

Most Favorite Posts

Server-driven UI (SDUI): Meet Zalandos AppCraft and AirBnB Lona

A short WTF: Joe Birch:  SERVER DRIVEN UI, PART 1: THE CONCEPT Zalando seems to follow the SDUI principle as well - defining a common design language and construct the screens on the backend while displaying them natively on the clients. They even go one step further; they implemented a mighty toolset to enable non-technical stakeholders to define their own native app screens Compass: Web tooling to create screens and bind data Beetroot: Backend service that combines the screen layout definition with the data Lapis/Golem: iOS/Android UI render engines Crazy cool! Good job, guys (when you do an open-source release?) To even move faster a Flutter based UI render engine implementation was great! See also AirBnB Lona SDUI approach Building a Visual Language Why Dropbox sunsetted its universal C++ mobile project and AirBnB its React Native implementation

Xamarin and MvvmCross

Xamarin Create Native iOS, Android, Mac and Windows apps in C# Xamarin delivers high performance compiled code with full access to all the native APIs so you can create native apps with device-specific experiences. Anything you can do in Objective-C or Java, you can do in C# with Xamarin. Xamarin MvvmCross for Xamarin This project provides a cross-platform mvvm mobile development framework built on top of: Silverlight for WP7, WP8 Mono for Android (or Xamarin.Android) MonoTouch for iOS (or Xamarin.iOS) the WinRT XAML framework for Windows 8 Store apps. WPF Mono for Mac (or Xamarin.Mac) This project makes extensive use of Portable Class Libraries to provide maintainable cross platform C# native applications. GitHub

Judo App - Server Driven UI out of the box

Judo App Judo brings server-driven UI to your iOS and Android apps. Build user interfaces visually in a fraction of time and publish them instantly without submitting to the app store. Build Experiences - With No Code The Judo app for macOS, available through the App Store, is built for design professionals with common keyboard shortcuts and familiar concepts like canvas, layers and inspector panel. Workflow is streamlined with the ability to drag and drop media files directly into your experiences and manage your own Judo files in Finder. Manage Creative Execution A Judo experience is interactive and can include text, images, video and buttons. An experience may be part of a screen, a single screen, or more typically multiple linked screens. Judo supports screen transitions, carousels, horizontal scrolling and modals. Clients can add custom fonts and define global colors and these are updates applied universally. Effortlessly Deploy Judo Cloud syncs your experiences with your iOS and ...

iPad HTTP Debugging with Charles

After noticing that the caching in iPad Safari seemed a little funky, I made an effort to decipher some of the logic used by the browser cache. I didn’t get very far, but in the process I figured out how to route my iPad HTTP traffic through a web debugger on my laptop. It turns out it was very easy to do (although I’m sure there is a more complicated way to go about it). What follows is a simple step-by-step for connecting your iPad to an HTTP debugging proxy. The main requirement is that your desktop/laptop and iPad be on the same wireless network. Then it’s just a matter of telling your iPad to use your desktop as an HTTP proxy. iPad HTTP Debugging with Charles
LazyPages is a highly customizable library that helps you to show a scrollable list of view controllers synchronized with an index. It is written in Swift 2.2 for iOS 8+. Like Scrollable Tabs in Android. GitHub