@prologic@twtxt.net I could, but something I was wondering is: why not share the codebase between the webapp and the mobile app so that such discrepancies are minimized? Otherwise there’s parallel development going on at all times, which violates the [DRY](https://en.wikipedia.org/wiki/Don’t_repeat_yourself?useskin=vector) principle.

@abucci@anthony.buc.ci This is quite hard to do really. Because the “web app” is a server-side rendered (SSR) app. Mobiles Apps are not normally written this way (in fact they never are). They are two very different code-bases, which is why we spend a lot of effort on the client and the API. On a side note, I’m also working in parallel on a way to “embed” Go code (as a client) in a Flutter App in the hopes for more reusability for Salty.im – If we can pull that off, it’ll also help improve the reuseability of client features and improve on keeping things DRY for the Yarn.social app 👌

@abucci@anthony.buc.ci Yeah like I said it’s being worked on slowly 🤞

@abucci@anthony.buc.ci Yup that’s the goal 🤞