Logbook

Lately, I’ve been spending time playing around with oneweek.dev, and I realized how much I simply enjoy showing up each day to work on something, anything that feels interesting or necessary in the little time I have left after my full-time job.

It makes me feel progress, even in small steps. It keeps me accountable to myself.

The idea

At some point, I thought: what if there was a way to visualize this consistency?
Something like a GitHub-style heatmap, but instead of commits, it would track daily logs, small updates, reflections, or learnings.

Right now, I’m still setting up the base here and handling most updates myself. But I imagine that one day anyone in the team might be interested taking over the day to share an update.

So the heatmap is more than a visual feature. It’s a symbol of showing up, whether that means working on a new idea, fixing something small, or even taking a mindful rest day.

Why it matters

When we don’t reflect, it can feel like we’re not doing enough.
But in reality, we do a lot of small things and all those things deserve a small acknowledgment, a small celebration.

That’s why I decided to bring the heatmap right into the landing page, highlighted in the first section. Because showing up matters.

Big or small, progress only happens when you show up.

Today we worked on editing a new promo video for our running niche app, kvikapp.com.

The video highlights the new feature has been built within a week after realizing its viral potential among runners who love sharing their workouts.

Most of the existing solutions on the market didn’t feel stylish, so we wanted to bring something more aesthetic and personal into the app.

The video outlines the preparation process — choosing running outfits, showing the environment and the app in action while completing a workout synced with Garmin. It also shows how users can share their route and stats automatically with clean, also animated templates.

This feature is still in beta testing, but we’re planning to move it to the main page soon to highlight its viral potential and use it as a key part of our product marketing strategy.

Watch on Instagram or TikTok.

Today I focused on building the language study flashcards part of langnotes.app.

This will be the space where users can actually review and repeat what they’ve saved in their collections.

Right now, I’m shaping the logic for how sessions are created, how cards are shown and flipped, and how progress might be tracked later.

It’s still early, but this part feels like the heart of the app where everything comes together into real learning flow.

After building the first working prototype of langnotes.app in a fast 24-hour flow of inspiration to build a personalized language learning experience with AI, study notes and flashcards, I decided to slow down a bit today to polish the UI and add a few features I really wanted before sharing it with the world.

Notes

• Still keeping everything in client-side storage for now. I’m experimenting with structure and flow before moving into authenticated API calls and backend storage.
• I keep AI model as gpt-3.5-turbo as the cheapest one for now to not spend much on the building phase.
• Used Web Speech API for text-to-speech for now, might consider switching to more natural model later.
• Added the option to create new pages inside each collection. I imagine collections as small books or magazines, and this change makes the whole experience feel more natural.
• Added missing translations. Localization and SEO are a big part of this project, so it’s now live in English, German, French, and Turkish. Once the base structure feels stable, adding more languages should be easy, one of the parts I enjoy most about this project.

The Library (with collections and their details) is now functional. It needs a few mobile tweaks, and after that, I’ll start reworking the Study section to organize flashcards better.

Feeling good about the progress, it’s slowly turning from a quick experiment into something real. 🎉

I’ve had the oneweek.dev domain sitting around for a while now. At first I thought I’d use it for a boilerplate or maybe a small community for fast prototypers, a space for people who love building and shipping ideas quickly.

But like most side ideas, it kept getting pushed aside by other projects and responsibilities.

The realization

A couple of weeks ago I had a small realization. We don’t need to build another full product around it.

This can simply be a living log of our journey at Noe Crafts; the things we build, the experiments we run, and what we learn each day while juggling full-time jobs and trying to keep the spark alive.

We love experimenting, trying new tools, maintaining the ones that work, and figuring out what’s the minimum, fastest, and cheapest way to bring an idea to life.

So that’s what this space will be: a logbook of progress, ideas, and lessons.

The structure

Today I created the first version of the Logbook section, which I’m personally most excited about but the rest also is ready with dummy data for now.

• 🪵 Logbook: short, journal-style notes with quick updates, learnings, and behind-the-scenes thoughts.
• ✍️ Blog: longer articles for deeper dives.
• ⚙️ Tools: small utilities we build for ourselves to help us build, ship, and market faster.
• 🛒 Shop: fun prints, small digital goods, and designs made for indie makers and builders.

The first entry

I even used our Markdown Editor tool to write this entry, which feels like the perfect way to start.

I’m just happy this is finally happening.

The goal isn’t perfection or big launches, just to keep showing up with even the smallest updates each day or week.

Stay tuned. 🚀