r/VibeCodeCamp

The app is called Puplytics.

Before this project I had basically zero real coding experience. I went from not understanding app structure at all to learning React Native / Expo workflows, App Store Connect, subscriptions, AI APIs, privacy compliance, camera permissions, TestFlight builds, backend deployment, and debugging random production issues at 2am.

Honestly the hardest part wasn’t even building the app — it was getting through Apple review.

I got rejected for:
• subscription flow issues
• missing legal links
• camera permission wording
• AI consent flow compliance
• metadata problems
• purchase restore handling
• sandbox purchase behavior
• UI edge cases on iPad
…and probably more I’m forgetting lol.

The app itself is a dog wellness tracking app focused on digestive health and daily wellness tracking.

Features include:
• AI stool scan analysis
• symptom tracking
• food logging
• sleep & mood tracking
• AI wellness chat
• trend analysis
• downloadable vet reports
• multi-pet support
• reminders and history timelines

The original idea came from dealing with recurring stomach issues with my own dog and constantly forgetting what food changes or symptoms happened during vet visits.

So I basically built the app I wished existed.

The craziest part is realizing how much you can actually build now if you’re willing to learn while moving fast.

Would genuinely love feedback from other builders / vibe coders:
• UI/UX thoughts
• onboarding feedback
• feature ideas
• App Store screenshots
• monetization thoughts
• anything that feels confusing or broken

Still improving it daily. (As of right now it’s been live for about 20 minutes lol)

The app is called Puplytics on the App Store if anyone wants to roast/test it 🙏

I'm just curious. How concerned are people about the security/vulnerabilities in vibe coded apps?

It seems that it's defaulted to by the platform. Yes?

My first app has officially launched.

It’s powered by AI-driven TTS and STT technologies, and uses generative AI to automatically create language learning materials for 38 different languages. For everyday learners working on a second language, it offers a wide range of practical features. One of the core highlights is its ability to recognize a learner’s pronunciation, break it down into phoneme-level units, and analyze it in detail. On top of that, it provides a Free Talking feature across all 38 languages.

In short, yes—Duolingo would be considered a competitor. (Why not? 😊, quite competetive on Free-Tier)

But here’s the part that matters most: I built this entire app through vibe coding, with zero coding knowledge. None. There may be people who doubt vibe coding. I understand that skepticism. But I believe this app itself stands as proof that it’s not only possible—it’s real.

It’s been about a month since launch. There were challenges, of course. A few twists and turns. But now, I can confidently say the app has taken its proper shape as a fully functional product. It’s officially approved and live on both iOS and Android, and there’s also a working web version. Ads are running. Subscription plans are active across all three platforms. Payments are functioning smoothly.

Through this process, I came to a realization: the technical necessity of traditional IT developers may inevitably decrease. I can’t read code. Even if I look at it, I don’t understand what it means. But I chose to trust the code generated by AI. I trusted it—and I kept moving forward. That’s how this product came to life.

It’s not because the app is simple. It’s not a lightweight toy. Technically, it includes the structures and features you would expect from a serious product. And that makes me reflect—perhaps skeptically—on the future of conventional development roles.

Believing that AI-generated code is likely correct… and providing extremely detailed requirements—that combination allowed someone who knows nothing about coding to build a real app.

If anyone tries my app and thinks, “This can’t be done because it’s vibe coding,” I’d genuinely welcome that conversation. Let’s talk.

We've all had that one project where juggling multiple APIs turned into a headache. What's been your biggest challenge or pain point when integrating different APIs? Let's share experiences!

https://i.redd.it/oip9cy23fr1h1.gif

DevHelper has grown so much in the past 5 years. From a simple tool that sits in your tray menu and lets you trigger urls and shell commands, throught a UI app addition and extensions to AI.
Now its more powerfull than ever. It your prototype development hotspot, where you have the controle over the AI not vice-versa. You start your idea with ai and plan mode, or by manually adding components. You need help of ai to speed things up, fire up any prompt, anything you can do manually you can do it with the AI, "add new screen", "add app bar", "change the image", "when i press the sign up button navigate to the new sign up screen" ... or you have a big idea in your head, type it in the plan mode, and let the AI build the design so you can refine it later, or go into the more powerfull interactive plan, where you build screen by screen, step by step, you dont like what AI is planing, refine the plan.

And at the end, when you are ready, with a click of a button generate a plan to build the real app, by first answering few questions to pick the tech-stack, and then with a single click let Codex generate the entire code bas for free. Dont like codex, would rather use someting else, you can download the entire plan.md with all the screenshots of everything you have desined in a single zip file, and use it wherever you want.

This is one of the features built in the DevHelper, and you have so much more, with so many more to come, but to keep this project alive for free, we need all the support we can get, either by donating via buymeacoffe, or spreding the word on the social media.

Get the latest version on our website

I’ve been building Flyers Up, a local services marketplace for people who need help and local service pros who need more work.

The app is built as a web app and wrapped for iOS, so one of the biggest things I’m working on right now is making it feel less like a website inside an app and more like a real mobile product.

The main flows are:

• customers request local services
• service pros receive booking opportunities
• customers pay a deposit
• Pros complete the job
• final payment and payout logic happen after completion

The hardest parts so far have not just been the code. It has been making the whole thing feel simple and trustworthy.

Things I’m currently trying to improve:

1. First screen clarity
2. Customer vs pro onboarding
3. Mobile spacing and button hierarchy
4. Bottom navigation
5. Booking flow
6. Trust signals
7. Payment screens
8. Making the app feel more native on iOS

A few things I’ve learned while building:

• Marketplace apps are harder than normal apps because you need both sides at once
• UI that looks fine on desktop can feel crowded fast on mobile
• trust matters more when the service happens offline
• Onboarding has to explain the product without making people read too much
• payment screens need to feel extremely clear
• AI can help move fast, but you still have to know what good UX should feel like

Right now, I’m trying to figure out what to improve first:

• simplify the landing page
• improve the customer/pro split
• make the booking flow feel smoother
• add stronger trust signals
• polish the iOS layout
• narrow the service categories

If you were looking at an early marketplace app, what would you fix first to make it feel more polished and trustworthy?

I’m open to direct criticism. I’m trying to make this feel like a real product, not just a project.

After spending way too long researching why no-code apps get rejected on the App Store, I found some patterns that kept coming up — especially for Adalo, FlutterFlow, and Bubble founders.

Here's what actually causes rejections (not the obvious stuff):

1. Privacy policy linked in the wrong place

Most founders add it to App Store Connect but forget to make it accessible from inside the app. Apple checks both. A button in your Settings screen pointing to your policy URL is all you need.

2. App Review Notes left blank

This field in App Store Connect is where you give the reviewer demo credentials and explain how to test your app. Over 40% of Guideline 2.1 rejections happen because the reviewer simply couldn't access the app. Most founders have never heard of this field.

3. Bubble WebView wrapper risk

If you're using Natively or BDK Native to wrap a Bubble app, you're at risk of Guideline 4.2 rejection (Minimum Functionality). Apple has been cracking down on WebView wrappers harder in 2025-26.

4. No Restore Purchases button

If your app has any IAP or subscriptions, Apple requires a visible Restore Purchases button. Reviewers check for this specifically. Missing it = rejection.

5. The Data Safety form (Google Play)

Most no-code platforms bundle Firebase/Crashlytics by default. You have to declare that data in Google's Data Safety form — not just your own app's data. Most founders only declare their own data and miss the SDK data entirely.

6. Age rating mismatch

If your app has any form of chat or user interaction, you cannot rate it 4+. Both stores will reject this automatically.

7. Screenshots showing unbuilt features

Reviewers open your app and compare it to your screenshots. If you show a feature that doesn't exist yet — rejection.

8. New Google Play accounts need 12 testers for 14 days

Before you can publish to production on a new Google Play account, you need to complete closed testing with 20 real testers for 14 consecutive days. Most first-time founders discover this gate only after they think they're ready to launch.

----------

I built a free checker that scans for all of these (and more) before you submit: Check Comment

Hope this saves someone a rejection cycle.

Just to be upfront: I wrote the original version of this post myself, but I was lazy and used AI to clean it up for grammar, punctuation, and clarity. The thoughts/frustrations are mine.

This might be a dumb question, or maybe just proof that I’m a complete beginner, but I’m curious if anyone else has had this experience.

When I’m working on apps/websites, I try to plan everything out as much as possible with ChatGPT first. I’ll create goals, break things into detailed epics, generate tasks for each epic, keep project logs, set communication rules, and basically build a whole workflow around it.

Right now my process is something like:

ChatGPT helps me create a plan-only prompt for a task → Replit Agent creates the plan → I paste that back into ChatGPT → ChatGPT approves or revises it → ChatGPT creates the execution prompt → Replit Agent does the work → I paste the project log update and Git SHA back into ChatGPT so it can review what changed → then I move on to the next task.

It’s very structured, which is probably good, but honestly it’s also incredibly boring. I don’t feel like I have much real oversight into what’s actually happening.

One of the things I have ChatGPT do is translate every plan, execution prompt, and recap into plain-English summaries because the actual prompts can get really long. That helps, but I still feel like I’m mostly just copying things between tools and hoping the process is moving the project forward.

In general, I feel like I’m spinning my wheels without really seeing much happen. Part of that might be because the epics are set up to do a lot of backend work first before the frontend UI gets built out. So aside from occasional smoke tests, I don’t have a great feel for what’s actually been accomplished.

Does anyone else feel this way?

I’m usually the kind of person who wants to understand every little detail so I can picture how everything works and fits together. But I have basically zero coding knowledge and almost no understanding of tech stacks, architecture, backend/frontend stuff, etc., so the whole process makes me feel completely lost.

I guess what I’m asking is: is this normal when you’re building with AI as a non-coder, especially early on when most of the work is backend/setup stuff? Any tips on how to improve my understanding (within realistic constraints; I'm not going to get a degree in this and I barely have enough time to work through about 2 hours/day on Replit)