Hidonix’s October 28, 2026 announcement set November 2 as the start of commercial integration for ION SDK 2.0 on iOS and Android through technology partners. The useful planning distinction is between avoiding dedicated positioning hardware and avoiding all preparation at a venue.
Hidonix’s October 28 SDK 2.0 announcement
Choose the method before estimating the work
The release says partners can use geomagnetic positioning, the new Visual Positioning System, or both. VPS uses physical visual markers at known venue locations, with corresponding positions defined on the floor plan in the ION Content Management System. Existing compatible beacons are optional. Those details matter when interpreting the company’s infrastructure-free description.
Ask the integration partner to identify the method proposed for each area, the preparation it requires and who maintains it. The announcement describes automatic fallback when both positioning methods are used; it does not establish performance in your building. Request confirmation of partner access and the SDK version before treating the announced date as a completed integration.
Put the venue assumptions on one page
ION’s CMS page describes map preparation, validation and simulation before deployment. For an evaluation discussion, create a short record that separates the proposed setup from what has actually been observed. The following worksheet is an original planning suggestion.
ION CMS: mapping preparation and validation
- Scope: name the floors, rooms and visitor routes included in the proposed evaluation.
- Preparation: list the mapping work or marker placement the partner says is required.
- Ownership: assign responsibility for approving locations and maintaining the venue record.
- App: record the phone models, operating-system versions and exact integration build used.
- Evidence: keep observations and unresolved questions beside the setup that produced them.
Try a fictional museum planning exercise
Imagine a fictional museum considering navigation between its entrance and two galleries. The team asks its partner to mark the proposed evaluation route on the current floor plan. It then records which areas would use visual positioning, geomagnetic positioning or both, without assuming the same choice applies throughout the building.
Before any demonstration, the team agrees on what it wants to observe: whether the app starts in the intended area, whether displayed progress follows the agreed route and how exceptions are recorded. It keeps unsuccessful attempts in the review notes. These are evaluation questions, not measured ION results or instructions for a safety-critical navigation system.
Budget the defined project
Request an itemized proposal covering integration, venue preparation, maintenance and support. Keep any recurring charge beside its stated billing basis, and ask what changes when the planned space or usage changes. Leave missing prices unknown instead of estimating them from a general product description.
An announced availability date is a useful starting point for a partner discussion. A documented venue plan makes the discussion specific enough to review. No ION SDK, phone application, marker installation, navigation accuracy or fallback behavior was tested for this guide.