The MyWisdom redesign used Flutter, Computer Vision, and AWS to rethink how older adults stay safe at home. Here’s what building a healthcare platform for the most accessibility-demanding users on the planet actually requires — and why most digital agencies get it wrong before the first wireframe
Valeria Varlamova — Project Manager, Phenomenon Studio February 24, 2026 14 min read
Key Takeaways
The caseMyWisdom is a US platform helping older adults live safely at home. Phenomenon Studio redesigned the mobile app and delivered Flutter-based front-end development in a 5-month engagement using Python, Computer Vision, Java, Spring Boot, and AWS.
The insightMost “accessible” interfaces are designed accessible as an afterthought. Phenomenon Studio designed for a 70+ demographic as the primary use case — adjustable modes, large tap targets, low cognitive load — not as an accessibility checklist but as the core UX brief.
The process pointIn my project work managing healthcare apps at Phenomenon Studio, the teams that succeed are the ones that test with real users from the target demographic before anything ships, not after. Usability testing with older adults and caregivers was built into the sprint cycle, not bolted on at the end.
The scopePhenomenon Studio handles the full stack for healthcare digital products: web app development, hybrid mobile app development, EHR development, AI chatbot solutions, healthcare website development, brand identity development, MVP builds, and front end web development services — all under one process.
There’s a design assumption buried in most mobile app briefs that rarely gets challenged: that the person using the product is between 25 and 40, reasonably comfortable with smartphones, and interacting with the app in a calm, well-lit environment with full attention and no physical limitation. That assumption shapes everything — tap target sizes, type hierarchy, information density, onboarding length, error state design. And for the overwhelming majority of consumer apps, it’s roughly correct.
MyWisdom is not one of those apps. The platform helps older adults live safely and independently at home, using sensors and cameras to detect anomalies — a fall, an unusual period of inactivity, a missed routine — and alerts a trusted circle of family members or caregivers. The primary end user is in their seventies. They may have reduced vision, reduced fine motor control, reduced comfort with technology. They are often looking at the app in a moment of mild confusion or genuine emergency. The design brief, if you’re honest about it, is: build something that works for the most demanding user on the planet, in the most stressful moment they’ll encounter.
We took that brief seriously at Phenomenon Studio. The result is a redesigned mobile platform that passed usability testing with older adults before any feature was considered done. Here’s what that actually meant — for the design process, the development stack, and the choices a website development agency has to make when the stakes are genuinely high.
Why Senior Care UX Is a Completely Different Design Problem
“When we benchmarked MyWisdom against Ring, AlfredCamera, Faceter, and Camy, the finding was consistent: every existing platform was built around property protection, not people. Strong technical features, but almost no consideration for how an anxious 75-year-old actually uses a smartphone. That gap was the brief. We designed for the edge case that the whole market had ignored.”
Valeria Varlamova
Project Manager · Phenomenon Studio
We analyzed four competing monitoring platforms before a single MyWisdom screen was designed. Ring, AlfredCamera, Faceter, Camy — all of them excellent products for their intended users. All of them built with the assumption that the person setting up and managing the monitoring system is a competent, mid-career adult who will spend thirty minutes reading documentation if needed. None of them were built for someone who finds a three-step onboarding flow overwhelming.
The competitive analysis shaped our brief in a specific way. We weren’t looking for features to copy. We were cataloguing what every competitor had missed, and then we were going to build for exactly that gap. Less surveillance apparatus, more safety companion. Less control panel, more clarity about what’s happening right now and what needs a response.
This is what user experience design services actually mean at the strategic level: the research doesn’t just inform the design, it defines what the product is competing for. Most UI UX design agency briefs focus on feature parity. The MyWisdom brief, after research, was about emotional positioning — and that distinction changes every visual, structural, and interaction decision that follows.
Why is designing for older adults harder than designing for a general consumer audience?
Because the margin for error is smaller. Younger users recover from confusing interfaces — they tap around, figure it out, move on. An older adult with reduced vision or motor function who can’t complete a task may conclude that technology “isn’t for them” and stop using the product entirely. Every ambiguous label, every small tap target, every buried setting is a potential exit point. Designing for this demographic means designing with zero tolerance for unclear affordances.
The MyWisdom Case: A Platform Rebuilt for Real Human Needs
Case Study — Phenomenon Studio
MyWisdom: Digital Platform for Safer, More Connected Aging · USA
MyWisdom uses sensor networks and computer vision to detect falls, prolonged inactivity, and anomalous patterns in an elderly person’s daily routine — then alerts a trusted circle of family members and caregivers. Phenomenon Studio was brought in to redesign the mobile app and deliver cross-platform Flutter development.
5 months
Design sprint + Flutter front-end development delivery
3/3
Usability tasks completed by older adult test participants without confusion
100%
Core screens redesigned with scalable reusable component system
Stack: Flutter · Java · Spring Boot · Python · WebSocket · Computer Vision · AWS · PostgreSQL · Redis · Docker · Swagger · Liquibase
The project ran in two distinct phases. The first was a two-sprint redesign where we built the new design system, redesigned core screens, and validated everything with actual users — older adults and family caregivers, not design team members simulating the target demographic. The second phase was Flutter front-end development, where we discovered that parts of the backend were still pending implementation, which forced iterative redeployment cycles and close coordination with the original development team.
That second-phase reality is worth pausing on, because it’s common on healthcare platform builds and rarely discussed honestly in agency case studies. The back end isn’t always done when front-end development begins. Dependencies shift. Business logic that seemed settled turns out to be in flux. In my project experience managing these engagements, the teams that handle this well are the ones with a genuinely collaborative relationship with the client’s internal developers — not a fixed-scope handoff mentality that breaks down the moment something unexpected surfaces.
We resolved each iteration quickly because the communication channel was open and the development environment was properly containerized with Docker from the beginning. That’s a setup choice that looks like overhead at the start and saves days of debugging later.
Phenomenon Studio — mobile app design and Flutter development for the MyWisdom senior care platform. February 2026.
Accessibility as a Core Architecture Decision, Not a Feature
Most accessibility implementations go like this: the product gets built, design reviews it against a WCAG checklist, the engineering team adds an “Accessibility Settings” screen somewhere in the options menu, and the product ships. Users who need accessible features have to find those settings themselves — usually in a moment of frustration when the default presentation isn’t working for them.
We took the opposite approach on MyWisdom. Adjustable text size, high-contrast color mode, and larger tap targets weren’t placed in a settings screen. They were surfaced prominently in the interface, because the demographic we were designing for shouldn’t have to hunt for the version of the app that actually works for them. The default state should be accessible. The settings exist for personalization, not remediation.
What specific accessibility decisions went into the MyWisdom redesign?
Larger tap targets across all interactive elements — minimum 48×48dp per Google’s Android guidelines, with most critical actions exceeding that. Text size controls placed in a visible location on first use, not buried in settings. A high-contrast color mode accessible from the home screen. Simplified icon labels using plain language rather than icon-only navigation. Reduced information density per screen — one primary action per view wherever structurally possible. Every decision tested with participants from the 65+ demographic before finalizing.
Internal Research — Phenomenon Studio, 2025
Across 14 healthcare mobile and web app projects completed over 30 months, products that conducted structured usability testing with users from the actual target demographic (rather than internal team proxies) during the design phase required 47% fewer post-launch accessibility-related revisions. In projects where testing was delayed until post-launch, the average number of critical accessibility issues found in the first 90 days of live usage was 8.3. In projects with pre-launch demographic testing, that number dropped to 2.1. The difference isn’t design skill — it’s process discipline.
The Tech Stack Behind a Healthcare Platform That Has to Work Every Time
MyWisdom isn’t a productivity app where a bug means someone reschedules a meeting. It’s a safety platform where a bug means an alert doesn’t reach a caregiver when an elderly person has fallen. The engineering decisions have to reflect that. Here’s how the technology choices on this project mapped to the safety and reliability requirements:
| Technology | Role in MyWisdom | Why This Choice | What It Enables |
| Flutter | Cross-platform mobile front-end | Single codebase for iOS + Android; near-native performance; strong accessibility widget support | Consistent UX across device families; faster release cycles; hybrid mobile app development without quality compromise |
| Java + Spring Boot | Core backend services | Enterprise-grade reliability; strong typing; mature ecosystem for healthcare-grade Java web development services | Stable API layer; role-based access control; audit trail infrastructure |
| Python | Data processing and Computer Vision | Best-in-class ML library ecosystem; Python web development services for sensor data analysis | Fall detection algorithms; activity pattern analysis; anomaly detection from camera feeds |
| WebSocket | Real-time alert delivery | Persistent connections for push notifications without polling latency | Instant caregiver alerts; live sensor status updates |
| AWS | Cloud infrastructure | HIPAA-eligible services; auto-scaling; reliable uptime SLA | Compliant data storage; geographic redundancy; enterprise web app development services grade reliability |
| PostgreSQL + Redis | Primary DB + cache layer | PostgreSQL for structured health data; Redis for session state and real-time performance | Fast alert response times; query performance under load; dashboard ui design data feeds |
| Docker + Liquibase | DevOps and DB migrations | Containerized environments for consistent deployments; versioned schema changes | Iterative redeployment during back-end dev cycles; no schema drift between environments |
What Phenomenon Studio’s Healthcare Capability Stack Actually Covers
MyWisdom represents one type of healthcare engagement — mobile platform redesign and development for a B2C safety product. But the studio’s healthcare capability runs significantly wider than that. Here’s a clear picture of the services that map to healthcare and digital health clients:
- EHR development — electronic health record systems with role-based permission architecture, audit logging, and HIPAA-compliant data handling. Built on React, Node.js, Python, or Java depending on integration requirements with existing clinical systems.
- Healthcare website development — from medical practice website design to complex web portal development services for multi-provider healthcare organizations. Architecture built for WCAG compliance and GDPR consent management from the first sprint.
- Healthcare website design company work — UI and UX design services for patient-facing platforms, clinical dashboards, telemedicine interfaces, and caregiver apps. User experience design services rooted in demographic-specific research rather than generic UX patterns.
- AI chatbot solutions — custom chatbot development services for symptom triage, appointment booking automation, and patient FAQ handling. AI chatbot services designed as clinical UX, not chatbot widgets bolted onto a healthcare website.
- Best mobile app development company work for health platforms — hybrid mobile app development with Flutter and React Native, handling the full cycle from product discovery to deployment across iOS and Android.
- Minimum viable product development services for digital health startups — rapid MVP development (6–10 weeks) and custom MVP development for more complex scopes. What is MVP in software development for healthcare means careful scoping — regulatory requirements mean some architecture decisions can’t be deferred.
- Visual branding and brand identity development — for healthcare brands that need to communicate clinical authority and human warmth simultaneously. Visual branding and identity design as a product discipline integrated into the healthcare website development process.
- Web app design and front end web development services — dashboard ui design for clinical analytics, progressive web app development services for cross-device health monitoring, and ReactJS web development services and Node js web development services for the application layer.
Phenomenon Studio — Process & Work
Choosing a Digital Partner for Healthcare: What Actually Matters
The decision to outsource web development services for a healthcare product is a different calculation than outsourcing a marketing site or a SaaS dashboard. The compliance exposure is higher, the user vulnerability is higher, and the gap between “technically functional” and “actually safe to deploy” is wider. Here are the criteria that I’d apply when evaluating any web development services company for a healthcare engagement:
Do they understand the regulatory landscape — not just HIPAA as a concept, but the specific implications for data architecture, form handling, third-party integration, and audit logging? Do they have a process for testing with representative users from the clinical demographic, or do they rely on internal team proxies? Can they articulate the difference between what is MVP in software development for a consumer app versus for a healthcare platform — specifically, what can’t be deferred to a later version when patient safety is involved?
And practically: do they run design and development in parallel or sequentially? Sequential is slower and produces more interpretation errors. Parallel is harder to manage but consistently produces better outcomes on complex healthcare products. We run parallel at Phenomenon Studio. It’s why the MyWisdom timeline was five months for a complete redesign plus Flutter development on a platform with a twelve-component tech stack.
For clients in the US searching web development services near me or specifically seeking healthcare-focused web design and web development services, geographic proximity matters less than process alignment and compliance certification. The studio operates from offices in Poland, Estonia, Switzerland, Canada, and the US — with async-first workflows and structured sync checkpoints designed around the client’s clinical and development schedule.
Questions Worth Answering
What is the difference between hybrid mobile app development and native app development?
Hybrid mobile app development uses a single codebase — like Flutter or React Native — to deploy across iOS and Android, reducing cost and development time. Native development writes separate code per platform, which delivers better performance for graphics-heavy or hardware-intensive applications. For most healthcare apps, hybrid with Flutter is the right choice: near-native performance, cross-platform reach, and consistent UX on both device families.
How does Phenomenon Studio approach accessibility in mobile and web design?
Accessibility starts in research, not as a checklist at the end. For MyWisdom, we designed adjustable text sizes, high-contrast modes, larger tap targets, and clearer label hierarchies as core UI decisions. We also conduct usability testing with users from the actual target demographic — in this case, older adults and family caregivers — before any feature ships.
What does Phenomenon Studio’s web app development process look like for healthcare clients?
For healthcare clients, the process starts with a deeper research phase than usual: we analyze how the specific patient or caregiver demographic uses technology, benchmark competitors with a focus on accessibility and trust signals, and map emotional states at key interaction points. Design follows research, not the other way around. Development uses HIPAA-compliant architecture, audit-trail logging, and role-based access control as baseline requirements.
Can Phenomenon Studio work as a website development agency for small healthcare startups?
Yes. The studio works with clients at different scales — from early-stage digital health startups building their first patient-facing product, to established healthcare platforms scaling to new markets. Minimum viable product development services, rapid MVP builds, and full product development are distinct engagement models depending on budget and stage.
What tech stack does Phenomenon Studio use for complex healthcare app development?
For MyWisdom, the team used Flutter for cross-platform mobile development, Java and Spring Boot for the backend, Python for data processing and computer vision logic, WebSocket for real-time alerts, PostgreSQL and Redis for data management, and AWS for cloud infrastructure. Docker, Swagger, and Liquibase completed the DevOps and documentation layer. Stack selection always follows the clinical and performance requirements of the specific project.