A1SI IoT WiFiCross-platform WiFi provisioning — brandable
A1SI IoT WiFi is a licensable, cross-platform React Native template that OEMs ship with their headless WiFi devices. Brand it, customize the device SSID, code-sign it under your own developer accounts, and put it on the App Store and Google Play as your product — with the encrypted credential exchange, platform-security hardening, accessibility, and i18n already done.
On iPhone
Your end user opens the app, finds the device, hands it the Wi-Fi credentials, and it's on the network — five plain-language steps that need no networking knowledge. The Diffie-Hellman + AES-256-GCM credential handoff happens invisibly behind the wizard; the user only ever sees progress, never a credential in the clear.
On Android
One React Native codebase renders the identical five-step provisioning flow natively on Android — TalkBack-ready and ready to code-sign and submit to Google Play under your own developer account. Android's network_security_config.xml pins cleartext to the device's local access point, so the encrypted handoff is the only thing that ever leaves the phone.
What ships in the box
The template is the boring engineering work an OEM would otherwise spend months rebuilding. License it once, and your team gets to focus on the device-specific work that actually differentiates your product.
React Native + TypeScript in one source tree (keep the rest of the sentence). Versions, if wanted at all, belong in the licensing conversation, not on the page where they will silently go stale.. Native iOS and Android builds from a single codebase, with bundle ID com.a1si.iotwifi as the customizable default.
Pure-JavaScript DH key exchange — no native crypto modules required. AES-256-GCM with a unique 16-byte CSPRNG nonce per encrypted field. NIST SP 800-38D unique-nonce discipline.
iOS ATS via NSAllowsLocalNetworking; Android network_security_config.xml pinning cleartext to local IP ranges; release-build keystore + ProGuard / R8. The template enters App Store review with the security audit already passing.
SSID 1–32 bytes, WPA2 password 8–63 characters or empty for open networks, all validated with inline field-level error messages — and validated again on the device side before the handshake begins.
Automatic device-language detection. English and Spanish ship fully translated; additional languages drop in as simple translation files with no code change.
Every interactive element carries accessibilityRole, accessibilityLabel, accessibilityState, and accessibilityHint. useSafeAreaInsets() throughout. VoiceOver and TalkBack pass on first audit.
A productized engineering offering
A1SI IoT WiFi is a licensable React Native template. License terms, customization scope, and engineering-support tiers are agreed in the engagement — talk to engineering and we'll show you the source.
Why IoT WiFi
WiFi credentials never travel in the clear. The app and the device perform a Diffie-Hellman key exchange over the device's local AP, then encrypt the SSID and the password separately with AES-256-GCM using a unique 16-byte CSPRNG nonce per field. No credentials, keys, or tokens are ever logged. The DH primitive runs in pure JavaScript — no native crypto module to maintain across upgrades, no native build surface to misconfigure.
A1SI IoT WiFi is a template, not a finished app. Customize the device AP SSID, the app icon, the splash, the color palette, the copy, and the screens — then code-sign and submit the result under your own Apple Developer and Google Play developer accounts. The end user installs your product from your account; A1SI's name doesn't appear anywhere in their flow.
The boring engineering work — crypto, network security configuration, retry logic, accessibility passes, i18n setup, App Store review readiness — is already done. Your team licenses the template and spends its quarter building the part of the experience that's actually unique to your product: the device-specific provisioning copy, the post-onboarding flow, the firmware-side protocol you already control. Months of plumbing collapse into a customization sprint.
Questions & answers
A1SI IoT WiFi is a licensable, cross-platform React Native template that OEMs ship with their headless WiFi devices. You brand it, customize the device access-point SSID, code-sign it under your own developer accounts, and publish it to the App Store and Google Play as your product — with the encrypted credential exchange, platform-security hardening, accessibility, and internationalization already done.
The end user follows a plain-language five-step flow — welcome, turn on WiFi, join the device, enter the network, connected. Behind the wizard the app and device perform a Diffie-Hellman key exchange over the device’s local access point, then encrypt the SSID and password separately with AES-256-GCM using a unique 16-byte CSPRNG nonce per field (NIST SP 800-38D). Credentials never travel in the clear and are never logged; the user only ever sees a progress indicator.
iOS and Android from a single React Native + TypeScript codebase — the same source tree builds both native apps. It ships English and Spanish fully translated with automatic device-language detection (additional languages drop in as translation files), and every interactive element carries accessibility role, label, state, and hint so the flow passes VoiceOver and TalkBack on first audit.
Yours. A1SI IoT WiFi is a template, not a finished app — you customize the device AP SSID, icon, splash, palette, copy, and screens, then code-sign and submit the result under your own Apple Developer and Google Play accounts. The end user installs your product from your account; A1SI’s name never appears in their flow. A1SI does not publish the template to the app stores under its own developer accounts.
iOS uses NSAllowsLocalNetworking (not arbitrary loads); Android ships a network_security_config.xml that pins cleartext to local IP ranges — the device’s own access point — while release builds use a separate env-var-driven keystore with ProGuard / R8. Input is validated end to end (SSID 1–32 bytes, WPA2 password 8–63 characters or empty for open networks) with inline field-level errors. The template enters App Store review with the security audit already passing.
A1SI IoT WiFi is licensed per engagement as full source code. Licensing terms, customization scope, and engineering-support tiers are agreed up front and are not described on this page. Start a conversation with engineering through the website and we’ll show you the source, the protocol, and what an OEM-branded build looks like. Once an OEM customizes and ships the app, that app is the OEM’s product under its own developer accounts and end-user terms.
Plans & availability
A1SI IoT WiFi is a source-available template you license and ship under your own developer accounts. We walk you through the source, the encrypted-pairing protocol, and what an OEM-branded build looks like for your device.
IoT WiFi is licensed per engagement, with customization and support tiers agreed up front — there is no online checkout. Request pricing and engineering will scope the license for your product.
A1SI IoT WiFi is licensed per engagement, with customization and support tiers agreed up front. Start a conversation with engineering and we'll show you the source, the protocol, and what an OEM-branded build looks like.
A1SI IoT WiFi is a licensable React Native template; licensing terms, customization scope, and support tiers are agreed in the engineering engagement and are not described on this page. Once an OEM customizes, brands, code-signs, and submits the resulting application to the App Store or Google Play, that application is the OEM's product and falls under the OEM's developer accounts, privacy disclosures, App Store / Play review responsibility, and end-user terms. Diffie-Hellman key exchange and AES-256-GCM are industry-standard cryptographic primitives; the security properties of any deployment depend on correct integration, key strength, and the firmware-side implementation of the matching protocol — A1SI provides the mobile-side reference implementation, firmware compatibility is the device manufacturer's responsibility.