In early 2016, the Java compiler looked like a better bet and we went forward with it.
Jrebel android android#
We had the option to pick between working on the Java compiler or Android resources packaging. We also saw a drop-off in product sales, with many deals lost because the product wasn’t fast enough. Eureka, it worked!īut we knew this wasn’t enough. We did quite a clever trick: By starting the Gradle task in the background, it would complete the configuration phase and continue once the user decided to “Apply changes”. This is the time needed to generate the Gradle tasks and understand the project layout. The first to tackle was configuration time. We gained new visibility and presence in the Android community.īy this time, we had discovered that a lot of the steps in build process were not incremental. Google had just announced Instant Run in Android Studio and we felt the need to react. We adjusted our Individual license pricing to increase the market presence.
Jrebel android for android#
In late 2015, we also decided to launch JRebel for Android 1.0. JRebel for Android 1.0, Looking into the Build Process But we knew that we’d need to look into the build process a lot more. We worked hard to reduce the initial installation overhead. Once bigger companies started adopting the tool, the hard reality of slow build times started to hit us. The first sales came in very quickly.Ī lot of those deals came from existing JRebel customers. Our initial offering consisted of annual Individual and Business subscriptions. By autumn 2015, we had the confidence to start figuring out the go-to-market plan. We gathered feedback and sent out Beta invitations in regular batches. Back then, we didn’t focus on what happens before in the build process.
Jrebel android code#
We spent the late spring and summer of 2015 to get our code reloading technology on Android as solid as possible. It was by far the most successful beta launch we had with almost 1000 sign-ups registered in the first 24 hours.
By spring 2015, we had moved to Android Studio and Gradle, and announced our private beta program. Our very first proof of concept worked on Eclipse and ANT projects. JRebel for Android started three years ago with the porting of our legacy JRebel core to Android.
Looking for the latest version of JRebel?ĭOWNLOAD NOW The Journey of Android With JRebel Beta Programs For those who are interested in the history, here’s a recap of how JRebel for Android came to be. We would like to thank everyone who has been part of this awesome journey for the past three years. However, we will not be building new features or working to further optimize the build process. We will continue integrating new Android Studio, Android Gradle Plugin, and Gradle versions throughout this time. And, as promised, we’ll also continue adding annotation processors for our Enterprise customers. However, we will not be accepting any new users.Įnterprise license users can continue using JRebel for Android until the license expires. All JRebel for Android Free version users can continue using the product until March 31, 2019. Hi, I’m Sten the Product Manager of JRebel for Android.Īs a team, we’ve made the decision to halt active development on JRebel for Android.
0 kommentar(er)
