Vibe Coding Projects

I build software because I want to use it myself.

My projects usually start with a concrete need or simple curiosity. With AI, I can quickly turn ideas into software of my own, see what works and build tools that fit me and my everyday life.

Why I do this

Vibe coding is DIY for the digital age.

What appeals to me is the ability to shape digital tools myself and adapt them to my own needs. It is about independence and control over my data, but just as much about the act of building.

I can explore new technologies and ideas, experiment, change things and learn along the way. And an idea in my head can quickly become something I actually use.

Selected projects

From a personal need to a tool of my own.

$ ./gradlew assembleDebugBUILD SUCCESSFUL$ git statusOn branch main
A simplified view of the mobile development workflow
AndroidDeveloper ToolSSH

PocketDev

Use my daily commute to keep working on my software projects.

I spend part of every workday on a bus. I want to use that time to work on my apps. My development machine is at home, while my phone is already in my hand.

PocketDev makes the important development workflows accessible directly from the phone. I can switch projects, follow changes, start tests and builds, install apps and control running processes.

The idea behind it: My development workflow should fit my everyday life. The lower the barriers between an idea and the next step, the easier it becomes to use my time for developing, experimenting and learning.

View public repository →
BOOK
PhotoTitle + authorLibrary
From a book photo to a digital collection
BooksCameraMultimodal AI

Personal Library

Keep track of my book collection and rediscover it.

With more than 600 books, it is difficult to keep track of what is actually sitting on my shelves. Personal Library makes the collection searchable and lets me filter, group and rediscover titles that have slipped out of view.

Adding a book is simple: I take a photo directly in the app. Title and author are recognized, and additional information is enriched from publicly available internet sources. I can then review the entry and add it to my library.

The idea behind it: A digital library creates a new way to access the books I already own. Simple capture helps keep the collection current. Search, filters and grouping then turn it into something I can explore and rediscover again and again.

View public repository →
FreyaOSBooksAndroid LLM Service1 local model
One shared AI capability for several apps
Local AIAndroidInfrastructure

Android LLM Service

Local AI as shared infrastructure for my apps.

I want to use language models in several of my own applications while choosing different local resources depending on the task. A smaller model can run fully offline on the phone, while a larger model on my own server is available for more demanding tasks.

Android LLM Service provides a shared foundation for this on the phone. Applications such as FreyaOS, Personal Library and LocalChat can use local AI without each needing to bring its own infrastructure.

LocalChat is both an application and an experimentation space. Alongside fully local chat with multiple conversations and memory, I am building ways to systematically test and benchmark different models and configurations.

The idea behind it: I am interested in how local AI can become useful personal infrastructure. Which tasks can run directly on the phone? When is a larger model on my own hardware worth it? And how can shared infrastructure make these capabilities available to several applications?

Personal history
Health Connect → own database → backup
Health data on my own hardware
HealthAndroidData Sovereignty

Health Data Hub

Own and understand my health data.

Wearables collect years of data about my body, activity, sleep and habits. I want to make that data useful to me, independently of a manufacturer's app and cloud.

Health Data Hub creates a personal data foundation for this. I can follow developments over longer periods and relate different aspects to each other. That lets me explore my own questions, for example how sleep, movement and training are connected.

The project is evolving from a collection of my wearable data into a tool for exploring and understanding that data.

The idea behind it: The value of personal health data lies in being able to keep it over time and ask my own questions of it. Health Data Hub combines data sovereignty with the ability to discover insights for myself.

PhoneBluetoothGoodVibesCustom control → hardware
Direct control of connected hardware
AndroidBluetoothHardware

GoodVibes

Use connected hardware in a way that fits how I actually want to use it.

Many connected devices come with their own app, which also defines how the device can be used. I wanted to see what happens when I take control of that software layer myself.

GoodVibes connects directly to compatible hardware over Bluetooth and gives me my own interface for controlling it. I can shape workflows, interaction and features around what makes sense to me. What started as simple control has grown into a stable app with its own patterns, multiple simultaneously connected devices and a much more developed interface.

The idea behind it: With connected hardware, software determines a large part of what a device can actually do. If I can shape that software myself, I can also change and extend how an existing physical product is used.

Granada
Interactive travel photos on a map
PhotographyMapsStatic Site

PhotoMap

Bring travel photos back into the context where they were created.

Travel creates a lot of photos, but in a classic gallery it is easy to lose the connection between individual places and the route a journey took.

PhotoMap uses the location data in my images and shows them on an interactive map. This lets me explore trips geographically, find places again and view photos in their temporal and geographic context.

The idea behind it: Photos tell me more when their place and the course of the journey remain visible. The map adds a spatial perspective to the chronological order of the images and makes past trips accessible in a different way.

View public repository →

How I work

Most projects begin with something in everyday life that occupies or interests me. Because I am also the user, I can quickly tell whether an idea is actually useful.

01

Build something real quickly

I try to get to a working version early. As soon as I can actually use something, abstract considerations become concrete. I see what works, what gets in the way and which questions I had not even thought to ask before.

02

Use it and keep developing it

Many decisions only emerge through daily use. My apps therefore do not evolve according to a fully fixed plan, but through being used. What proves useful stays. New needs and possibilities lead to the next changes.

03

Deliberate Play

For me, vibe coding combines purposeful building with playful exploration. It creates knowledge and new ideas, and sometimes an experiment turns into a tool that becomes a lasting part of my everyday life.

Ideas become things I can use.

Vibe coding has greatly reduced the distance between an idea and working software. Something that starts with “Surely this should be possible” can quickly turn into something I can try, change and integrate into my everyday life.

The result can be tools that solve concrete needs, experiments that teach me something, and new ideas for the next project.

More public projects on GitHub