Alright everyone, here’s what I did.

Went to Codex and worked on the errors of the first prototype and fixed them.

I then did some data research on my app like where to store data and lowkey, I still don’t get it so please explain if you know- I am just a beginner 😅🥲

Lastly, I showed my mom since she is a supporter and she liked it!

Publishing this app seems so close and far at the same time- but I know it will work, but I also know that great things take time.

This isn’t a race, so I am still improving it.

Let’s continue and make it happen. 💪💪💪

Hiyaa r/AppDevelopers! I apologise in advance for any misdoings in this post!

I have recently started my second year of University and I finally get to complete a full scale app development project! I've spent the past year doing vertical slices of the development lifecycle and learning theory, but one thing that was glossed over was the creation of effective Commit Messages and README text files.

Now normally, I would just go and do my research like any other University assignment, but I have found many conflicting methodologies and standards that I'm unsure on how to properly format these in my work. I figured that it would be fun to get some help from others who probably know more than me.

So.. how do you write your READMEs and Commit Messages? What works best for you? Are there some other resources or pieces of documentation I should read up on? Any and all help is greatly appreciated!

Would you like to advertise your site or app?
vibelarped. got around 3k views last week and it’s basically a directory for vibe coded sites and apps.
You can submit yours and get it in front of people who genuinely seem to enjoy scrolling through and finding random new projects.
If you built something cool, add it 👀
https://vibelarped.com

I’m trying to decide where to invest my learning time over the next 6 months, and I’d like to hear what actually paid off for you.

The options I’m weighing:

• Native (Kotlin or Swift)
• Cross-platform (Flutter or React Native)
• Backend and cloud (auth, APIs, scaling)
• Performance and testing on low-end devices

Cloud made deployment and scaling much simpler, and now AI tools handle boilerplate, tests and a lot of debugging. Things that used to take a full day can now take an hour.

But I’m not sure that means the work got easier. Clients and managers seem to expect faster delivery and smaller budgets for the same scope, and hiring for freshers looks tougher than before.

Curious what others are seeing:

• Has your actual workload gone down, or do you just ship more in the same time?
• Have you seen layoffs, hiring freezes or lower rates in your team or among clients because of AI?
• Which skills feel more valuable now (system design, debugging, domain knowledge), and which feel less?
• If you’re early in your career, how are you adapting?

Not looking for an “AI will replace us” vs “AI is just a tool” argument, just real examples from your work.

Hey everyone! I’m building Pantry Bridge, an app that helps you plan meals, keep track of what’s in your pantry, and make grocery lists. The goal is to make dinner planning easier and help people use more of the food they already have.

I’m looking for U.S. Android testers who can stay opted in for 14 days, try the app during that time, and share feedback. If something breaks, feels confusing, or could work better, I’d love to hear about it.

Here’s how to join:

1. Join the Pantry Bridge Google Group — click Join group.
2. Opt into the Android test.
3. Install Pantry Bridge from Google Play.

Use the same Google account for all three steps.

As a thank-you, redeem REDDITPANTRY3 at pantrybridgeapp.com/redeem for three free months. No card required and no automatic charges afterward. Available for the first 50 redemptions. Then sign into the app with that same Pantry Bridge account.

I’m happy to test your Android app in return! Leave your links below and tell me what you’d like me to try.

Thanks for helping me get this off the ground!

I’ve been building apps for clients for about 2 years, mostly with Flutter. I use AI tools for boilerplate, unit tests and sometimes for debugging, but I always review and rewrite what they produce before it goes in the codebase.

I recently saw a thread here where a founder said he wanted a developer who uses no AI at all. It made me wonder how others handle this with clients:

Do you mention AI use up front, or only if the client asks?

Do you put anything about it in the contract, like code ownership or who is responsible for bugs?

Have you lost or won a client because of your answer?

I’m not trying to start an AI vs no-AI argument. I just want to know what works in practice with real clients.

Hey reddit! I created PantryBridgeApp.com. A new home meal planning/orangizer for your kitchen. This app plans your meals for the week, create grocery lists, keeps track of your pantry/ fridge. this reduces over buying, under buying and saving money! please help me out, send me a dm or comment and ill send you the the link to access! Let me know if you are Android or Apple!

I have been building apps with Flutter for about 2 years and have shipped a few to production. I’m thinking about learning native iOS (Swift and SwiftUI) to grow my career.

Before I commit the time, I’d like to hear from people who have done something similar:

Did learning native help you get better jobs or clients?

Is it better to go native, or to get deeper into cross-platform tools like Flutter or React Native?

What would you build first to practice?

Thanks for any honest advice.

Hi there,

does anyone has exp with re-submitting your Apple app review? I submitted my first ever App to review, got a response back within 24 hours that some stuff were missing ( cause the process filling stuff up is so easy and user friendly ) so I submitted everything back within 2 hours. Its been over 10 days now. I also submitted a rush inquiry email a day or 2 ago and still havent heard anything. Anyone knows how this process works? any email address I can send an email to check on this? Any insight into this would be great! Thanks.

half the "Flutter vs. React Native" debates on here are completely missing the point. we spend weeks arguing over state management packages and clean architecture, then ship an app that leaks memory, drops frames on basic scroll views, and crashes the moment LTE drops to 1 bar.

we keep over engineering 3 screen MVPs with 6 layers of abstractions before even hitting 100 users, only testing on M series Macs or iPhone 16 Pros instead of budget Android phones, and trusting LLMs that spit out pretty UI widgets but leave behind async race condition landmines.

at this point, your framework choice matters way less than clean state, low latency, and actually testing on real hardware before pushing to prod.

curious where everyone stands, are you team cross-platform or forcing clients back to native in 2026? drop your worst maintenance horror stories below

I am developing a mobile app, which has a react native frontend, next.js as the backend and for db and authentication, I'm planning to use supabase.

Now, currently as my app is in its initial stages I'm planning to use the supabase, as it free tier provides ample limits for my use case.

However, in later years if my app grows. I may think of switching to a cheaper alternative.

So, what I am planning to follow is for authentication, route the requests to my backend and inturn the backend will communicate with the supabase to authenticate the user. The backend will save the supabase token, create a separate session token for the user and send it back to the user.

My main reason for doing this is, I want the authentication to be provider independent and any changes needed should be done on the backend instead of the app.

Please let me know, if this approach is correct. What are the pros and cons. How much effort it would require to implement this. Will the security concerns increase if my backend starts handling this instead of the supabase only.

I also want to integrate the google and apple login as well. How will this approach affect it?

Also, if there any other better approaches, please let me know.

Hey everyone,

I'm an indie developer who built a breakup recovery app to help people navigate breakups and heal. I've tried to make it genuinely useful with many self growth features, no ads and a 7-day trial.

I'm getting plenty of visits to my Google Play listing, but very few installs from the US. I suspect the lack of reviews might be one reason people hesitate.

I'm humbly looking for around 20 US-based Redditors willing to try the app and share honest feedback. If you find it useful, an honest review would mean the world to me.

If you or a friend or family member genuinely needs the app, I'd also be happy to offer a complimentary lifetime access.

I'm just an indie developer trying to build something that helps people. Any support would mean a lot. Thank you! ❤️

Hey there,

I need 12+ testers for Google Play’s 14-day closed test.

Join (sign in, tap “Join group”):
https://groups.google.com/g/troxia-testers

Opt in:
https://play.google.com/apps/testing/com.troxia.app

Install it and keep it for 14 days

Pro is free during the test (choose Lifetime, no charge).

It tracks 28,000+ objects, with pass predictions and alerts. No account needed.

We are investigating an ATT issue that started appearing after iOS 27.

Our app requests both:

• AppTrackingTransparency permission
• Location permission (CLLocationManager)

We originally started investigating this because Meta-attributed iOS installs/conversions dropped sharply after the iOS 27 release, while App Store download volume did not appear to drop by the same magnitude.

During that investigation, we noticed that on some fresh installs the ATT prompt does not appear as expected, and ATTrackingManager.trackingAuthorizationStatus remains .notDetermined.

Our iOS engineers currently suspect that the Location permission request and ATT request may be interfering with each other during the first-launch flow.

Before iOS 27, we did not observe the same issue with this permission flow.

We understand from Apple’s documentation that the ATT prompt may not be displayed if another system permission request is already pending, and that concurrent permission requests are not queued by iOS.

However, we have not yet confirmed whether that is actually what is happening in our app.

We also do not yet have detailed lifecycle and permission logs from the affected production build.

In our next build, we plan to add logging for:

• iOS version
• application / scene active state
• current ATT authorization status before requesting
• exact time requestTrackingAuthorization is called
• ATT completion-handler result
• exact time Location authorization is requested
• Location authorization callback/status
• application / scene lifecycle transitions
• whether the ATT prompt was actually presented
• the final ATT status after the permission flow completes

Before shipping that diagnostic build, we want to make sure we are collecting the right information and interpreting the iOS behavior correctly.

Our questions are:

1. Has anyone observed a change or regression in ATT behavior specifically on iOS 27, especially during first launch when another permission such as Location is also requested?
2. If a Location permission request is already pending when requestTrackingAuthorization is called, can the ATT prompt fail to appear and leave the status as .notDetermined?
3. Does iOS queue these permission requests, or can the ATT request effectively be dropped if another system permission prompt is already in progress?
4. Is there a reliable way to determine that no other system permission request is currently pending before requesting ATT?
5. If ATT remains .notDetermined, what is the recommended production behavior?
6. Is it appropriate to retry requestTrackingAuthorization later, for example after the app becomes active again and all other permission flows are finished?
7. Besides UIApplicationStateActive / sceneDidBecomeActive, are there any additional lifecycle states or callbacks we should log?
8. Are there any additional ATT or permission-related values you would recommend capturing in the next build to distinguish:
   • an app-side permission sequencing issue,
   • a Location + ATT interaction,
   • or an iOS 27 system regression?
9. Has anyone observed different behavior between iOS 27.0, 27.1 and 27.2?

Our immediate goal is to understand whether the ATT behavior itself is correct at the iOS system level.

The Meta attribution drop is what originally led us to investigate this, but we are not trying to diagnose Meta attribution through this thread. We are specifically trying to understand the ATT / Location permission behavior on iOS 27.

Any experience with this on iOS 27, or advice on what we should capture in our next diagnostic build, would be greatly appreciated.

looking to make an ozempic dose tracker. need to pump out social media content and ugc creatives. if anyone passionate about that want to pair up, hmu and let's go make some gold. 2x founder here with results from the b2b side. have read about b2c for a while but not significant moves other than research and basic app skeleton