As written, I had started to gather all ideas and document what we want. Of course, there exist magic tools which transform unstructured input into well-defined #requirements and which help you to make them conflict-free, unambiguous, atomic, feasible and verifiable. Yada yada, you know the drill.
Then the development started, and we have a first #MVP (minimum viable product) now, as an Android release package and Linux Desktop build. The first content has been added, so the first user feedback could be gathered today. I have to admit, offering an app with well-known competitors yields a lot of “oh, but here it should behave like this” … anyway, input from the target audience is really dear to me. So we now have plenty more things to implement and some to adjust. But we did not experience a single crash or logic deadlock.
โจ ๐๐ง๐ ๐ฌ๐จ๐ฆ๐ ๐ฎ๐ฌ๐๐ซ๐ฌ ๐๐จ๐ฎ๐ฅ๐ ๐๐ฅ๐ซ๐๐๐๐ฒ ๐ฅ๐๐๐ซ๐ง ๐ฌ๐จ๐ฆ๐ ๐ง๐๐ฐ ๐ฐ๐จ๐ซ๐๐ฌ. โจ
I’ve added on-device screenshots from one of the recent builds. If you want the hands-on experience, go to https://github.com/marcelpetrick/CroLingo/releases/tag/v0.0.40
I’ll keep you updated on what comes next. ๐ญ๐ท โค๏ธ ๐ฉ๐ช
