Okay Jemaw so i've Been cooking again. 😅

Just pushed another update to Equib Manager (v3.2.0) with a major UI/UX refresh, lots of small fixes, and some backend/security improvements to prepare for future releases.

The screenshots below are from the latest build. Let me know what you think. 👀🚀

#equib_manager @equbmanager

We are live on Product Hunt 🎉

litreally takes less than a minute of your time, but it means a lot.

Click Here to UPVOTE

Appreciate your support.
@imsanyi

And honestly Jemaw… I’m in that mood again

I’m building automation into my release workflow from my github repo to Equb Manager channel for the app for the next releases so next time I push a version, it won’t even be me posting the update to the telegram channel anymore cause am too lazy for that 😅… let it be my system doing it

and this is a new type of feature for me, so I’m taking it slow, testing things out, breaking stuff, fixing it, then repeating the cycle like a responsible engineer.

I just like getting my hands dirty cause i will know something new.

And yeah… this is exactly where I feel like I need @sanyi’s ShipLog Project which i rely encourage you to up-vote his project

let’s see how far I can push this before something explodes

#equib_manager

Dont you dare say "why dont you just vibe code it?"

actully its not that complicated it’s just adding one extra step to the current release workflow: a simple POST request to the Telegram Bot API

i will create a bot, grab the token, get the Equib Manager channel ID, make the bot admin in the channel, then store the token + channel ID in GitHub secrets. After that, flutter build the app store it in releases and the workflow just sends the already built release APK with a caption whenever a new tag is pushed.

noting fancy btw akbdkut meslej 😅😂

#equib_manager

bayhon i can add some kinda features to the telegram bot tho but not today am wrapping my head around this 🤔🤔

#equib_manager

Just waiting for this one

Well Jemaw... turns out I hit my first "wait... what?" moment 😭

The full APK is around 63MB, and that's over Telegram's upload limit for bots 😅.

So... small change of plans.

Instead of building one universal APK, I'm updating the release workflow to build separate APKs and only publish the arm64-v8a version for now. It's smaller, and honestly that's what most Android phones are running anyway.

Didn't expect Telegram to be the one slowing me down 😂

Anyways, here are the changes I made to the release workflow in case you're curious 👇

#equib_manager

you'll notice that releases now come with 3 APK files instead of just one 😄

That's because I started using Flutter's --split-per-abi build flag.

So now each APK is built for a specific device architecture:

📱 app-arm64-v8a-release.apk → This is the one you should download. Almost all modern Android phones use 64-bit, and it's smaller too.
📱 app-armeabi-v7a-release.apk → For older Android devices that still run on 32-bit.
💻 app-x86_64-release.apk → Mostly for Android emulators... which is exactly what I'm testing on these days 😅

So if you're ever confused about which one to pick, just download app-arm64-v8a-release.apk. That's the right one for almost everyone. 🚀

moment of truth

Ladies and gentlemen....... we got him 😎😎

#equib_manager

but for now since we schedule a post for this release will be removing it from EQUB MANAGER channel

annnnnnnnnnnnnnnnnd we're done for today.


i guess.

I gotta check this

bikerebjes 😂

well Jemaw ik be Equib app adrekachewalew now colabing with Mike , we are cooking something up for this weekend probably maybe earlier ena besu lenaderkachew nw but its worth it Thrust me

#tugs

idk about you guys but there are quite afew times i failed over few projects as team or solo ive worked more and less than 3 months which i wish i can go back to them thinking back now.