After five months of development, I am excited to announce the release of version 2.1 of IndoorAtlas’ SDK, which builds on our 2.0 SDK that was released in November 2015. We have consolidated a large number of performance improvements across the entire stack of our mobile and cloud positioning technology in this release based on field experience with our valued customers.
Highlights of this release include significantly reduced battery consumption, improvements in automatic venue and floor detection and use of some of the latest capabilities of smartphone devices from Apple and major Android manufacturers. Detailed release notes and all related technical documentation can be found at docs.indooratlas.com.
This release helps to further extend our global leadership position as the global Platform-as-a-Service leader in Geomagnetic indoor positioning, delivering scalable and accurate indoor positioning for your mobile apps. Our cloud-based platform remains freely accessible to all developers up to 100 users and our customer success team is happy to continue to help you through our platform workflow stages.
New Web Tools
We are also happy to invite customers to new web tools at app.indooratlas.com with new functionality and improved usability. These tools will remain side-by-side with our previous web tools for the time being while we collect additional customer usability feedback. Your feedback is valuable and we want to continually improve and enhance your experience. Let us know how we are doing by sending your comments and questions over the online support channel integrated to the web tools.
End of Life Notifications
Today, we are announcing the End Of Life for version 1.3 SDK, originally released in 2014. According to our usage statistics, this is a non-service-impacting end of life, with no remaining live customer applications on version 1.3.
Version 1.4 SDK will continue to be supported until further notice, although we strongly encourage you to update your apps to version 2.1 SDK due to improved performance. Our commitment to support previous major version extends for a minimum of six months from each end of life notice, and we will be contacting developers using version 1.4 separately to discuss upgrade timelines.
// Osma Ahvenlampi, SVP Engineering