KeepRecord is like a database in a database, allowing you to build tables (definitions), relationships (links), fill in data (records) and use that to plan your weeks. Create weekly meal plans or record your exercises. All without a spreadsheet-like experience
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.
Report
π‘ Bright idea
I'm really loving the concept of KeepRecord! The idea of creating tables, relationships, and filling in data to plan weeks sounds super intriguing. I'm curious, how customizable are the forms that can be built with KeepRecord? Are there any specific industries or use cases you had in mind during development? Can't wait to explore this further!
Thanks a lot @iuliia_all
I've aimed to keep it as simple as possible. Currently, users can choose from the following data types:
* Text
* Number
* Boolean
* Link (to another record)
These options have met all my personal needs so far. Additionally, the app allows for customization of the form behavior when editing records, offering a choice between single-line and multi-line input fields. For viewing records, such as a recipe on your phone while cooking, the display format of each field can be adjusted as well:
* Raw text
* Markdown
* Clickable link (URL)
For instance, I utilize the Markdown option to enhance the appearance of personal notes attached to each recipe, which I find incredibly helpful.
Given that the app is designed for scheduling records, including repeated scheduling, it may not be well suited for cases that are transient, like a typical task list where tasks are frequently added and completed.
It's generally tailored to more personal use cases like scheduling recipes, workouts, events, etc.
KeepRecord
KeepRecord
Emma Intelligence
KeepRecord
WeInstaReply
KeepRecord
KeepRecord