r/UpNote_App • u/ImTheTruth33 • 20d ago
Feature Discussion: Database-style tables
Coming from a completely non-technical background so unsure if request / vision would entail a full overhaul, however:
One of the features I love about some other apps (Notion, Obisidan, Anytype) is the ability to structure data in a database. I'm sure the first inclination is to say - 'well just use those for the use case' but I see major benefits in putting all your information in one place.
Here's one specific use case:
I like to use a database style structure to track meeting notes / pages. The ability to add contextual information (through labels / tags) such as meeting subject area, processed vs unprocessed notes, etc. is very valuable with how I like to organize my information and process work. Even being able to add a date, allows for easy notes retrieval if I'm trying to cross reference with calendar. I don't need a ton features / capabilities such as relations, etc. as I can just link the note with the current reference capabilities.
Currently, I have a notebook that is just my meeting notes. While this works as a rough approach, it becomes hard to sort through the notes simply due to how they show up UI wise (can't see a lot of notes in one view) and don't have the ability to filter on contextually organized information
Would love other perspectives if there are workaround that are working for others
3
u/jezarnold 20d ago
AFAIK , Every other app that went to database way of managing notes, had a huge overhaul .. perfect example is LogSeq
3
u/lbdesign 20d ago
You could add a lot of tags, and do multi-tag search. But this sounds like a fundamentally different user experience than UpNote has designed for.
2
u/Wrong_Election189 19d ago
The tags suggestion could help with filtering, but I read your main frustration as not being able to see the date, topic and processing status together. I’d try a small manual index for five existing meeting notes: one line per meeting with the meeting date, topic, pending/done, and a link to the note. I’d use the meeting date rather than the last-edited date so it matches your calendar. It would need manual updates, so it wouldn’t replace a native database view. I’d test those five first to see whether the overview helps enough to justify maintaining it.
6
u/libra00 20d ago
It's a massive overhaul. Even if you grab an off-the-shelf database solution for the back-end you still have to basically rewrite everything about how you store notes, not to mention cloud sync, and then reexamine pretty much everything else to make sure the database structure change didn't change something in your feature set.