It's that time of year here in the northern hemisphere that I find myself repeatedly searching Google for "Costa Rica relocation." However, from a glass-half-full perspective, it is a fantastic time of year to sit with a warm laptop and discover what's new with your favorite piece of the Telerik Platform. Let's take a closer look at the latest release of Telerik AppBuilder.
Before you continue, be sure to consult the release notes for all of the details that I'm glossing over in this post.
If you have logged into Telerik Platform within the last week, you may have noticed a considerable increase in responsiveness. This is because we just completed a massive migration to Amazon Web Services (AWS) for our backend infrastructure. This not only improves the reliability and performance of our In-Browser client, but also has a huge impact on our cloud-based build times (numbers based on cloud builds of our Telerik Friends sample app):
You'll also notice a big improvement with version control commands that you issue from the In-Browser client or Windows client.
As I've stated many times about past releases, we are always working on improving our device simulator. This time, we are adding support for multitouch, so you can accurately simulate pinch-to-zoom gestures. Simply hold down the
shift key and you'll be able to click and drag to simulate a pinch gesture.
It's an easy performance tweak that many hybrid developers miss. On Android 4.4+ devices, you can target a modern Chromium webview with your AppBuilder apps. This means performance improvements on modern Android devices and significantly improved HTML5 support.
These settings are applied automatically to new AppBuilder projects, but to add this setting to an existing project, open your Android Manifest and you’ll probably have a line that looks like this:
<uses-sdk android:minSdkVersion="8" />
You can change that to:
<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="21" />
This has been around for a while (since Android 4.4 was released), so if you're not doing it now, better late than never!
Everyone is hot and bothered to try out the Visual Studio 2015 Preview from Microsoft, so what better time to update the AppBuilder extension for Visual Studio to support the latest IDE from Microsoft. Plus, if you have been holding off on using AppBuilder in Visual Studio because you don't want to pay for a VS license, now is the time to jump all over the 2013 Community edition!
Visual Studio Community 2013 is a free version of Visual Studio that provides full support for plugins/extensions. If you currently use the AppBuilder Windows client, I highly recommend you take closer look at our Visual Studio extension; you'll quickly see everything you can do in our Windows client, you can do with our Visual Studio extension (and then some).
Your Windows Phone apps have worked just fine on Windows Phone 8.1 devices all this time, but we now offer full 8.1 support with this release. That means full build support for the 8.1 SDK and an updated Windows Phone Companion App.
To build for Windows Phone 8.1, make sure you are targeting Cordova 3.7+ and target the appropriate Windows Phone SDK in your project properties.
Since the last release of AppBuilder, you've been able to use Cordova 3.7 in an "experimental" state. We have finished our verification of 3.7 and are happy to say it is now an official part of AppBuilder. All of your new projects should now default to 3.7. Because the Apache Cordova team now releases slightly different versions for each platform, when we say "Cordova 3.7" we are really referencing the following platform-specific versions:
As usual, there is too much to talk about and not enough space. Here's a quick rundown of some of the other goodies we're including with this release:
Rob Lauer is a former senior manager of developer relations at Progress.
Subscribe to be the first to get our expert-written articles and tutorials for developers!