Care-kiro Evolution - From Nurse App to Platform

An important realization while developing Care-kiro.

💡 Key Discovery

I was building an app for visiting nurses,

but realized station manager features are essential too.

Why Manager Features Are Needed?

Even if a nurse says "I want to use this app!",

without station (office) support, it's impossible to use 100%.

For example:

A personal app has its limits.

🔄 Pivot: From App to Platform

So I'm changing direction now.

- Before: Personal work management app for nurses

- After: Platform connecting nurses + station managers

📈 The System Has Grown

Started as a simple app,

now it's become a structure with 5 interconnected systems.

⚙️ CI/CD Automation

As a solo developer, there's no surviving without automation.

Built a CI/CD pipeline with GitHub Actions:

git push → auto detect → deploy all 5 systems

- detect-changes: Detect changed files

- deploy-landing: Deploy landing page

- deploy-web: Deploy web app

- deploy-station: Deploy station manager page

- deploy-console: Deploy operator console

One push deploys everything.

🚀 Development Status

Focusing on the station manager page right now.

Station manager page main features:

🎯 Lessons Learned

B2B SaaS must consider all stakeholders.

Don't just look at individual users.

First visualize how it will be used within the organization.

And for solo development, automation is not optional but essential.

As systems grow, manual deployment becomes impossible.

This realization helped clarify the direction a bit more.

Whether it can truly become a service that both nurses and stations use — that remains to be seen.