Blogs by Colt

Author: Colt Cruz
Date: March 16, 2026

This week’s progress on CalmSpace was again a bit slower than I would have liked. I’m still dealing with the sickness that hit me last week, so development time and energy were limited.

Even so, there were still a few meaningful steps forward.

Headphones Now Working With Masking

One of the biggest improvements this week was getting headphones working properly with the masking system.

The masking itself is still driven by the phone’s microphone, which listens to the surrounding environment and generates noise to counteract it. That core system hasn’t changed, but the way the sound is delivered makes a big difference.

Testing showed that the masking works much better through headphones than through the phone’s speakers. The sound feels more consistent and controlled, which makes the overall experience more effective.

This is important because many people use headphones or earbuds when trying to sleep in noisy environments.

Getting this working reliably moves CalmSpace closer to real-world usability.

Sorting Out Code Between Teammates

Another challenge this week involved cleaning up code differences between my work and Sora’s.

Whenever multiple people work on the same project, code structure and implementation choices don’t always line up perfectly. Merging and stabilizing everything required some extra time and attention.

It wasn’t the most exciting work, but resolving those conflicts helped keep the project stable and easier to maintain going forward.

Backend Direction

Originally I was planning to start building more backend functionality myself this week.

However, backend work has now been recommended to another teammate, which allows me to stay focused on the part of the app that currently matters most: the masking system itself.

That shift should help development move faster overall.

Focusing on the Core System

With headphones now functioning correctly, the next priority is making sure the masking system works as reliably and smoothly as possible.

Right now the system works, but there is still room to improve responsiveness and consistency. Since masking is the core purpose of CalmSpace, it needs to feel stable and dependable before anything else.

That will be my main focus going forward.

Possible UI and Theme Improvements

If time allows, I may also start experimenting with some theme adjustments and visual refinements.

CalmSpace is meant to feel quiet and supportive, so eventually the interface will need to reflect that atmosphere more clearly.

For now though, functionality still comes first.

Where CalmSpace Stands

At this point CalmSpace now:

• Runs directly on a physical phone
• Uses the phone microphone to generate adaptive masking
• Works reliably with headphones
• Supports multiple noise profiles
• Continues to improve through collaboration and code cleanup

Progress has been slower the past couple of weeks due to being sick, but the core pieces of the system are continuing to come together.

The focus now is simple: make the masking work really well.

Everything else will build on that.