KeepRecord - Build forms, fill & link data - plan your weeks | Product Hunt
source link: https://www.producthunt.com/posts/keeprecord
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Support is great. Feedback is even better.
"Many thanks for taking a look at KeepRecord. This project is a long-standing passion of mine. Being a daily user, there might be a bias towards certain features that seem less obvious but could be valuable for others. I'd love to hear your ideas on what you think is missing!"
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.
Congrats on KeepRecord, Timo! Love how it started with meal plans and grew from there.
Just wondering, how will you keep it simple for us as it gets bigger?
Excited to try it out for organizing my week. Awesome stuff!
@karanbhakuni Thank you for your kind words, Karan!
You've raised an excellent point. In my process of developing features, I always consider whether I can implement them without compromising efficiency and avoid excessive planning. Let me share an example: In an earlier version, I designed a generic filter builder for use in the planning phase. This builder was a distinct section within the app, allowing users to create pre-set filters with the ability to create complex conditions and multiple layers of relationships. These filters could be applied later in the planning process. However, after using the app extensively myself, I realized this approach to filtering had its drawbacks: 1. The pre-set filters were relatively "static," which could be limiting during planning when dynamic adjustment might be necessary. 2. The complexity of the filter system was ultimately unnecessary for everyday use.
To address these issues, I introduced simpler inline filters in a subsequent version that could easily be combined, improving both functionality and mobile usability.
Your question also seems to touch on the volume of data managed within the app. Speaking from my own experience, with currently over 300 records (recipes) stored, the ability to search and filter across most pages provides me with a sufficient overview.
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.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK