Blog - Page 12

We thought about skipping the release today and going strait for a release on the day of the code freeze but this might create a situation where a regression is missed because you didn't have enough time with the code. This means we might have more than one update until the 16th release of 3.6 so please bare with us. We will release plugin updates with the code freeze and they should include the release candidate of 3.6 within them

Just a couple of weeks ago I was offering tips on how to search the website in lieu of a search engine. Having gone thru the process repeatedly and trying many different approaches and off the shelf solutions we decided to build something simple of our own and we did.

We will release Codename One 3.6 on the 16th of January, this means we will enter code freeze on the 9th during which only critical bugs will be fixed with peer review. Since Codename One is a SaaS product release cycles aren't as crucial for most of us but they provide a framework both for versioned builds and for us to focus on the more mundane aspects of product maintenence.

Auto-renewable subscriptions provide, arguably, an easier path to recurring revenue than non-renewable subscriptions because all of the subscription stuff is handled by the app store. You defer almost entirely to the app store (iTunes for iOS, and Play for Android) for billing and management.

Opening a demo or sample code from GIT is relatively easy if you are an experienced Codename One developer but for a lot of newer developers for whom samples are often more crucial this can be challenging. One of our solutions was placing the demos in the Codename One new project menu but that's probably not enough.

Happy holidays, Merry Christmas, happy new year to all. All of us here at Codename One hope you have a lovely vacation if you are taking one. Since half of our readership is from countries that celebrate these holidays it seems like a good time to take a short blogging vacation as well.

One of the fallouts from the new encrypted storage API we added last week is the fact that it encrypts things like preferences making them unusable if you expected them to work before/after encryption was applied. To workaround this we added a new API to the `Preferences` class:

Non-renewable subscriptions are really the same as consumable products, except that they are shareable across all of a user's devices. Auto-renewable subscriptions, on the other hand, will continue as long as the user doesn't cancel it. They will be re-billed automatically by the appropriate app-store when the chosen period expires, and all management of the subscription is handled by the the app-store itself.

One of the most painful aspects in any mobile app is input, besides the difficulty of viewing the details on a tiny cramped screen the input via the virtual keyboard is nowhere near the input comfort of a full fledged computer or even a tablet.

We had to push out an update to the IntelliJ/IDEA plugin to workaround an issue that started happening with their latest IDE update. The 3.5.11 version didn't change much just fixed those specific issues. Other than that this weeks release includes some new In-App-Purchase features (that we will discuss next week) and the new seamless caching API discussed yesterday.