u/skylarknexus

I’m one of those people who takes photos of almost every meal.
The problem is, after a while, they just become hundreds of random photos in my gallery. I remember the food, but slowly forget the context — where I ate it, who I was with, or what made that moment memorable.

Before building this, I was literally using my Notes app to keep track of the food my girlfriend and I tried together. It worked, but having the notes separate from the photos felt incomplete.

So I built PlateDiary — a private, offline-first food diary where you can save your food photos, add notes and memories, and look back at everything in one place.

I also wanted the experience itself to feel fun and carefully crafted, so I spent a lot of time on the small details: animations, transitions, cross-platform consistency, and how your saved meals can eventually become something worth sharing as a story.

I recently launched it on iOS and Android, and seeing actual people use it has probably been the most rewarding part so far.

It even reached #40 in the App Store charts at one point, which was completely unexpected.

Still early, still improving it, and definitely still learning in public.
Would love feedback, especially from people who also have way too many food photos sitting in their camera roll 😅
platediary.app

I’ve always been the kind of person who takes photos of food.
Not necessarily because the food looks amazing, but because a lot of those meals have a memory attached to them — where I was, who I was with, what we talked about, or just what life felt like at that time.

The problem is they eventually just disappear into thousands of photos in my camera roll, and months later I barely remember the story behind them.

At one point, I was even keeping a note of the different things my girlfriend and I ate together, but having the notes separate from the photos never really felt like a journal.

So I ended up building PlateDiary, basically a private food journal where I can save a photo of what I ate, write a little note about the moment, and eventually look back through all of them like tiny memories from different days of my life.

I tried to make the experience feel less like “tracking food” and more like keeping a visual journal.

Curious if anyone here journals this way too — through meals, photos, or small everyday moments?

Would genuinely love to hear how you preserve these kinds of memories.

I take a lot of photos when eating out, but weeks later the photo usually tells me very little.

What did we order? Where was it? Who was there? And why did I take six nearly identical pictures?

I built PlateDiary around a simpler idea: take one photo of the whole table and let that one photo do the work.

PlateDiary finds the individual dishes and drinks, turns each into a separate save, and keeps the entire table together as a moment. Your moments fill a visual board and can appear on a map of the places where you ate.

There is no required naming or note-writing. You can take the photo, confirm the cutouts, and be finished in about three seconds.

No account is required. Photos and saves are processed and stored on your device, and the main experience works offline.

iOS:

https://apps.apple.com/app/id6787356977

Android:

https://play.google.com/store/apps/details?id=com.platediary.app

Would individual dish cutouts make you revisit your food photos, or would you still prefer keeping only the original table photo?

Whenever I ate out with friends, I kept doing the same thing: taking five separate food photos, forgetting what we ordered, and never looking at them again.

So I built PlateDiary.

You take one photo of the whole table. On-device image processing finds each dish and drink, cuts them into separate saves, and groups that table into a moment. Those moments build a board you can revisit later and appear on a map of the places you’ve eaten.

The part I cared about most was keeping it fast:

• One photo

• Confirm the cutouts

• Done in about three seconds

• Names, stars, and notes are completely optional

• No account required

• Photos stay on your device, and the main experience works offline

PlateDiary is now available on iOS and Android. The core experience is free; optional Premium adds collections, personalization, and more creative sharing tools.

https://platediary.app

The one thing I’d genuinely love feedback on:

After watching the first 10 seconds, is it obvious why you’d use this instead of leaving the photo in your camera roll? If not, where did I lose you?

What it does: snap one photo of your whole table, and it auto-segments each plate, cup, and dish into its own cutout. You tag each one as Food, Drinks, or Others, and it builds a running diary you can browse by day, month, or place on a map.

Why I built it: I kept taking a dozen separate food photos every time I ate out and they'd just vanish into my camera roll. Wanted one photo to do the work instead.

The capture flow — one shot in, auto-cutout out:

Been building this for the past few months and finally have something worth showing.

The idea started from something small — every time we'd eat out with friends, I'd take like 5 separate photos of the food just to remember what we ordered, and they'd all just sit in my camera roll forever. So I built PlateDiary: you take one photo of the whole table, and it automatically cuts out each dish or drink into its own little sticker, lets you tag it as Food, Drinks, or Others, and saves it into a timeline you can browse by day, month, or place.

A few things it does that I'm proud of:

• One-shot capture, auto-segmented into individual items, no manual cropping
• A map view of every place you've eaten, pinned automatically
• A stats page with total saves, most-eaten dishes, and favorite drinks
• Collections (I have a "Rice" collection with 25 saves across 13 places) and a shuffle view for browsing
• Turns any moment into a shareable story card for Instagram

It's basically a scrapbook for your table, built for people like me who eat out a lot with friends and want an actual record of it instead of a messy camera roll.

Would genuinely love feedback from other founders here, especially on whether the one-photo auto-cutout flow is clear enough on first use. Happy to answer anything about how I built it.

platediary.app

I built an app because I realized “How are you?” rarely leads to real conversations.

Hi everyone!
I wanted to share a side project I’ve been working on called Kumustahan.

It’s an offline conversation card app designed to help people have more meaningful conversations—with a partner, friends, family, small groups, or even with themselves.

The idea came from noticing how conversations often stay on the surface. Sometimes all we need is a thoughtful question to help someone open up.

Instead of endless scrolling or chat prompts, Kumustahan gives you beautifully designed bilingual (English & Tagalog) conversation cards that feel like a physical deck in your hand.

Some things I’m proud of:
🫶 Works completely offline
💬 Hundreds of carefully written conversation prompts
❤️ Great for couples, friends, family, and self-reflection
🌏 Bilingual (English & Tagalog)
📱 Available on both iOS and Android

I’m still actively improving it, so I’d genuinely love your feedback.
What would make an app like this something you’d actually use?

Visit kumustahan.app for details

I recently shipped my first mobile app built with React Native + Expo, and it’s now live on both the App Store and Google Play.
This was actually my first time properly touching React Native.

My background is mostly frontend React/Next.js, so a lot felt familiar at first — components, state, props, hooks — but I quickly realized mobile has its own learning curve.

Things that were new to me:
EAS builds
iOS certificates and provisioning profiles
TestFlight
Google Play testing/release tracks
native-feeling gestures
offline-first behavior
in-app purchases
testing on real devices
app store review/submission

I also leaned heavily on Claude/Codex while building, especially when understanding mobile-specific setup and debugging things I hadn’t dealt with before as a web developer.

Expo made the transition from web to mobile much less intimidating, but the whole release process still taught me a lot.

The app itself is called Kumustahan — a conversation card app — but the main milestone for me was going from “I only know React for web” to actually shipping a React Native app cross-platform.

For other frontend React devs here who are thinking about trying Expo: it’s very approachable, but expect the store/distribution side to be a separate learning curve.

Happy to share what I learned if anyone is going through the same path.

If you want to see, visit kumustahan.app