Famiyo

January was a big month for Famiyo. I finally connected a lot of the pieces that had been floating around separately, and the app is starting to feel like something families can actually use day to day.

The biggest change is the new calendar. You can now switch between a monthly and weekly view, browse through days, and add events directly. Events can also award points to participants, with a short description of what the points are for. The idea is to make everyday activities a bit more engaging, especially for kids, without turning it into a chore for parents.

Daily tasks also got an upgrade. Each day now has its own list, and completing tasks can unlock rewards. Rewards have quantities, expiration dates, and deactivate automatically when they run out. I’m planning to add notifications for parents when a child redeems a reward, but the backend logic for that is already in place.

Another thing I added this month is the ability to join a family using a code. New members start with the >child< role by default. If someone is actually a parent, another parent in the family needs to approve that change. It’s a simple safeguard, but it keeps the structure of the family intentional.

One thing I’m still thinking about is how task confirmation should work. Should a parent have to approve completed tasks, or is it enough for a child to mark them as done? I can see arguments for both approaches, so I’d love to hear how other families handle this.

I'll attach screenshots of the new calendar views, the event creation flow, and the daily tasks screen as soon as I find how to do this! :). If you have thoughts, ideas, or things you’d like to see in Famiyo, I’m all ears! This project is evolving week by week, and real feedback helps shape what comes next.

Hey Indie Hackers!

I’m Piter, and I’m building Famiyo: a family organization app that tries to solve a problem I kept running into in my own life: families operate like teams, but they don’t have team tools.

At some point I realized something funny (or sad, depending on the day). I can manage a dev team, a product roadmap, and a release cycle but planning a normal week with my family felt like debugging a production incident at 2 AM.

Calendars everywhere. Tasks scattered across apps. Kids forgetting chores. Parents forgetting who was supposed to pick up who. Everyone stressed. Nobody aligned.

So I thought: what if family life had the same clarity and structure we expect from good software? Not in a cold, robotic way - but in a "finally we know what’s going on" way.

Why Famiyo

Because families deserve tools that actually reduce chaos instead of adding more. Because planning shouldn’t feel like a boss fight. Because kids love rewards, parents love clarity, and everyone loves when things just… work.

What I'm building

• A shared family calendar that doesn’t require a PhD to understand

• Tasks and routines that sync in real time

• A simple reward system for kids (and honestly, adults too)

• Offline‑first architecture, because life happens in places with terrible Wi‑Fi

• A clean, calm UI that doesn’t scream at you

My unofficial goal

To build the first app that stops families from asking: wait, what are we doing tomorrow?

Status

Early build is shaping up nicely. Architecture is clean, data flows are ok, UI is getting there. And I’m finally ready to share the journey publicly.

If you’re into productivity, family tech, offline‑first apps, or just enjoy watching founders try to turn chaos into software 0 follow along. I'll be posting updates, wins, fails, and probably a few "why did I architect it like this" moments.

p.s. the landing page is already live: https://famiyo.app