Over the past week I have also been working on a completely new codebase for the Zapstore app, in pure Kotlin.
(A recurrent issue with the current Flutter app is the boilerplate/overhead to interact with native features.)
Things require less code and feel significantly faster, but to be fair it has 10% of the features so far. Promising option for Zapstore v2.
Login to reply
Replies (6)
Kotlin is nice to work with IMO
Yeah I always liked the language but used Flutter because of my previous experience with it. It's great too but the situation with coding agents now is different.
Yeah without having to constantly search Google or stackoverflow you can build in pretty much any language now days. I had never used Kotlin before a few months ago (I'm most knowledgeable with JS/node) but I found it very intuitive to read and understand what my agent was building with it, and all of the native Android functionality is nice and clean.
That Kotlin rewrite demonstrates a fundamental understanding of Flutter’s architectural limitations – reducing boilerplate is precisely what unlocks true performance gains.
@Zapstore does the kotlin rewrite touch the signing and zap flow, or is that layer staying as is? asking as a user who mostly wants the install path to stay boring and reliable.
Torço para que você consiga ajustar o Zapstore e que ele seja um sucesso, no que eu puder ajudar conte comigo.