Our team does a lot of our UI development in Storybook. If you are curious about how we manage our business logic, you can read more about how we build our UI components here.

Storybook has been working hard to improve its UI testing features and introduced integrated interactive testing in version 7, where you can build UI tests that can run in your preferred test runner. We decided to try this with our components, and this blog will go into what we have found so far with our experimentation.

A little history​

When first building out our website we did like many people do and directly accessed our hooks within components. There's nothing wrong with that but as the site grew, as our components file sizes grew, we realized we were running into a few walls. How can we make our components easier to explore and at the same time make our components smaller with the goal of better re-usability?

One of our core beliefs at Summer Health is that if we want do something as ambitious as to define a new standard of care we need our entire team to have mission-driven empathy. It is only with this mindset that we can create a compelling vision of what that world looks like, why it matters and work backwards on how we can make it reality.

Imagine the peace of mind of being able to connect with a pediatrician within just 15 minutes, around the clock, as a parent. That's exactly what we provide to our caregivers. In this blog post, I will describe how we designed the system to achieve this goal.

A little history​

As you've read in our previous Summer Health Dev Blog post, Summer Health is an early-stage start-up whose goal is to simplify healthcare and provide better access to doctors for patients. When we first started building our applications last summer our main focus was to move quickly while building a base for the future. At first, tailwind seemed like the right choice. If offered us a simple CSS utility interface to build out pages quickly and easily. In addition, there are several sites with well-documented tailwind recipes we were able to lean on. However, as time passed, we started to encounter issues with relying upon tailwind alone.

Four months ago, I embarked on a new adventure, transitioning from the world of classical violin to the dynamic realm of healthcare technology at Summer Health. The mixture of excitement and uncertainty was palpable. Today, I'm thrilled to share my reflections on my journey at Summer Health, giving you a glimpse into the extraordinary Engineering Team I've been fortunate to collaborate with.

Every pediatrician knows the strain of a cluttered and convoluted Electronic Health Record (EHR) system. The age-old EHR systems, teeming with irrelevant fields and buttons, can bring back painful memories. What exacerbates this is that these traditional EHRs are focused on appointments and billing instead of being focused on providing care.

Summer Health focuses on direct-to-consumer care that's available around the clock. We're not just streamlining healthcare for parents; we're tailoring it for the pediatricians so they can provide the highest quality care without being burdened by outdated tech.

At Summer Health, we're reinventing the world of pediatric care with a unique vision: to place a doctor in every parent's pocket. With an innovative platform that connects parents to a pediatrician within 15 minutes, our commitment to healthcare is as uncomplicated as sending a text message. This formidable challenge of integrating healthcare, technology, and convenience presents our team with a wealth of engineering problems. However, our growth-minded, problem-solving approach helps us continually rise to these challenges.