I had been using Typeless for voice input on Android. But it did not even have simple buttons for moving the cursor left and right. And if you want to use it a lot, you need a paid plan, which is not cheap. I was not happy with that.
OpenAI’s transcription API provides low enough latency for this kind of voice input, and it can be used at a very low cost compared with many existing voice-input applications.
So I thought: why not make something for myself first?
And I did. That became KoIME.
KoIME is BYOK, and I operate no backend server. More importantly, it was just the right size of project for learning and experimenting with the IME internals of an Android application.
The STT engine is separated behind a small interface, so I hope people will fork the project and experiment with it themselves. For example, you could insert an LLM layer that rewrites the transcription for a particular domain. That kind of modification is exactly what I would like people to try.
The name KoIME also contains a small Japanese joke.
The Japanese word for “voice” is koe, written 声. A voice IME can therefore be described as a “Koe IME,” which I shortened to KoIME.
But KoIME also sounds like the Japanese word 濃いめ, meaning something like “a little stronger” or “richer.”
The design philosophy has become rather concentrated too, so I think the name fits. :)
My impression from the `.smolmachine` single-binary packaging is that it could have a massive impact on next-gen edge computing and distributed serverless infrastructure.
To me, it feels like it could fulfill WASM's promise of a "portable execution unit that runs instantly anywhere," but with the added benefit of keeping the existing Linux binary ecosystem intact via microVMs.
I'm curious—is this kind of use case aligned with the direction you're aiming for?