Hi, I’m Timo, creator of KeepRecord. I’ve created KeepRecord out of a personal need. It initially started as a meal planning app, where I could schedule my personal recipes for a week. It was plain simple as it would help me make decisions on what to eat next, based on a simple formula: variety. I was able to quickly see recipes I did not schedule that often. This was sufficient for me to make my weekly meal plans as I often times just need some inspiration, not a perfect suggestion. As I used it for a while, I realized that it has the potential to be much more generic. Why only schedule recipes, when I could also schedule workouts or other things? And why shouldn’t I be able to configure what data I attach to a recipe? The idea for KeepRecord was born, a weekly planning tool where it’s possible to create your own data structures. Over the years I’ve rewritten the app multiple times, starting at Golang with Vue, over to Rust with Svelte and also Hasura (GraphQL Server) with Golang and Svelte. After a long SPA journey I found myself reinventing the wheel way to often and basic features took a long time to implement, while other features were never really at the stage I was satisfied with. I was absolutely annoyed by the state of the auth feature and its many edge cases. I stumbled across Laravel, Livewire and Filament and realized this had everything I need, even though I’ve been neglecting PHP in the past for being old-fashioned and too inconsistent. With all of my experience, also at my day job, I’ve realized that PHP with Laravel was much more complete than everything I’ve came across so far, so I decided to give it a try. Within 3 weeks I had most of the features from the previous version working quite well. But of course, many more hours went into it. I hope that others may find use KeepRecord as much as I do. KeepRecord is also inspired by AirTable and its concepts, though it’s intentionally not focused on a spreadsheet-like experience and promotes working with individual records more.