Last update 31 JUL 2026

Navigine Summer 2026 Release: OpenLayers 10, SDK 2.26 & Scopes

image

Learn how the latest Navigine Summer 2026 releases enhance your spatial mapping and tracking ecosystem. From OpenLayers 10 web rendering and SDK v2.26 refactoring to granular location-based scopes and accelerated route optimization, this post covers everything you need to know about our latest updates.

TL;DR

  • Upgraded Web Client Architecture: Navigine Web Client now runs on OpenLayers 10, bringing targeted route re-rendering, snappy single-direction route arrows, action history (undo support), and Shift-lock drawing for 90° horizontal/vertical line precision.
  • Refactored Cross-Platform SDKs (v2.26.0–v2.26.2): We migrated from legacy Djinni support libraries to a modern, unified common binding runtime. Highlights include map object icon clustering (ClusterMapObject), native Swift Package Manager (SPM) support for iOS, and direct Maven Central publishing for Android.
  • Granular Location-Based Scopes: Enterprise administrators can now restrict team members to specific physical locations within a single application. Scopes are enforced across backend APIs, JWT tokens, and the Team management UI.
  • Routing & Tracking Engine Acceleration: QRouter now limits TSP route calculations to a strict 1-second timeout and collapses duplicate shelf coordinates. Tracking reports gain custom image overlays and an early preview of 3D location views.

Release Overview: What Shipped in Summer 2026

This update breakdown details technical releases shipped across the Navigine platform during June and July 2026. It covers major performance upgrades to our core web map editor, architecture changes across our mobile SDKs, and enterprise security features that make managing multi-building venues simpler and more secure.

This post is for software engineers, product managers, system integrators, and enterprise solutions architects who build, maintain, or manage indoor positioning and RTLS software on top of Navigine infrastructure. Whether you integrate our SDKs into mobile applications or operate our web tracking console, this article provides a complete overview of what has changed and how to leverage these new capabilities.

Why Core Mapping Architecture and Access Control Matter at Scale

As enterprise indoor tracking deployments scale across thousands of square meters, small inefficiencies in rendering, memory management, and access control compound rapidly. A map editor that re-renders every path vector during an edit slows down operators; a mobile SDK with rigid binding wrappers increases app bundle bloat and memory footprint; and open access permissions across multi-building campuses introduce compliance and operational risks.

Addressing these friction points requires structural improvements across the entire software stack. By upgrading our rendering engine to OpenLayers 10, completely rebuilding our cross-platform binding layer, and embedding location-level security scopes directly into JWT session tokens, Navigine provides a faster, lighter, and more secure foundation for indoor location-based services.

Key Platform Upgrades Breakdown

Navigine Summer 2026 Release: OpenLayers 10, SDK 2.26 & Scopes

1. Web Client & Map Editor Enhancements

With the upgrade to OpenLayers 10, map editing in the Navigine Web Client is significantly faster and more responsive. When modifying routes, the map engine no longer executes a full redrawn cycle of the entire canvas—only the updated route vectors are re-rendered. Single-direction route arrows now render faster across dense path networks.

  • Axis-Snapping (Shift-Lock): Press and hold the Shift key while drawing routes, barriers, or zones to construct strictly horizontal or vertical 90° lines. This allows you to draw straight corridors and rectangular zones effortlessly.
  • Action History (Undo): You can now use standard undo operations on all route editing tasks, preventing accidental deletions during floor plan adjustments.
  • Integrated Map Element Search: Click the new Search button in the map view toolbar to instantly locate specific transmitters, venues, cameras, and sensors across active floors.
  • Unified Interface Controls: The main map editing button has been standardized as Tools. All navigation drawers feature smooth open/close animations, and location/floor/app selectors have been unified across all administrative tabs.

Navigine Indoor Navigation Kit

Try all the possibilities of indoor navigation with the Navigine Demo Kit!

Indoor navigation solution

2. Mobile SDK Architecture Refactoring (v2.26.0–v2.26.2)

The 2.26 release family introduces a major structural refactoring of our mobile developer kits. We removed the legacy vendored djinni_support_lib and replaced it with a streamlined common runtime library that owns target platform binding infrastructure across Android JNI, iOS Objective-C++, and Flutter FFI.

  • iOS Integration (Swift Package Manager): In addition to CocoaPods, you can now add the iOS SDK directly via SPM. Open Xcode, select File > Add Package Dependencies, and point to the official Navigine GitHub repository using Package.swift.
  • Android Integration (Maven Central): Android build scripts no longer require custom binary downloads. Reference the official Android SDK artifacts directly from Maven Central inside your project-level build.gradle file. Javadoc artifacts are hosted on JitPack.
  • Flutter Integration (Pub.dev): Update your pubspec.yaml file to pull the latest navigine package from pub.dev. The package utilizes new Flutter FFI binding wrappers under navigine/bindings/flutter/ with native finalizable handles.
  • Map Icon Clustering: To handle dense map icon layouts, initialize ClusterMapObject and ClusterMapObjectController in your code. The SDK will automatically group nearby icons into clusters, improving frame rates and visual clarity.

The updated bindings also feature automated listener lifetime management. Event listeners generated via Djinni bindings now automatically unsubscribe expired listeners in the background, eliminating memory leaks caused by lingering event subscriptions.

UWB vs. BLE: Technology Guide 2026

Everything you need to know to choose the right indoor positioning technology for your business — no engineering degree required.

UWB vs. BLE: Technology Guide 2026

3. Granular Location-Based Access Controls (Scopes)

Managing access control across multi-facility enterprises no longer requires creating separate accounts or applications for every building. Administrators can now assign Location Scopes directly to individual users within a shared application environment.

To configure location scopes for your team, navigate to the Apps page in the Navigine Web Client, select the Team tab, and use the multi-selector dropdown in the new Scopes column to pick authorized locations.

Under the hood, the authorization engine attaches a scopes: { locations: number[]; } object inside the JWT token's activeApp payload during login. Strict authorization checks are enforced across all primary API endpoints (including /locations, /sublocations, /elevations, /routes, /transmitters, /venues, /zones, and /navigation-logs). If a user attempts to query a location outside their assigned scope array, the API responds with a 401 Access Denied error code.

4. Accelerated Route Optimization & Tracking Overlays

For warehouse, industrial, and retail environments that process massive route optimization queries, our backend routing engine (QRouter) has received targeted speed improvements:

  • Duplicate Position Collapsing: The routing engine automatically identifies and merges duplicate item coordinates (for example, multiple order items located on the same rack with identical priorities) before passing them to the solver.
  • Engine Timeout Caps: A strict 1-second execution cap is now enforced on the Travelling Salesperson Problem (TSP) optimization engine. This prevents high-volume route requests from stalling execution queues.
  • Custom Store Thresholds: Adjusted route optimization thresholds (minPointsToOptimize) have been rolled out across enterprise client accounts to ensure optimal balance between calculation speed and path accuracy.

Additionally, our Tracking Web Application now supports image overlays across tracking history views and map-based report screens, alongside an early preview of 3D location visualization for primary administrators.

Navigine Tracking

Navigine Tracking

A location-aware platform for Digital Transformation of Enterprises.

Real-World Application Scenarios

Scenario 1: Rapid Map Editing for Large Logistics Venues

A logistics manager needed to update picking routes across a 40,000 m² warehouse with over 150 storage aisles. Using the upgraded Web Client with OpenLayers 10, the manager uses Shift-lock drawing to rapidly draw long, perfectly straight barrier lines along storage racks. When adjusting route connection nodes, targeted vector re-rendering updates only the modified paths instantly. If a line is drawn incorrectly, pressing Undo reverts the change immediately without requiring manual vector deletion.

Scenario 2: Modernizing Mobile Apps to SDK v2.26

A software engineering team building an Android and iOS app for a healthcare campus needed to upgrade their mobile codebase to support icon clustering for thousands of medical asset tags. With SDK v2.26, the iOS engineer imports Navigine directly through Xcode's Swift Package Manager, while the Android developer adds the Maven Central dependency to build.gradle. They implement ClusterMapObjectController in less than ten lines of code to group dense markers cleanly.

Scenario 3: Multi-Facility Enterprise Access Control

A regional facility management company uses a single Navigine application to manage indoor positioning across ten separate corporate office buildings. The system administrator opens the Team management page and configures Location Scopes for each site manager. When a site manager logs in, their JWT token contains their specific location scope array. The Web Client UI automatically filters out all unassigned buildings, and direct API calls to unauthorized location IDs return a 401 Access Denied error.

What to Do Next

To start using these updates across your projects, log in to your dashboard at navigine.com and test out the new map editing tools in the Web Client. Try drawing new route vectors using Shift-lock drawing and test the integrated map search bar.

If you maintain mobile apps built on Navigine, review the SDK v2.26 release notes on GitHub, update your dependencies via SPM, Maven Central, or Pub.dev, and implement ClusterMapObject to optimize icon rendering performance. For enterprise administrators, navigate to the Apps > Team tab to configure location-based scopes for your team members today.

img

Not sure which tracking technology you need?

Every facility is different. Tell us about your project and we will recommend the right technology in under 3 minutes.

Start audit

Related News

  • Navigine Summer 2026 Release: OpenLayers 10, SDK 2.26 & Scopes Technology
    03 AUG 2026 Published: Pavel Tychinin

    Navigine Summer 2026 Release: OpenLayers 10, SDK 2.26 & Scopes

  • Bluetooth Low Energy Applications: A Deployment Guide Technology
    13 JUL 2026 Published: Tom M.

    Bluetooth Low Energy Applications: A Deployment Guide

  • How to Boost Operational Throughput with Indoor Positioning Technology
    03 JUL 2026 Published: Tom M.

    How to Boost Operational Throughput with Indoor Positioning

Join our community in social media

icon

Your request has been received. Thank you!