Parenting is a team effort—especially when grandparents are involved. In the early days of caring for our baby, my spouse and I faced a common challenge: coordinating feedings and diaper changes across caregivers. Did we already log that last bottle? Did Grandma give the baby a feeding right before nap time? These small but essential details were getting lost in the shuffle.

To solve this, I decided to learn Alexa development and create a custom skill that could help us seamlessly track and share this information.

Why Alexa Development for Shared Baby Care?

As busy caregivers, we needed a system that everyone could use—parents and grandparents alike. Writing notes on paper or texting updates felt clunky and error-prone. Alexa provided the perfect solution: a hands-free, voice-activated tool that could capture feeding and diaper change logs in real time.

Here’s why Alexa made sense for us:

• Accessibility: Voice commands made it easy for anyone, even with hands full, to log updates.
• Shared Data: Logs could be centralized so everyone had access to the same information.
• Convenience: Alexa is already a household name, and everyone was comfortable using it.

Getting Started: My First Steps in Alexa Development

I had no prior experience with Alexa development, but I did have some experience with Google Cloud for hosting other projects. Additionally, I utilized AI tools to assist in programming the app, which helped streamline the development process and provided solutions for complex challenges. Before diving into development, I explored existing tools for tracking this information. However, I didn’t feel comfortable using an Alexa app without many reviews, and many iOS apps that were recommended came with a monthly cost, which didn’t feel worthwhile for our needs. This led me to create a custom solution that fit our family’s specific requirements. Furthermore, I wanted to integrate with a shared tool my partner and I were already using—Notion—to ensure a seamless and familiar experience for everyone.

For Alexa, I started exploring:

• Alexa Skills Kit (ASK): A powerful toolset for creating custom voice applications.
• Google Cloud Functions: To initially manage the backend logic of my skill. Later, I moved to Amazon Lambda, which opened the door for more native functions and significantly reduced latency issues.
• Node.js: The language I used to build the functionality.

Setting up the development environment was an adventure in itself, but learning how Alexa handles intents, slots, and utterances was eye-opening. It made me realize the importance of clear and intuitive voice commands.

Designing a Skill for Team-Based Baby Care

The primary goal was to create a skill that anyone in the caregiving team could use to log and retrieve information effortlessly.

Core Features:

1. Logging Feedings:
   Commands like "Alexa, ask Baby Tracker to log a feeding at 2 PM, 5 ounces, bottle-fed."
2. Tracking Diaper Changes:
   Commands like "Alexa, ask Baby Tracker to log a dirty diaper at 4 PM."
3. Retrieving Logs:
   Questions like "Alexa, ask Baby Tracker when was the last feeding?" or "How many diaper changes today?"

Integrating Notion:

Since we were already using Notion for tracking, I looked into ways to sync Alexa logs with our existing system. Using APIs and automation, I connected the Alexa skill with Notion so that all logs were automatically updated in our shared Notion database. This ensured everyone could access the latest information, whether they were using Alexa or viewing the logs on their phones.

Challenges and Breakthroughs

Developing a multi-user system wasn’t without its hurdles:

• Data Synchronization: Making sure logs updated consistently between Alexa and Notion.
• Natural Language Processing: Making sure the skill understood different phrasing, like "log a bottle" vs. "record feeding."
• Handling Past Feedings: One of the biggest challenges was processing various ways of phrasing requests for past feedings. For example, users might say "log a feeding from yesterday at 2 PM" or "record a bottle from earlier today at noon." I spent significant time fine-tuning slot values and intent matching to ensure the skill could interpret these requests accurately.

Learning About Alexa’s Limitations

One significant challenge was working within Alexa’s 8-second timeout limitation. This required me to avoid complex database queries and multi-step processes. I streamlined the backend logic to make interactions more efficient, optimizing both the skill’s architecture and data handling.

Lessons Learned

This project taught me more than just Alexa development. Here’s what I gained:

• Technical Skills: Understanding Alexa’s API, working with Google Cloud, as well as AWS Lambda,  and using Notion's API.
• Collaboration: Building a tool that improved teamwork among caregivers.
• Problem-Solving: Addressing real-world challenges, like keeping logs simple but effective.

On a personal level, it deepened my appreciation for technology’s role in making parenting just a little easier.

This side project has been a rewarding experience, blending my understanding of programming with the goal of improving my family’s life during a time of great transition. Adapting technology to meet our evolving needs as new parents has been both challenging and deeply fulfilling. It’s amazing how a few voice commands can simplify life and improve coordination across a caregiving team.

If you’re a parent or caregiver, I encourage you to explore Alexa development—who knows what challenges you might solve for your family?

‍