Shipping the app is easy-publishing it almost burned me out
When I started publishing my mobile apps, I was surprised how quickly the fun part ended.
Building the app felt straightforward, but submitting it to the stores turned into filling endless forms, dealing with bureaucracy, and guessing what I did wrong every time a review was rejected.
I noticed that a lot of indie and vibe-coders around me had the same experience.
Submitting the app became the most stressful step: double‑checking every field, fixing screenshots, rewriting descriptions, and then resubmitting after another vague rejection. It was more exhausting than actually building the product.
So I decided to build a small tool for myself and my friends to remove that pain.
That tool became Froxi AI- a helper that automates most of the app publishing process, helps you fill submission forms correctly, and reduces common rejection reasons so you can focus on coding instead of paperwork.
Right now Froxi AI is free to try, and I’m looking for honest feedback from other indie developers- https://app.froxi.ai/register
If publishing to the App Store / Google Play is the part you dread the most, I’d love for you to test it and tell me what works, what’s missing, and what feels confusing.
I’ll keep sharing my progress, lessons, and numbers here as I continue building Froxi in public.
If you’re interested, what’s the single most frustrating part of app publishing for you today?
I gave Froxi a try, and I really like how it breaks the publishing process into small, manageable steps instead of throwing everything at you at once.
One thing I noticed is that while answering the questions, I wasn't always sure how each choice would affect the final guide. Even a short explanation of why a question matters could make the process feel more like working with an assistant instead of filling out a form.
I'd love to understand your experience a bit better. Could you tell me more about your app and which tool you used to build it? At the end, did the personalized guide match what you expected based on your answers? If not, what felt missing?
Sure! I don't actually have an app to publish — I was testing Froxi as a potential first-time user to understand the overall experience.
The guide itself was clear and well structured, and it generally matched the answers I gave. My main uncertainty was during the questionnaire. I wasn't always sure how some of my answers would influence the final recommendations, so at times it felt more like filling out a form than helping the AI understand my project. That's why I suggested briefly explaining why certain questions matter. I think it would make the experience feel more collaborative and give users more confidence that the final guide is tailored to their answers.
The interesting problem isn't app publishing—it's the confidence gap between "my app is ready" and "the stores will actually accept it." I'd keep validating whether developers are buying automation, or the peace of mind that they won't lose days to avoidable rejections and resubmissions.
Yeah, do you also work on building mobile app? When you first saw Froxi AI, what problem did you think it was solving?
Good question.
I did have an initial impression, but what I found more interesting was the gap between what I first assumed the product solved and what your positioning suggests you're actually trying to solve.
I'd rather explain that in the context of Froxi than reduce it to a couple of comments.
If you're interested, what's the best email to reach you on?
yeah, lets switch to email aizhan.k@froxi.ai
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.