Lately, I’ve been deep in the trenches with FlutterFlow — and ran into an unexpected dilemma.
Deploying an app on Apple turned out to be simpler than on Google Play... even though Flutter is a Google product! 🤔
At first, I was going to just post about the experience on the community board... but then I thought, "Why not turn it into a poem?". Which I did and posted.
And then I thought — "Wait, why stop there?" — and turned it into a full-blown song. 🎤😂
If you’ve ever wrestled with the Google Play Console (or if you build with @FlutterFlow, you might feel some of this pain.
Or maybe it's just me. (Please tell me it’s not just me.)
Here's the quick rundown of how it came together:
➝ Original draft: Written by yours truly, [Mosses Akizian]( / mossesakizian , founder of Practical Pixel Studio.
➝ Poemitized: Thanks to OpenAI ChatGPT (is that a word? Well, it is now.)
➝ Lyrics: I added a chorus and closing verses to tighten it up
➝ Song creation: Discovered Brev AI while "googling" and trying few other music generating AIs.
➝ ➝ Music prompt: Deep-voice rap with a hip-hop touch
➝ Final edits: Cleaned up the audio in Audacity
➝ iMovie to convert mp3 to mp4.
➝ Converted to karaoke mode with @Descript
🎶 Hope you enjoy — and if you’ve got Google Play Console war stories, I’m all ears. 😂
Lyrics:
Yo.
Flutter's from Google, that much is true,
And Dart is their darling, their backend glue.
FlutterFlow rides that same wave,
Built by ex-Googlers, sharp and brave.
Google Play Console? Same big brand.
So deploying should be... just as planned?
Instead, it’s like decoding lore,
Apple’s gate feels like an open door!
The first launch? A comedy show.
Endless errors — fast or slow.
Form fields missing, assets denied,
Random checkboxes multiply.
Okay, fine — version one’s live.
Took a week and ten deep sighs.
Then comes build two, just a tweak,
Now Google screams, “Major change!” — what a streak.
Why the drama? What’s the deal?
Why’s a bug fix such an ordeal?
[chorus]
No code broke, no rules bent,
Still stuck in this Google event.
Maybe it's pride, or just routine,
A form of stress baked in the machine.
Whatever it is, I need to ask:
Why’s a simple update such a task?
[chorus]
No code broke, no rules bent,
Still stuck in this Google event.
Agree with this? Or think it’s fine?
I’d love to hear your take — drop a line.
Meanwhile, I’ll chant this hopeful phrase:
"Maybe smooth deploys come in May days.
[chorus]
No code broke, no rules bent,
Still stuck in this Google event.
Maybe it's pride, or just routine,
A form of stress baked in the machine.
Whatever it is, I need to ask:
Why’s a simple update such a task?
[chorus]
No code broke, no rules bent,
Still stuck in this Google event.
Like I said,
"Maybe smooth deploys come in May days.
Peace out. Now back to FlutterFlow.
Информация по комментариям в разработке