More consistent short development cycles than Instant Run...a must when doing backend codehttps://www.trustradius.com/build-automationJRebelUnspecified9.891012017-08-22T15:09:51.683Z
August 22, 2017
More consistent short development cycles than Instant Run...a must when doing backend code
Score 8 out of 101
Overall Satisfaction with JRebel
It's being used by a few of our Android developers. It allows them to minimize compile/deployment time of Android apps during the development process. Android Studio has support for something called "Instant Run" but it tends to do full compiles quite a bit more often then JRebel does, so using JRebel minimizes our debug deployment time.
- Deploys all layout changes consistently (when Instant Run was initially available, you couldn't tell if the change you made to a layout was actually being tested or not).
- Doesn't require a full build as often as Instant Run when changing code.
- Works with compile time annotation libraries like Realm, etc.
- Launch times are where JRebel is slower than Instant Run.
- Sometimes, it has incompatibilities with how you wrote something and causes compile failures, but Zero turnaround is quick to respond.
- Andriod Studio
Hot code swapping doesn't have many players...it's mainly JRebel. We use JRebel a lot in our backend code development where it minimizes our development cycle (20min down to 30sec). For Android, the competitor is Android Studio's Instant Run which works fairly well now. For smaller apps, Instant Run is faster deploying but needs more full builds. With JRebel, you hardly ever need to do a full build.