I think the era is changing where we start to callabrate tokens per tasks 🤦‍♂😔

Almost done with it... Lately, I realized that posting APK builds directly to the Telegram channel isn't the ideal way to distribute Equb Manager. It doesn't give me much control over how releases are presented or managed. I wanted people to download the app directly from the website instead, while keeping Telegram for release announcements and changelogs. It turned out to be a bigger task than I expected because I had to rethink almost the entire release infrastructure. Previously, my GitHub Actions pipeline built the APKs and sent them straight to Telegram. It was simple, but not very manageable as the project grew. So I changed the pipeline. Now, instead of sending APK files to Telegram, GitHub Actions uploads them to Supabase Storage. From there, I can manage releases, review changelogs, update release notes, and publish everything through the admin dashboard. The website handles the actual downloads. This also gives me something important: control over the release notes. Since the changelogs are AI-generated from Git diffs, I can't always trust them to capture every change correctly. Sometimes the AI misses important updates, and there are also cases where I need to include additional information or testing notes. Having the chance to review and edit everything before publishing makes a big difference. The only reason I was distributing builds through Telegram in the first place was that I couldn't publish Equb Manager on the Play Store, and I hadn't considered building my own distribution system using cloud storage. Of course, if I had a Google Play Console account, this would probably have been a much simpler task. I could have just shared a Play Store link. But since I don't, I had to build the infrastructure myself. And that's what kept me busy throughout the night. If you're in a similar situation and need somewhere to store and distribute your app builds, I'd suggest looking into Supabase Storage. It has its limits, so use it wisely. One thing worth mentioning: I'm already using PostgreSQL for Equb Manager, where I have client and agent data. I don't see a reason to migrate all of that to Supabase just to use its storage. That would create unnecessary work. I'm keeping my existing database and using Supabase strictly for file storage. Supabase has quite a few things to figure out at first. I had to get some help understanding how its storage API works, but once you get the hang of it, it's a pretty great platform. Sometimes, building a product also means building the infrastructure around it.

Good Morning Jemaw