SDK 3.7 Release Information

2025-03-14

Accessible Wayfinding and more

This update introduces accessible wayfinding and the ability to use custom tags for routing, expanding wayfinding use cases. Custom tags allow you as a developer to implement a plethora of wayfinding use cases. For example, a staff_only tag could guide visitors and employees through the same wayfinding graph while restricting certain routes for visitors.

Additionally, new venue-specific remote configurations enable optimizing SDK performance for individual venues without requiring changes to the app code and allowing performance tuning after application releases.

As a summary, SDK 3.7 has these new features:

  • Accessible wayfinding support
  • Improved remote SDK configurability for specific venue needs
  • Improved enterprise SDK configurability
  • External storage API
  • Bug fixes and performance improvements

SDK 3.7 also brings together all the updates and hardening done from 3.6.0 to 3.6.11, including

  • Support for WiFi RTT / FTM
  • API for using 3rd party wayfinding routes
  • Beacon and WiFi scan callbacks
  • Improvements to Low Power beacon fusion

Wayfinding Editor

You can now use IndoorAtlas Web App to define accessibility criteria for edges of the wayfinding graph. Currently, the editor supports tagging edges as:

  • Inaccessible (e.g., areas not suitable for wheelchairs)
  • Accessible-only (e.g., special elevators designated for wheelchair use)

By tagging edges in the IndoorAtlas Web App, you can customize navigation routes based on accessibility needs. This feature can be tested in the web tool, ensuring a seamless experience for all users.

Defining Accessible edges for wayfinding graph