What is Genymotion and what are its top alternatives?
Top Alternatives to Genymotion
Android Studio is a new Android development environment based on IntelliJ IDEA. It provides new features and improvements over Eclipse ADT and will be the official Android IDE once it's ready. ...
Run Android applications on any GNU/Linux operating system. Anbox uses Linux namespaces (user, pid, uts, net, mount, ipc) to run a full Android system in a container and provide Android applications on any GNU Linux based platform. ...
Run Android APKs on Chrome OS, OS X, Linux and Windows.
App.io (previously Kickfolio) is an interactive, HTML5 mobile development & marketing tool that allows customers to play with iPhone and iPad apps directly inside a web browser. ...
Genymotion alternatives & related posts
- Android studio is a great tool, getting better and bet173
- Google's official android ide101
- Intelligent code editor with lots of auto-completion35
- Its powerful and robust25
- Easy creating android app5
- Amazing Layout Designer3
- Great Code Tips3
- Great tool & very helpful3
- Built in Emulator2
- Easy to use2
- Keyboard Shortcuts are Amazing Out of the box2
- Huge memory usage4
- Slow emulator4
- No checking incompatibilities2
- Complex for begginers2
- Lags behind IntelliJ IDEA1
- Slow release process1
related Android Studio posts
As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.
Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.
Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.
After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.
After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.
Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.