About my 'Telegram mindset':

For a long time my main project was Fullyst, a service that lives entirely inside Telegram. Naturally, everything there is built around the Telegram ID. For me it was the single source of truth and the unique user key.

Now, while building my new project Saylify, I carried over some of Fullyst’s architectural decisions out of habit. When I finally got to the standalone web app, I realized I had once again treated Telegram ID as User ID in Saylify.

I ended up having to redo quite a lot: switch to UUIDs, store mappings to OAuth providers, and decouple the product core from Telegram, which in Saylify is just one of the usage channels.

Soon I will write about verifying Improvy OÜ in the Apple Developer Program, the adventures around that, and why I needed it in the first place.

And this post is also the first time I have mentioned the name of the new project 😉