An indoor map stops being portable when every chair, desk, or fixture still depends on a private model URL.
KiMap exports now keep furniture metadata in kidata.furnitures and model content in kidata.models. Each furniture item points to its embedded model through modelRef, so the Vue 2 SDK can parse OBJ, FBX, GLB, or glTF content from memory and restore position, rotation, scale, size, and material settings without a separate furniture server.
The compatibility requirement mattered just as much as the new path. Existing integrations can continue providing a .kimap URL, while upload-driven applications can pass kimapContent, kidataContent, and kithemeContent directly.
The SDK is MIT licensed:
https://github.com/zyl19950114/kimap-vue2-sdk
You can test the editor example without signing in:
https://www.kimap.cc/editor/example?utm_source=devto&utm_medium=article&utm_campaign=early_access&utm_content=sdk_followup
The most useful feedback is specific: which model format, loading lifecycle, or scene-performance limit would block your integration?
Top comments (0)