Restarting care-kiro - feedback is finally getting closer
More people can now give useful feedback on care-kiro. After a quieter development period, I am going to focus on hardening the beta and preparing for an official release.
I am starting to feel that care-kiro needs my attention again. For a while, my time went into other experiments and into improving the Park Labs site itself, but the number of people who can actually touch care-kiro and give useful feedback is growing.

🔬 Why care-kiro now
care-kiro started as a work management app for visiting nurses. The first idea was simple: make daily records and expense tracking less painful for nurses who are already moving between homes and handling a lot of context.
But the more I looked at the actual workflow, the clearer it became that this is not only an individual tool. A nurse may enter a report, but a station needs to review it. Expenses need approval. Schedules connect to the whole organization. Patient and visit information cannot live only in one person's screen.
So care-kiro sits between B2C and B2B. It needs to be useful for individual nurses, but it also has to fit the station's management flow.
Recently, the useful feedback surface has grown. The number is still small, but at this stage the quality of feedback matters more than scale. A comment like "this is how the work actually flows in the field" is much more valuable than a generic feature request.
📊 What the beta taught me
The beta so far was less about launching a polished product and more about checking direction.
Real workflow matters
records, schedules, and expenses should not feel like separate tools. They are connected parts of one workday.
Nurses and station managers see different things
nurses need speed and low friction. Stations need review, approval, and visibility. The same data needs different interfaces depending on the role.
Mobile is not optional
visiting nursing does not happen only at a desk. Input has to work between visits, right after visits, and in short gaps. That is why the PWA and Flutter app path both matter.
Trust beats feature volume
in healthcare and care work, a long feature list is less important than predictable behavior, safe data handling, and a product that does not create anxiety.
🔄 Why development slowed down
Honestly, care-kiro did not keep moving at the same pace. I spent time on the Park Labs website, AdSense readiness, lab notes, and other experiments.
That is not really an excuse. It is just the shape of solo development. When I focus on one thing, another slows down. If I touch everything at once, nothing gets enough depth. care-kiro especially needs domain understanding and grounded feedback, so working on it shallowly did not feel right.
Now the situation is different. There are more people who can react to the product, and the direction is clearer. It has moved from "I should return to this someday" to "this is the right moment to return."
🛠️ Rechecking alpha, hardening beta
To be precise, this does not mean care-kiro is going backward from beta to alpha. The idea is to take the beta that already exists, run an alpha-style internal checklist again, and then raise the external beta quality toward an official release.
Alpha checklist
review the foundations: data model, permissions, record flow, expense flow, and role boundaries.
Beta hardening
prioritize the places where real users get stuck, where mobile feels awkward, and where the product needs clearer guidance.
Release preparation
prepare the parts around the product too: pricing, onboarding, support, terms, privacy, and operating routines.
At this stage, the question is not "what big feature can I add?" The better question is "does this feel safe enough to use?"
💡 What I will focus on
The next phase has to be driven by real feedback.
I do not want to invent too much here. Visiting nursing is already complex. If care-kiro adds more complexity, it misses the point.
So for a while, the work is less about building more and more about building the right things.
🎯 Next
care-kiro is an important experiment inside Park Labs. Some services test advertising revenue, some test hackathon ideas, but care-kiro is closest to reducing inconvenience in a real work environment.
Now that feedback is getting closer, I want to use this timing well. I will revisit the alpha checklist, harden the beta, and prepare the path toward an official release one step at a time.
There is still a lot to do. But now I have a much better reason to start moving again.