My Supernotes Experience: A Two-Week Journey

[ivomota]

After using Supernotes daily for the past two weeks, I’ve found it to be an incredibly promising note-taking and productivity app. The overall experience has been impressive, but I’ve identified a few potential improvements that could enhance the user experience.

What I Love About Supernotes

• Intuitive interface
• Smooth note-taking experience
• Flexible organization of cards
• Clean and minimalist design

Suggested Improvements

While the app is already excellent, I believe these features could take Supernotes to the next level:

1. Enhanced Todo and Line Management

   • Implement a feature to move todos or lines up and down easily
   • Suggestion: Add a button on the mobile keyboard or a key combination for quick reordering

2. Archiving Functionality

   • Introduce an archive option similar to Google Keep
   • Allow users to archive cards instead of just hiding them
   • Ensure archived cards remain searchable but don’t clutter the Home screen

3. Alias Creation

   • Add the ability to create aliases for cards or links
   • This would improve navigation and cross-referencing

4. Incoming Links Suggestions

   • Develop a feature to suggest related or incoming links
   • Help users discover connections between their notes more easily

Conclusion

Supernotes has quickly become an essential tool in my daily workflow. These suggestions come from a place of appreciation and excitement about the app’s potential. I’m looking forward to seeing how the app evolves and continues to improve.
I will continue to use it and will be back with more feedback when I have used it for more days.

Cheers to the Supernotes team!

[tobias]

Hi @ivomota, really happy to hear you’re enjoying Supernotes!

That’s some wonderful feedback. You’ll be happy to hear that 3 out of the 4 improvements you’ve suggested partially exist – seems like we need to improve our help center or tweak those features so they’re more obvious

1. Moving Lines – on Desktop can hold down ALT↑ / ↓ to move lines quickly. There’s no way to do this on Mobile at the moment, but we’ve been looking into it.
2. Archiving – You can archive cards within parent cards already, but they will show up within the Home collection (unless you want to add a customised “Non-Archived Home” collection that removes them). The reason we did this is that cards can be in multiple parents, and then you may want to archive a card in one but not in another.
3. Alias Link Creation – You can modify the names of links already when linking cards inside the content of another card. However you can’t assign aliases by default from cards, one of the biggest reasons of this is for simplicity. Try adding tags and or aliases within the content of a card – since our search already indexes these properties. If you’re finding it hard to find cards, let us know some specific reproducible use cases and we’ll see how we can improve it.
4. Incoming Link Suggestions – We’ve aware of this feature and it’s been suggested before. It involves us sharing all your cards with AI, which we’re currently not enthused about due to privacy concerns and it also won’t work offline. However with Apple and other Windows beginning to support local only models, it may become possible to do this on your device at some point in the future.

I hope that helps! Let us know if you have any further feedback

[mjax]

Aliases is something I miss coming from Obsedian. But it requires extra meta data on each card.

[ivomota]

Thank you for your reply @tobias

@tobias

Moving Lines – on Desktop can hold down ALT↑ / ↓ to move lines quickly. There’s no way to do this on Mobile at the moment, but we’ve been looking into it.

Oh I didn’t know about that. Very cool. I hope we can have an action button on the mobile keyboard to do that to on mobile.

@tobias

Archiving – You can archive cards within parent cards already, but they will show up within the Home collection (unless you want to add a customised “Non-Archived Home” collection that removes them). The reason we did this is that cards can be in multiple parents, and then you may want to archive a card in one but not in another.

Oh cool! But I would like to have an easier command or action to do that.

@tobias

Alias Link Creation – You can modify the names of links already when linking cards inside the content of another card. However you can’t assign aliases by default from cards, one of the biggest reasons of this is for simplicity. Try adding tags and or aliases within the content of a card – since our search already indexes these properties. If you’re finding it hard to find cards, let us know some specific reproducible use cases and we’ll see how we can improve it.

Yeah I think you are right but coming from Obsidian I miss the simplicity of the use there. Same as @mjax

@tobias

Incoming Link Suggestions – We’ve aware of this feature and it’s been suggested before. It involves us sharing all your cards with AI, which we’re currently not enthused about due to privacy concerns and it also won’t work offline. However with Apple and other Windows beginning to support local only models, it may become possible to do this on your device at some point in the future.

Yes I would prefer the option of running that locally instead of send it to IA. I think we are closer than ever to have that.

[tobias]

Awesome, thanks for the further feedback @ivomota and @mjax, we’ll see what we can do.

Re. aliases I just had a quick idea, you can just add a quick <!-- aliasName1 aliasName2 --> at the start of a card. Since it’s in a HTML comment it won’t display in render, but it will still be indexed as part of our search algo as we search the markup not the HTML.

[ivomota]

Oh! This is an amazing hack really like it.
Thank you @tobias

[tobias]

No worries, that’s what we’re here for. You’ll notice a little bug with the <!-- ligature in the current version of Supernotes, but we’ve fixed that for the update dropping next week

[JohnCP]

Would multimarkdown headers create the necessary metadata for such a feature? I’ve never used Obsidian but I’d like better table support via multimarkdown. I may make a feature request for that

[mjax]

I’m not familiar with multimarkdown headers. But as a purist, I would like meta data (such as aliases) to not be part of the main content of the note. Tobias’s workaround should work for now.