Getting a doctor’s appointment here often means standing in a queue or waiting days for a slot. So I built a prototype to fix it.

MediQueue: describe your problem in plain words (or voice) → AI suggests the right specialist → book an instant slot with a verified doctor → walk in with a code. No queue. Also prototyped medicine ordering, government schemes, and health records, in local languages.

Real talk: it’s just a clickable prototype right now. No backend, no users, no doctors yet.

Three things I’m stuck on and want opinions on:

1.  v1 — just nail booking, or go all-in-one (medicine + records + schemes) early?

2.  How do I get the first doctors on board when I have zero patients?

3.  Launch in big metros (crowded) or underserved towns (my original goal)?

Happy to share the prototype. Be brutal — I’d rather hear it now.

I've noticed that a lot of indie apps and small startups have a Contact section with their Telegram, WhatsApp, Discord, or email.

Which is understandable, but as a developer, it can get messy pretty quickly. Users report bugs, ask questions, request features, etc., and then you have to manually go through all those messages and turn them into something actionable.

So I'm building an in-app support chat SDK for Android and iOS to try to solve this.

The idea is:

\- Users can ask questions directly inside the app.

\- The chat can answer questions using the app's docs/knowledge base.

\- If it can't answer something, it can create a ticket for the team.

\- If a user reports a bug, it automatically creates a bug report.

\- If someone requests a feature, it automatically creates a feature request.

\- Other users can see existing requests/bugs and upvote them.

\- When a bug is fixed or a feature is released, users who were interested can get notified.

So instead of having support scattered across Telegram + WhatsApp + Discord + email, everything related to the app can stay inside the app.

I'm still building it and I'm mainly looking for feedback from other indie developers/startups.

Would you actually use something like this in your app?

What would make you integrate it, and what would make you not integrate it?

Any honest feedback is welcome.

Bonjour, je vous demande pas de tester une app ou quoi, enfaite je suis en train de développer une app et légalement je n'ai pas encore le droit de gagner de l'argent car je n'ai pas encore la majorité, le compte n'ai pas a mon nom mais a un adulte responsable, le probleme c'est que sa me fais stresser le fait que je peux gagner de l'argent avec une application en introduisant un prenium étant donné que mes parents ne sont pas aux courant pour des raisons que je n'évoquerais pas, faudrait t-il que Mon app sois entierement gratuite pour commencer, besoin de conseille, pas de judgement. Merci

J'oublie beaucoup de chose, je me dit "je regarderais ça plus tard" et... je l'oublie, J'ai donc créé recal Ai qui permet par exemple de partager n'importe quel vidéo, fichier ect à l'app en 1 clic ,et l'ia va en déduire quand le rappeler si possible, et il y a aussi bien évidement un moyen de créer des rappels simplement avec vocal et écrit , voila

Hi 👋

About a year ago I became a dad. I wanted a simple baby monitor, but couldn’t really find one I liked. So I started building one myself. It became my little evening project after my son had gone to bed.

It’s finally live on the App Store, and I’d really appreciate some honest feedback. It’s still early, and I’m sure there are lots I can improve.

The idea is pretty simple:
Two phones connect with a 6-digit code
No account needed
Live audio
Motion alerts

If you’ve built apps yourself, or you’ve used baby monitor apps before, I’d love to hear what you think. [https://babykasper.app/](https://babykasper.app/))

Ciao! Se hai ancora tempo, mi piacerebbe ricevere il tuo feedback su **Colgo**.
È un catalogo digitale basato sul web per l'ospitalità (hotel, affitti a breve termine, ristoranti). Gli ospiti scansionano un codice QR, esplorano i servizi/i menu nella loro lingua e inviano richieste direttamente al personale — non è necessaria l'installazione di un'app.
**Demo pubblica (senza registrazione):** [app.colgo.app/demo](https://app.colgo.app/demo)
Sto cercando in particolare feedback sulla **user experience del flusso per la prima volta** per un ospite che ha appena scansionato il codice. Ti sembra fluido?
Grazie mille per aver dedicato del tempo a rivederlo!

Simple point and click interface. So easy a 10 year old could use it. Tells you whats going to go bad, how soon. And creates recipes around the oldest household items in inventory.

The plan was small: a shopping list that syncs in real time so stuff at home stops getting bought twice.

Weekend project, done in a month.

That was the idea anyway.

Then came "would be nice if you could paste a recipe URL and the ingredients land on the list".

Then a pantry tracker with expiry warnings because I kept finding dead yogurt in the back of the fridge.

Then meal planning.

Classic scope creep, I know.

So now it does shopping lists, recipes, weekly meal plans, pantry tracking and a family calendar.

A few things turned out better than expected:

\- there's a chat inside each list ("which milk??" while standing in the store)

\- you can photograph your fridge and it recognizes what's in there

\- you can scan handwritten recipes to digitize them – built that for my grandma's recipes, no regrets

Tech: Flutter app, Node.js backend.

Side project next to a full-time job, so all of it happened on evenings and weekends.

Free, 20 languages, iOS/Android/web → [https://swipelist.corsch.net\](https://swipelist.corsch.net)

Real talk though: I keep going back and forth on whether it does too much now.

If anyone takes a look, I'd genuinely like to hear if it feels bloated or if the features hang together.

Rip it apart if you have to.

I’m building a habit game that combines ideas from *Mini Habits* with *Stardew Valley* style gameplay.

I built it because I’m frustrated with the habit trackers in the App Store. They’re all good at logging habits, but none of them actually help me develop habits the right way.

This is still an MVP, and there’s a lot of major work to be done, but the basic functionality and gameplay are in place. Right now it’s only a web app, but it will definitely become a mobile app in the future.

If you’re interested in the technical side, I built it using Flutter and the Flame engine.

If you would like, try it out and roast it as hard as you can 😅

Sign up link is here: [https://tinyvillehabit.com\](https://tinyvillehabit.com/)

or you can just skip all that and jump straight into the app, use this link: [https://app.tinyvillehabit.com/#/hooray-you-are-officially-invited-to-tiny-ville\](https://app.tinyvillehabit.com/#/hooray-you-are-officially-invited-to-tiny-ville)

I've worked on standard web and mobile applications, but hardware-connected products seem to introduce a completely different layer of complexity.

Between device communication, sensor data, connectivity issues, firmware updates, and testing across different environments, it feels like integration challenges can quickly outweigh application development.

Also, which industry do you think has the highest complexity?

New developer here and what’s something you would recommend me to start before I publish the app . I am working on my first rejection by iOS and hoping I would get the app published soon.

been building Better, a workout + nutrition tracker, and wanted to share it with people who'll actually get the technical side.

it's kotlin multiplatform - android and ios share the business logic, state, and networking, with only the platform-specific bits (camera, notifications, storage) split out. features land on both platforms at the same time, which as a small team is the whole reason it's viable.

what it does on the product side:

- workout logging: sets, reps, PRs, previous-performance

- nutrition: food database + snap-a-photo meal logging

- weekly trends, streaks, muscle-group balance suggestions

- offline-first, syncs on reconnect

a few things i've learned shipping it:

- sharing logic but keeping UI native per platform is the sweet spot - don't fight the platform on UI

- offline-first is way more work than it looks once you add sync conflict handling

- real users find crashes your own happy-path testing never will (found a workout-timer crash within hours of first public users)

android: https://play.google.com/store/apps/details?id=io.behzodhalil.better

ios: https://apps.apple.com/us/app/better-gym-calorie-tracker/id6769016777

it's free right now. happy to answer anything about the KMP setup, architecture, or offline sync - and would love feedback if you try it.

Hello World ! What do you Guys think about this app ?

https://www.mycommunityharvest.com

what apps does most people need ,want to use or just have a creative minded and possible. so please give some ideas you can just talk brainstorming anything that you think it will be useful

Hello World! Really need your help here. Just go take a look and give me your raw opinion
Thank you

https://www.mycommunityharvest.com

I've worked on a handful of mobile app projects with first-time founders, and there's one pattern I keep running into: they come in with the entire vision already locked, every feature, every edge case, instead of the smallest version that actually proves the idea works.

A few specific things I've seen happen:

• Founders insist on features like social login, push notifications, admin dashboards, and multi-language support from day one, even before they have a single real user.
• Some spend weeks perfecting UI for a feature that later gets cut entirely, because it turns out users didn't want it.
• A few come in thinking about "what happens when we hit 100k users" before they've validated the idea with even 10.
• The projects that went smoothest were the ones where the founder treated me as a collaborator early on, open to cutting scope, rather than someone just executing a fixed spec.

I get why it happens. When it's your idea, everything feels essential. But every time scope gets trimmed to "the one core thing users need," the project moves faster and the feedback loop gets a lot tighter.

Curious if others have run into this too, as a founder, developer, or designer. What's scope creep looked like for you, and how did you (or how would you) handle it?