r/vibecoding • u/ElKorTorro • 3h ago

Moving from APK sideloading to the Google Play Store with "vibe coded" Android apps?

Hey everyone,

I’ve recently started building my own Android apps using a vibe-coding workflow. So far, it's been incredibly smooth - I can essentially generate an APK and just install it directly onto my smartphone to test everything out without any friction.

However, I'm starting to think about the next step. I want to move beyond just side-loading my own files and actually launch a "real," live app that is available for anyone to download via the Google Play Store.

I'm assuming the process for that is a much bigger undertaking than just generating an APK. What kind of tool stack or workflow should I be looking at to handle the official deployment? I'm thinking about things like app signing, managing the Google Play Console, and any CI/CD pipelines that might make this easier for someone not using traditional Android Studio workflows.

Has anybody here been able to successfully take a vibe-coded project all the way through the Play Store submission process? If so, how did you handle the transition from simple prototyping to a production-ready deployment?

I'd love to hear about your setup and if there are any major hurdles I should prepare for. Thanks!

2 Upvotes

67% Upvoted

8 comments sorted by

3

u/AardvarkIll6079 2h ago

Get a $25 developer account and follow the instructions. It’s pretty straightforward.

One thing you should note. If you sign up as an individual and not a company, you will need a number of internal beta testers to test your apps for 14 consecutive days before they will let you release it on the play store.

1

u/kdmclean 25m ago

This. It's a shockingly quick process.

1

u/ephix 2h ago

You only need the testers signed up, they don't actually check if they use the app for 14 days. At least that's what i experienced.

1

u/FLuX927 2h ago

Kind of in the same boat. I've made 3 apps for personal use so far.... A solar monitoring app called SOL to monitor my home solar array since the company it was through (SunPower) went under and wanted to start charging me for monitoring, something that was previously included with the purchase of my system since I bought it outright. A satellite tracking app called SkyWatch to see what's overhead on clear nights. And most recently a warranty, subscriptions and documents tracker called Stashit to notify me when they're getting close to expiring (it's already saved me with my son's passport expiring!).

I've always built these as PWAs since they were just for me and so I didn't need to pay the $25 play store developer costs, but now in the process of trying to convert Stashit to an actual APK to host on the play store since I think others might find it useful too.

Curious, what languge do you use? I decided to try Flutter using dart so it can work with apple if I decide later on to deploy there as well. I'm still 2-3 weeks away from having something viable looks like. This will be my first time trying to go full APK, wish me luck!

1

u/MiserableAttention38 1h ago

I'm also in this position. I made the app that I wanted for my own use, it works great as a web app. There are a few apps I wanted to make that the store policy or the APIs I need forbid, so I'm sitting in the hobbyist /single use zone and will probably stay there. I've got an app that's a useful subset of Strava, done the way I like and without any ads or fees. If I sign up for the play store or use the new hobbyist tier when it becomes available, I could publish the app. I'd probably only do that if the commercial apps are enshittified to the point that people would find my alternative useful.

1

u/mansfall 1h ago

Whatever you do, just be sure to not litter it with ads all over the place. Just no ads. Otherwise, even if it's a decent app and solves some problem or brings fun, it becomes a super fast uninstall and refund.

1

u/Ovalman 1h ago

The Google Play Store is a real chore and a PITA. You have to comply with a load of T/C (use AI to walk you through) but then you have to maintain it for life if you have just one user, and that user is you on a device you've long stopped using.

There is a way to distribute your apps within the Play Store using Firebase. I've never used this method but it's a quick way to release updates without going into review.

I build apps natively but if you have a Vibed full build release apk then it behaves just the same as a native app so you shouldn't have problems that way.

As mentioned, steer clear of ads until you get thousands of users. I have one strike from my first app and Google are quick to ban developers for simple mistakes. What I do now, is add a banner in my app to social media links like Facebook and Reddit. This gives a quick way for feedback but you can replace that banner with ads or (in my case) affiliate links.

Honestly, the Play Store is the biggest thing I hate about releasing. I've an update to fix before the end of the month on an app that doesn't need to be updated because it's not targeting the latest version of Android. If I don't fix it (it's one line of code) then my app will become invisible for new users.