A journal of our progress behind the scenes.

 Exploring the Right Platform
We've been testing a range of low-code and no-code platforms to help bring our tools to life. Our priorities: HIPAA compliance, flexibility, strong data handling, and clean user experience for our caregiving teams. So far, several systems show promise — but we’re leaning toward those that allow us to customize without starting from scratch. 

 Glide: Beautiful, but Limited
We explored Glide for its visual simplicity and mobile-first design. It was quick to build with — and great for testing interface ideas — but unfortunately, it lacks HIPAA support and can’t handle the depth of functionality we need for staff and clinical documentation. 

 Testing, Not Guessing
We’ve been setting up sandbox environments in several platforms, including Glide, Betty Blocks, Thunkable, Microsoft Power Apps, Knack, Outsystems and Caspio. Each gives us something different — from strict compliance to creative freedom. We're running test flows like med passes, task charts, and client profiles to see what feels natural and what causes friction.

 Leaning Into Betty Blocks
Betty Blocks has emerged as a strong potential fit. It offers both HIPAA compliance and flexibility to build complex systems — like medication tracking, documentation logs, and care plan modules. We're now hoping to start working on a small pilot prototype to test caregiver workflows and backend structure. 

 Mapping the Core Modules
We’ve outlined the core modules that will form the foundation. Profile and access, Communication, Care Plans, eMAR, Documents, and Notes. Each one is being sketched with both caregivers and admin workflows in mind. Visual branding and icons are also in development to help users navigate easily across tools. 

 Thinking About Integration Early
Even at this early stage, we’re planning for future integrations. Synkwise, QuickBooks, Google Drive, and potential SMS/email tools are all on our radar. Building with integration in mind now ensures we won’t be locked into a silo later — and it keeps us aligned with the real-world systems our teams already rely on.