Turbo Modules
Turbo Module development
Native modules for the New Architecture, written bridgeless in Kotlin and Swift, and published.
Part of native ios and android developmentreact-native-google-places-turbo is on npm under the MIT licence. Every other Places autocomplete library for React Native calls the HTTP API from JavaScript and asks you to draw the results list yourself, which works and is always slightly wrong: you tune the debounce, you get the session tokens right, and the list still does not feel native because it is not.
That module renders the autocomplete interface Google ships in its own Android and iOS SDKs, driven from JavaScript across a Turbo Module, Kotlin on one side and Swift on the other, built bridgeless from the first version rather than ported to it afterwards.
What that covers
- Codegen-typed Turbo Modules, bridgeless from the start
- Kotlin on Android and Swift on iOS in one module
- Published to npm with a working example app
- Old-style bridge modules rewritten for the New Architecture
- Native SDK surfaces the JavaScript ecosystem has wrapped badly
Where this has shipped
Self Ride
Inara Consultancy Services, 2024
Rider and driver in one app, from an empty folder: auth, payments, maps, location, push and deep links.
How it is built
Revolt Summit and Streaming
Inara Consultancy Services, 2022 to 2023
Two apps for one brand: a live event platform and a streaming service, with offline video and deep links on both.
How it is built
Next: TanStack Start
Tell me what you are building.
A sentence about the product and where it is stuck is enough to start. I answer every mail myself, including the ones where the answer is that I am not the right person.