Loading Park Labs...
Loading Park Labs...
LAB NOTE No.0222026.05.13Development
I've been feeling more and more that I need to get properly back to Care Kiro. For a while most of my time went into other experiments and the Park Labs site, but lately a few more people have been using Care Kiro or giving me feedback on its features. It's May 2026, and it's time to get back to the product.

Care Kiro started as a records and expense app for visiting nurses. At first I mostly wanted to help individual nurses manage their work a little more easily. But once I actually talked to people, it was clear that looking only at individual users wasn't enough.
Visiting nursing isn't something one person finishes alone. Records have to be checked by the station, expenses need someone to approve them, and schedules have to fit together across the organization. So Care Kiro naturally ended up sitting between B2C and B2B.
The number of people giving feedback is still small. What I want to hear at this stage is less "it'd be nice to have this feature" and more "here's how this flow actually works in the field."
The beta so far has been about checking direction. It made it clearer that records, schedules and expenses all connect within a single workday.
Nurses want to record things quickly, while the station needs to review and manage. The same data has to be presented differently depending on the role.
Visiting nursing doesn't happen only at a desk, either. Nurses need to enter things on the move, right after a visit, in short gaps. That's why I'm thinking about the PWA and the Flutter app together.
And in healthcare and care work, a product that looks feature-packed mattered far less than the sense that the data is safe and the flow is predictable.
Honestly, Care Kiro didn't keep moving at the same pace. Tidying up the Park Labs site, preparing for the AdSense re-review and patching up other experiments spread my time thin.
It sounds like an excuse, but that's just how solo development goes. Pick up one thing and another slows down. Pick up several at once and none of them gets enough depth. Care Kiro depends heavily on understanding the domain and on real feedback, so I thought it was better to dive back in properly when I could focus than to keep poking at it. The product direction is also clearer now than it was then.
Starting from the beta features I've already built, I'll go through an alpha-level checklist again internally and raise the quality of the beta that users see.
Table 1
| Stage | What I'm looking at again |
|---|---|
| Alpha check | Data structure, permissions, the records flow, the expense flow |
| Beta hardening | Where users get stuck, what's awkward on mobile, where explanations are missing |
| Official release prep | Pricing, onboarding, support, terms of use, privacy, operations manual |
Care Kiro ties into real field work, so even small instabilities can feel big. Before adding new features, I want to see whether it feels like a product people can safely use.
I want real feedback to decide what gets fixed first. In particular:
Imagining features and bolting them on doesn't suit Care Kiro. Visiting nursing is already complicated, and the service shouldn't add to that.
Park Labs has services like FortuneToday that test an ad revenue model, and experiments like BrickQuest that were tested at a hackathon. Of all of them, Care Kiro comes closest to reducing friction in a real workplace.
There's still a long way to go. But now I have more than enough reason to get my hands moving again.