Building a nursing-care smartphone app plus admin console end to end with Laravel + React Native, from design through operation

What changed

• Digitization rate of field records
  Nearly full switchover
• Aggregation workload on the admin side
  Reduced
• Facilities using the app
  Expanding via phased rollout

Challenge

Many staff on the nursing-care floor are not accustomed to IT, and an app will not take hold unless it can be used with the same feel as the paper-based routine. Headquarters, on the other hand, wanted solid administrative features—aggregation, report output, per-facility permission management, and so on. "Ease of use in the field" and "ease of management at headquarters" are inherently a trade-off, and leaning too far toward one side breaks the other. Furthermore, with an eye on rolling out to multiple facilities, a mechanism to lower the operational cost of adding a facility had to be built in from the start.

Approach

1. 01 Observed field staff's movement patterns and pared the input fields down to the bare minimum
2. 02 Implemented a shared iOS/Android app with React Native and designed a 'tap-centric UI' premised on one-handed smartphone use
3. 03 Built the admin console and reporting features with Laravel + AWS, separating the responsibilities of the field and headquarters
4. 04 Unified the development, staging, and production environments with Docker to automate deployment when facilities are added
5. 05 Structured permission management along two axes—facility × role—so it can flexibly handle organizational changes and facility additions
6. 06 Set a phased rollout plan, expanding to the next facility while confirming adoption

Key success factors

Observing field movement patterns

We actually observed the movement patterns of field staff unaccustomed to IT and pared the input fields down to the bare minimum.

A tap-centric UI

We committed the React Native app side to 'tap-centric, minimal input,' lowering the barrier to adoption.

Separating field and headquarters responsibilities

We split responsibilities between the field app and the headquarters console so that the convenience of one side would not distort the other.

Repeatable facility rollout

By unifying the environment with Docker + AWS, we kept the rollout work for adding a facility from depending on individuals.

Solution

On the field side, we committed the React Native app to "tap-centric, minimal input," and had the entered data aggregated and turned into reports by the Laravel-side admin console. We set up the operating platform with AWS + Docker, making rollout smooth when facilities are added. At the facilities that adopted it, nearly all field records were digitized, and headquarters' aggregation workload dropped substantially. Through a phased rollout, we can grow the number of facilities while running a cycle of confirming adoption.