The new support and license extension site is now available.
As promised the new extensions are available through the site and all have had the server check removed. Each of your applications will now be completely independent of our servers.
To get started with the new site you should:
- log in with your GitHub account
- import your old developer key to get access to your extensions and a free support period!
- generate application keys for your applications
- and get developing!
Each of the extensions now has a dedicated area and we are planning to further expand these areas with getting started guides, screenshots, code snippets and FAQ's. Check out the Adverts extension here.
Get started now airnativeextensions.com.
As part of our review of our support and licensing model we have taken your advice and concerns on board and are currently redeveloping our entire system.
Over the coming month we will stop selling the extensions in their present form and be migrating to a new licensing and support model.
The new model will be as follows:
- All server checks removed, each of your applications will be independent of our servers, forever
- Updates and support will now be part of a yearly subscription, with discounts after the first year
- There will no longer be a developer key, instead each application will have a unique application key
- Application keys, subscriptions and support will all be managed through our new extensions site
Support Site //
The new site will be the gateway for all information, support, tutorials and subscriptions.
We have taken great care in putting together a site that will be easy to use and give you quick access to detailed information, documentation, tutorials and support on each of the extensions.
We will be introducing a getting started guide for each extension along with code snippets, screenshots (where applicable) and FAQs.
Migration Plans //
For customers who are using the existing extensions you'll be able to continue using them just as you have in the past and none of your published applications will be affected. If you don't wish to update then you can keep using the current extensions.
We will stop updating the current GitHub repository and will be migrating to separate repositories for each extension. The current repository will be shut down early next year.
When you are ready to update to the new system, you'll need to log into the new site with your GitHub username and import your existing developer key. This will give you access to the new repositories and support for the extensions you currently have access to.
Current extensions will no longer be available for sale: 3rd December 2014
New support and license site will become available: 12th December 2014
Existing GitHub repository will be closed: 12th January 2015
We also want to show off your applications and what you’ve used our extensions to build. So if you have an application you’d like us to showcase on the site please send through some information including video or screenshots and a summary of the application and we'll put it up on the site.
As of today, we've released an important update to the NativeMaps ANE.
Summary of features
- Android 4.4 (KitKat) visibility problems fixed (see below for information)
- Added functionality to get BitmapData of map view in Android
- Android NativeMapEvent.MAP_CREATED event should now be more reliable
- Important: New meta tag required for Android descriptor (see below)
Android 4.4 fixes
The main addition is a fix to resolve problems with the map visibility on devices running Android 4.4 (KitKat). Using the new version of the Android NativeMaps ANE (version 2.0), maps should now be visible on KitKat devices.
Unfortunately there is a downside to this, because of the change in z-order rendering required, the UI buttons on the map will not be visible in KitKat. This includes the zoom controls and the user location control buttons which normally appear above the map. It's recommended to provide additional UI controls in your application if these buttons are required.
Android BitmapData now available!
Retrieving a BitmapData object of the map view is now possible in Android. The old method (for iOS) drawMapToBitmapData() is now deprecated in favour of the new method requestMapBitmapData().
You should now listen for the new event type NativeMapBitmapEvent.READY, and retrieve the BitmapData object from the event payload. This is standard across iOS and Android now.
It's strongly recommended to use the AIR 4.0 SDK or newer for your application. The fixes for the NativeMaps ANE on Android may not work correctly for older versions of the AIR SDK.
New meta tag required for Android descriptor
As of this version, you must now include an additional meta tag in your descriptor XML. The following entry should be added inside the section of your Android manifest. You can place it below the google maps API key entry.
<meta-data android:name="com.google.android.gms.version" android:value="4030500"/>
Also, you must ensure that your Android manifest permissions include android.permission.ACCESS_NETWORK_STATE
As always, please let us know if you encounter any problems!
Following shortly after the announcement that Google acquired the company behind the Bump API (read here), the company has announced that it will be shutting down the service.
Dear Bump SDK users,
We are writing today to inform you that we will be discontinuing the Bump SDK and API effective January 31, 2014. As you may know, the Bump team recently joined Google, and the Bump SDK team is focusing its efforts on new and exciting projects within Google.
The SDK will be closed for new downloads beginning today. We will continue to support the SDK functionality for the next three months, through January 31, 2014. After that date, the Bump SDK/API will no longer function. We hope this will give you ample time to alter your apps and remove Bump functionality.
We are sorry for any inconvenience this may cause you. Thank you for your support and feedback over the years.
- The Bump Team
We just want to remind you to make sure you've addressed this in your applications as the service goes offline in a fortnight.
For more information head to the company website or the google group.
We had some great entries in the competition, so many good ideas out there and it's great to see the AIR community still embracing the platform.
However being the geeks that we are can't help but encouraging experimentation and we'd love to see what comes out of a combination of AIR, arduino and Kinect!
Congratuations @theguaz !
Thanks everyone for your interest, and checkout the latest extensions here.
Update: The competition is now closed. We'll be announcing the winner soon.
Do you want to win a license for the full ANE package?
We're giving away a full license and copy of our complete native extensions package. All you have to do is follow us on Twitter, and post a tweet with the hashtag #distriqtANE telling us what you'd make with the extensions.
Make sure to include the competition hashtag to be in the running!
1. Follow us!
2. Tweet it!
This competition will run from the 18th of November 2013 until the 2nd of December 2013, in Australian time (AEST). We'll select the most creative idea posted, and the winner will be provided with a full license key for the package.
After over a year of trying to handle support through email we've finally got a forum, feature requests and knowledge base up and running for the native extensions.
We'd love all our users to check it out, enter any suggestions for future ANE's, and to discuss any questions you may have regarding the use of the ANE's.
We've tried out several solutions and have decided to use the awesome Uservoice platform. We're hoping this will improve all our native extension users experience with our support and help you to get going with the native extensions faster.
We generally use Starling & Feathers to build most of our iOS and Android apps these days. The performance of Starling is great, and while Feathers is mostly aimed at game development, it's an awesome framework for building regular apps as well.
Recently we were building an app which also used our NativeMaps native extension (check it out here: labs.distriqt.com/native-extensions)
One issue with this, however, is that because of the way Starling runs on the GPU, it severely affected the interaction and performance of the native maps interface on iOS. (I'm not sure of the effects on Android, but we used the same technique here across platforms.)
This post is a rough guide to the way we worked around the problem in order to get better performance from the map UI.
Continue reading Using the NativeMaps ANE with Starling/Feathers
Open House Melbourne is a not-for-profit association that runs annual events providing the public a free and rare opportunity to discover a hidden wealth of architectural, engineering and historic buildings nestled around the city.
As part of a sponsorship for Open House Melbourne 2013, distriqt developed an iPhone and Android mobile app to support the event.
As we are partly based in Melbourne, this was a great opportunity to show our support and love for the city, and help give this great not-for-profit event a new way to reach over 100,000 of the public who will attend this year.
The app features a full list of over 100 buildings which are open for tours, an interactive map, a personal itinerary plus social integration with Twitter and Instagram and more.
We'd like to thank Cornwell (http://cornwell.com.au) for the visual design, and efront (http://efront.com.au) for their support.
If you're in Melbourne on July 27-28, grab the app or a printed program and check out some of the great buildings and architecture in Melbourne.
Visit the OHM 2013 Website
You can also find the Android version on the Google Play Store
All applications as of the 1st of May must now support the iPhone 5 resolution.
iPhone 5 Optimization Requirement - Your binary is not optimized for iPhone 5. As of May 1, all new iPhone apps and app updates submitted must support the 4-inch display on iPhone 5. All apps must include a launch image of the appropriate size. Learn more about iPhone 5 support by reviewing the iOS Human Interface Guidelines.
There is a little trick to get your AIR application to use the new resolution, you need to include a new Default image, otherwise you're application will always appear in the iPhone 4's resolution.
This new image must have the following:
640w x 1136h
And make sure you package it with your application.