Show HN: I wrote a local-first notes app for Mac, with data longevity in mind(noteship.com)
noteship.com
Show HN: I wrote a local-first notes app for Mac, with data longevity in mind
https://noteship.com
104 comments
This looks really cool.
But my pet peeve is hidden pricing for paid products. If it's worth buying, then show the price up front. I can't easily view the price anywhere on the website, and it's not displayed on the App Store description either. I was ready to download the app and try it out if I could view this information up front
But my pet peeve is hidden pricing for paid products. If it's worth buying, then show the price up front. I can't easily view the price anywhere on the website, and it's not displayed on the App Store description either. I was ready to download the app and try it out if I could view this information up front
To be fair to OP, Apple makes it dead easy to see how much the IAPs are for a given app (in the case of this one, $2.49 monthly or $24.99 yearly).
Apple does, but the product's website does not. As the above poster was pointing out: if the product is worth paying for the Op should make that clear.
If a product is available in the Mac App Store only, it gets tricky because you can provide the US price, but all other prices are generated by Apple in relation to the US price for other regions. This can cause confusion. Been there, done that. It's a tricky situation even for the developer.
Exactly. I just added the pricing details in USD and will figure something out.
Sure, the product's website doesn't display the price, and I agree that it should, but I was replying to this:
> it's not displayed on the App Store description either.
Developers don't need to (and, imo, shouldn't) put pricing in the App Store description, because that's what the auto-generated "In-App Purchases" list is there for.
> it's not displayed on the App Store description either.
Developers don't need to (and, imo, shouldn't) put pricing in the App Store description, because that's what the auto-generated "In-App Purchases" list is there for.
Agreed, you'd have to localize the description to support all currencies and then update whenever the price tiers or tax rates change. For the website: I just added the pricing in USD.
[deleted]
Sorry for the confusion. The app launched only yesterday. I just added the pricing details to the website. As another commenter pointed out, the tricky part is that the App Store adjusts prices for each country, but I will figure something out.
Congratulations - looks beautifully crafted. Sadly, MAS and subscriptions (as opposed to a one-time purchase with paid upgrades for major versions) make it a non-starter for me, especially given that it was made with "data longevity in mind".
I hear you. Trouble is, paid upgrades are tricky to implement in the MAS. About data longevity: if you cancel your subscription, you cannot add new notes, but you retain full access to all existing notes and all features remain active (you can edit existing notes, move stuff around, etc.). A knowledge base that locks you out once you cancel would be of no use...
I agree with this - I can only have so many subscriptions and unfortunately a notes up is not top priority even though it looks really nice.
Yup - was 100% excited and was going to buy it until I saw it's a subscription. Now 100% not excited and not gonna go there.
It just never works out for me to be worthwhile.
Sorry.
It just never works out for me to be worthwhile.
Sorry.
How much were you expecting to pay, out of curiosity?
$25 seems to be appropriate for this type of a program.
And if I ended up using it a lot, I'd hope for upgrades and would be happy to pay for them.
What I don't want is to bleed cash. That is a negative feature. Can't tell you how many programs I don't buy because of the SAAS model.
And if I ended up using it a lot, I'd hope for upgrades and would be happy to pay for them.
What I don't want is to bleed cash. That is a negative feature. Can't tell you how many programs I don't buy because of the SAAS model.
Totally understand. I was just curious. I bought Agenda and paid $25 for it, and then paid another $25 about 15 months later for another year of new features because I was using it so much, but I think I'd probably not have gone for $50 up front.
Totally. Much preferable model.
Same for me, i was interested until i saw it's subscription.
Great work! Love the effort you spent on making notes retrieval easy, all while keeping a beautiful and simple UX. Especially commendable for a solo dev.
Don't be overwhelmed by the negative comments on the pricing model. To be honest, I'd prefer a one-time purchase over subscriptions too, but the recurring pricing you've kept is modest and isn't a dealbreaker for me. And as someone else commented, the monthly subscription in a way gives a sense of safety that the app is going to be actively developed and maintained.
Also I like that you've decided to keep the app usable for all actions other than adding new notes if a user stops paying. I'd need that guarantee before I can commit to a new note-taking app and migrate all my notes.
I'd echo the request of introducing mobile apps for this as well. Preferably on both iOS and Android, as I find that while a lot of folks use Mac because of their work, a significant number of them use Android phones. Also, markdown imports would be great, if it's not already supported.
Don't be overwhelmed by the negative comments on the pricing model. To be honest, I'd prefer a one-time purchase over subscriptions too, but the recurring pricing you've kept is modest and isn't a dealbreaker for me. And as someone else commented, the monthly subscription in a way gives a sense of safety that the app is going to be actively developed and maintained.
Also I like that you've decided to keep the app usable for all actions other than adding new notes if a user stops paying. I'd need that guarantee before I can commit to a new note-taking app and migrate all my notes.
I'd echo the request of introducing mobile apps for this as well. Preferably on both iOS and Android, as I find that while a lot of folks use Mac because of their work, a significant number of them use Android phones. Also, markdown imports would be great, if it's not already supported.
Thanks for your feedback and encouragement!
I'm not taking this personal, I appreciate the feedback and I knew beforehand that subscriptions are controversial.
I contemplated the pricing model for a very long time going back and forth between the two options in my head multiple times.
In the end, the argument that convinced me what that with a subscription my focus is on adding features for my existing users. I'm constantly thinking "How can I make the app better for my users to keep my subscribers"?
Whereas for a single purchase I have to constantly think "What can I add to attract more users"?. All my other apps use one-time payments and sometimes it really pains me to put feature requests on my backpack knowing that I will never get to implement them, because they would not increase the visibility of the app.
Mobile: I have an iOS app planned, but it will take some time because I have a number of features that I want to add to the Mac app first (block based editor, smart search folders, larger calendar view).
I'm not taking this personal, I appreciate the feedback and I knew beforehand that subscriptions are controversial.
I contemplated the pricing model for a very long time going back and forth between the two options in my head multiple times.
In the end, the argument that convinced me what that with a subscription my focus is on adding features for my existing users. I'm constantly thinking "How can I make the app better for my users to keep my subscribers"?
Whereas for a single purchase I have to constantly think "What can I add to attract more users"?. All my other apps use one-time payments and sometimes it really pains me to put feature requests on my backpack knowing that I will never get to implement them, because they would not increase the visibility of the app.
Mobile: I have an iOS app planned, but it will take some time because I have a number of features that I want to add to the Mac app first (block based editor, smart search folders, larger calendar view).
Love the idea and, from the screenshots, the execution looks great. I've been looking for something like this and I'm still undecided, with Joplin and StandardNotes leading the pack for my use case.
It looks like you've settled on an App Store-only distribution model and a subscription-only pricing model. I'm curious about how you made that decision - subscription-only would suggest you're revenue-sensitive and want to provide continued updates, but App Store-only distribution means giving up revenues and putting someone else in control of updates. As a result, from the outside looking in, it seems a little incongruous. Just wondering :) obviously don't feel obligated to answer, either way it looks like a great piece of software.
It looks like you've settled on an App Store-only distribution model and a subscription-only pricing model. I'm curious about how you made that decision - subscription-only would suggest you're revenue-sensitive and want to provide continued updates, but App Store-only distribution means giving up revenues and putting someone else in control of updates. As a result, from the outside looking in, it seems a little incongruous. Just wondering :) obviously don't feel obligated to answer, either way it looks like a great piece of software.
Awesome, thanks for your feedback! Yes, I plan to provide continued updates. I have lots of more ideas (block based editor, large calendar view, smart search folders, …). I considered a one-time paid with paid upgrades model, but decided to use a subscription.
What would be your use case and is there something in particular that leaves you undecided between Joplin and StandardNotes?
What would be your use case and is there something in particular that leaves you undecided between Joplin and StandardNotes?
My dude, hear the words of wisdom and you shall be handsomely rewarded if you heed them.
You are not Adobe or Autodesk to pull off a subscription model. Not successfully.
Sell a perpetual license that is valid for the current version plus anything that is released in X months after that.
Then, sell an option to extend the access to upgrades for Y% of the original purchase price once X months are almost over. If X months are over, sell the same option with a mark-up.
This is universally perceived as a fair arrangement and it gives you a recurrent revenue from people who do keep on using your software (just like with the subscription). Best of both worlds.
You are not Adobe or Autodesk to pull off a subscription model. Not successfully.
Sell a perpetual license that is valid for the current version plus anything that is released in X months after that.
Then, sell an option to extend the access to upgrades for Y% of the original purchase price once X months are almost over. If X months are over, sell the same option with a mark-up.
This is universally perceived as a fair arrangement and it gives you a recurrent revenue from people who do keep on using your software (just like with the subscription). Best of both worlds.
Like others have mentioned, I'm not a fan of the subscription model either. After watching the demo video and reading through your site, I instantly went to download the app in the app store, only to be disappointed in, yet another subscription.
I'd gladly pay for the software and repurchase at major releases (if I wanted to upgrade)! I'm not looking for more subscriptions though. Give it a thought. I'd like to be one of the paying customers :-)
I'd gladly pay for the software and repurchase at major releases (if I wanted to upgrade)! I'm not looking for more subscriptions though. Give it a thought. I'd like to be one of the paying customers :-)
Thanks for your feedback! At what price would you consider the app for a one time purchase?
This probably sounds odd, but I'd be happy with the subscription's yearly price, or even a little more. It's not the price that bothers me, it's the subscription aspect to me.
The application is sold as, "with data longevity in mind", but the subscription model makes me feel like that is only the case while I pay for a subscription. From what I read in some of your other comments, that may not be the case, but it's still a worry. What if I can't access my notes/data in the future unless I have an active subscription?
The application is sold as, "with data longevity in mind", but the subscription model makes me feel like that is only the case while I pay for a subscription. From what I read in some of your other comments, that may not be the case, but it's still a worry. What if I can't access my notes/data in the future unless I have an active subscription?
Thanks again for your input! Yes, the app remains fully functional forever, with the limitation being that you cannot add new notes. Sounds like I need to make this more clear in the docs.
Not the commenter, but I’ve been in a similar struggle to find “thw perfect note app” since evernote went South. I’ve been trying Obsidian, Joplin, Bear, and Craft.
A must have for me is a code-block (three backticks enter or similar).
A killer feature would be a rest api so I could integrate with cli tools (bash, jq, grep, etc) without having to parse html.
I’m excited to try this out.
A must have for me is a code-block (three backticks enter or similar).
A killer feature would be a rest api so I could integrate with cli tools (bash, jq, grep, etc) without having to parse html.
I’m excited to try this out.
You say you've been struggling even though you've tried Obsidian. It has support for code blocks. I don't know about a rest API, but if you want to use CLI tools, the files are already stored in markdown format on your hard drive. I use CLI tools on my Obsidian files all the time.
[deleted]
I've been happy with FSNotes if someone is looking for a light markdown note taking app for Mac/iOS that syncs via iCloud.
This looks good if you are looking for something a bit more for school or something.
This looks good if you are looking for something a bit more for school or something.
I've used QOwnNotes which is open source and cross platform Windows/OSX/Linux, but sadly I don't think there's a mobile version...
Using HTML instead of Markdown gives some nice advantages if you want to use more than just text, so I am going to give this new app a try.
Using HTML instead of Markdown gives some nice advantages if you want to use more than just text, so I am going to give this new app a try.
A lot of markdown note apps including FSNotes (https://fsnot.es) support the TextBundle (http://textbundle.org) format so you can embed images in the same document.
HTML is nice for more advanced documents, but I prefer note taking in markdown as it's a simpler syntax, even when viewed in raw text.
I think HTML is perfect for this app because it's more for academic use and less personal use like grocery/todo lists, reminders, etc.
Having a synced mobile version is crucial as you want to access your notes on the go right? (at the grocery store, etc.)
HTML is nice for more advanced documents, but I prefer note taking in markdown as it's a simpler syntax, even when viewed in raw text.
I think HTML is perfect for this app because it's more for academic use and less personal use like grocery/todo lists, reminders, etc.
Having a synced mobile version is crucial as you want to access your notes on the go right? (at the grocery store, etc.)
I considered textbundle, but went for HTML for one reason: data accessibility. Imagine in 20 years from now you'd want to access your data and do not have the app around for some reason. You would need to find another app that supports the .textbundle format. Or you would need to manually rename all .textbundle notes to .zip to extract them. Even if a normal user would know about this, it would still be a pain. With HTML you can drag a note into a browser and see the contents. Links to other notes will work as well. Images will show right away, too. Pros and cons for each format...
Well that's one reason to not use a subscription based app. In the situation of a one time paid app a normal user would continue to use the same app, a power user would know it's a simple zip file. If you use a subscription based app you may not renew and you may be shit out of luck. A normal user may not even know what an HTML file is, much less how to edit it with a different program.
If you don't renew you can still use the app and open and edit all your existing notes. Good point, I need to make this more clear on the site. HTML vs. ZIP vs. power user: I'm going for the most common denominator, the average user with a browser :)
Yes, it is aimed more at academia and professionals who want/need to preserve knowledge in a structured way. Support for footnotes is planned.
I agree with the comments that a subscription model and delivery through the Apple's app store seem at odds with the 'with data longevity in mind' objective.
Requiring a subscription makes me ask what happens when you stop supporting the project? Relying on the App Store makes me wonder what happens when Apple decides to ban your developer account?
I'm not saying these are dealbreakers, but I'd like to have some sort of answer to these concerns.
Having a self-hosted way to download and pay for the app would increase my confidence level, even if I did decide to purchase through the app store. Similarly, there are 'subscription' apps that let the user keep using the latest version of the app if they cancel the subscription, they are just no longer able to get updates. You can also make a pledge to open-source the app if once you're no longer commercially supporting it.
Requiring a subscription makes me ask what happens when you stop supporting the project? Relying on the App Store makes me wonder what happens when Apple decides to ban your developer account?
I'm not saying these are dealbreakers, but I'd like to have some sort of answer to these concerns.
Having a self-hosted way to download and pay for the app would increase my confidence level, even if I did decide to purchase through the app store. Similarly, there are 'subscription' apps that let the user keep using the latest version of the app if they cancel the subscription, they are just no longer able to get updates. You can also make a pledge to open-source the app if once you're no longer commercially supporting it.
Yes, absolutely valid concerns and I've though about those.
When cancelling the subscription, all existing notes and all data remains fully accessible (read and write). It’s a knowledge base, after all. Projects with more than 50 notes will not support adding new notes, but all other features remain fully functional.
About the idea of keeping the latest version without updates: interesting, but tricky to implement in the App Store. You'd need a feature switch for everything. OS compatibility updates would still need to go through or the app would not survive in the App Store (typically this is what would get users to upgrade for apps distributed outside of the App Store).
Even if the app were to disappear, you could still access your notes with a browser and copy the data over to another app. Not as convenient as using text files, but the ability to embed images into the notes led me to go with HTML.
Happy to answer more questions!
When cancelling the subscription, all existing notes and all data remains fully accessible (read and write). It’s a knowledge base, after all. Projects with more than 50 notes will not support adding new notes, but all other features remain fully functional.
About the idea of keeping the latest version without updates: interesting, but tricky to implement in the App Store. You'd need a feature switch for everything. OS compatibility updates would still need to go through or the app would not survive in the App Store (typically this is what would get users to upgrade for apps distributed outside of the App Store).
Even if the app were to disappear, you could still access your notes with a browser and copy the data over to another app. Not as convenient as using text files, but the ability to embed images into the notes led me to go with HTML.
Happy to answer more questions!
It's hard to justify a $24/year longterm commitment when FSNotes App works just as well and is free.
As they say -
I am a simple man, I see a well-made installable desktop software, I upvote it. Even if it's just for Mac.
Well done, OP. Break a leg.
I have to withdraw my praise and the upvote. Subscriptions for installable apps are completely unacceptable.
I am a simple man, I see a well-made installable desktop software, I upvote it. Even if it's just for Mac.
Well done, OP. Break a leg.
-- Edit --
I have to withdraw my praise and the upvote. Subscriptions for installable apps are completely unacceptable.
Thank your for part 1 and I hear you for part 2 :)
I am currently a simpleton Notes.app user. It does the job enough for me.
I just downloaded this, tried it out. Fantastic work. The editor is excellent and behaves how I'd expect. I love the calendar right there. The app uses a small amount of memory/cpu.
What keeps me on Notes:
1. Subscription. I'd pay for a one time license. I'd pay for upgrades, but I'd want to own it.
2. It needs a mobile version with sync.
3. I don't see a way to switch into light mode.
I just downloaded this, tried it out. Fantastic work. The editor is excellent and behaves how I'd expect. I love the calendar right there. The app uses a small amount of memory/cpu.
What keeps me on Notes:
1. Subscription. I'd pay for a one time license. I'd pay for upgrades, but I'd want to own it.
2. It needs a mobile version with sync.
3. I don't see a way to switch into light mode.
> 1. Subscription. I'd pay for a one time license. I'd pay for upgrades, but I'd want to own it.
I'd love to have this, but as latchkey says for a one-time purchase. Ideally, the app would be open source and available for Mac as well as Linux, so one could add bespoke extensions. Note the reason I say "open source" is not because I would want it for free, but because open source means I will still be able to use it in 20 years on whatever platform will be mine then.
Wish list:
- plug-in for Emacs, Atom and Sublime.
- versioning support (Git integration)
I'd love to have this, but as latchkey says for a one-time purchase. Ideally, the app would be open source and available for Mac as well as Linux, so one could add bespoke extensions. Note the reason I say "open source" is not because I would want it for free, but because open source means I will still be able to use it in 20 years on whatever platform will be mine then.
Wish list:
- plug-in for Emacs, Atom and Sublime.
- versioning support (Git integration)
Thanks for your feedback!
1. If you cancel your subscription you cannot add new notes, but you can still access, edit, move, etc. your existing notes. All features remain active (and you get updates, important for OS upgrades).
2. iOS and iCloud Drive support are planned
3. It changes between light and dark mode automatically with the setting of macOS.
1. If you cancel your subscription you cannot add new notes, but you can still access, edit, move, etc. your existing notes. All features remain active (and you get updates, important for OS upgrades).
2. iOS and iCloud Drive support are planned
3. It changes between light and dark mode automatically with the setting of macOS.
1. No, thanks. That isn't a model I want to adopt. What happens when the single small developer stops working on it or decides to sell the app to someone else?
2. Great! It doesn't do me any good to keep a shopping list in my notes and not be able to edit it at the super market. =)
3. This needs to be a setting that the user can choose. I like my OS dark, but my notes editor light.
2. Great! It doesn't do me any good to keep a shopping list in my notes and not be able to edit it at the super market. =)
3. This needs to be a setting that the user can choose. I like my OS dark, but my notes editor light.
Congratulations on the launch! Downloaded and seems quite polished.
Recently found and use 30% of something called Obsidian so native UI and attachments are welcome.
I saw the option to view as Spreadsheet but wasn’t obvious how one was made? The concept of fields seems cool. Are there plans for data extraction/APIs?
Congrats again!
Recently found and use 30% of something called Obsidian so native UI and attachments are welcome.
I saw the option to view as Spreadsheet but wasn’t obvious how one was made? The concept of fields seems cool. Are there plans for data extraction/APIs?
Congrats again!
Thanks for your feedback! The spreadsheet view works in combination with metadata fields.
Let's say you have a number of notes for your contacts. You tag each note with #contact and add a few fields like "Name", "Department", "Diet".
Type #contact into the location bar to find all contacts and switch from there to the spreadsheet view.
You'll get a list of your contacts and you can quickly tell who is a vegetarian, for example. Great for planning a party (once in person meetings are a thing again).
Another neat thing:
Add a new note and add the tag #contact. The right sidebar will now suggest fields and headings that you used in other contact notes. This way you can use the same fields to keep your notes consistent.
Let's say you have a number of notes for your contacts. You tag each note with #contact and add a few fields like "Name", "Department", "Diet".
Type #contact into the location bar to find all contacts and switch from there to the spreadsheet view.
You'll get a list of your contacts and you can quickly tell who is a vegetarian, for example. Great for planning a party (once in person meetings are a thing again).
Another neat thing:
Add a new note and add the tag #contact. The right sidebar will now suggest fields and headings that you used in other contact notes. This way you can use the same fields to keep your notes consistent.
Really nice design; do you have a “rename field” action for editing all those metadatas across matching tags at once?
Not yet, but that's on my list. Same for headings. I'm still debating if I implement this as a separate "rename" feature or instead implement a project-wide search and replace.
This looks really awesome!
I always find myself looking for a mobile companion for these types of apps, though (it's what made me stop using Roam). Do you have any plans for a mobile app in the future? I assume the files could probably sync over iCloud as an optional feature.
I always find myself looking for a mobile companion for these types of apps, though (it's what made me stop using Roam). Do you have any plans for a mobile app in the future? I assume the files could probably sync over iCloud as an optional feature.
Thank you! Yes, I have plans for an iOS app, but want to add a few things to the Mac app before that. I have a block-based editor 70% ready and want to get that shipped before working on an iOS version. Syncing will work through iCloud Drive. Since the app already saves as plain files and folders there is not a lot of work needed there (mainly conflict handling).
This is surprisingly sophisticated and loaded with features for a 1.0, congratulations on the release! I totally know what it's like to work on a productivity app for a long time before it feels like it meets the minimum bar for release, serious props for making it over the line. The smart summaries feature in particular looks really interesting.
While I confess that I'd also like the option to purchase a 1.0 license and then pay to upgrade to 2.0 later, I fully recognize that the App Store makes that sort of arrangement extremely awkward and difficult to achieve, and think you priced it more than fairly anyways.
While I confess that I'd also like the option to purchase a 1.0 license and then pay to upgrade to 2.0 later, I fully recognize that the App Store makes that sort of arrangement extremely awkward and difficult to achieve, and think you priced it more than fairly anyways.
Thank you! Those last 10% always seem to take just as long as the first 90! Ask me one day about that typo that a friend discovered that showed in all marketing materials so that I had to redo all screenshots and the demo video.
Pricing: yes, agreed.
One Page Summaries: I have more ideas on that front. I'd like to add a way to "save" the summary config as kind of a "smart search" so that you could have them in the outline on the left or even embedded as a block inside a note.
Another idea is a kind of command line syntax for the location bar:
. / #meetingminutes / H2:Lessons Learned | View:OnePageSummary
This would find all notes tagged "meetingminutes" in the current note and below, pull all sections with level 2 headings "Lessons Learned" and show them as summary on one page.
Pricing: yes, agreed.
One Page Summaries: I have more ideas on that front. I'd like to add a way to "save" the summary config as kind of a "smart search" so that you could have them in the outline on the left or even embedded as a block inside a note.
Another idea is a kind of command line syntax for the location bar:
. / #meetingminutes / H2:Lessons Learned | View:OnePageSummary
This would find all notes tagged "meetingminutes" in the current note and below, pull all sections with level 2 headings "Lessons Learned" and show them as summary on one page.
Looks really cool. The introduction video was very informative, but on a kinda unrelated sidenote, the way the narrator talks reminds me of a 90s infomercial - the cube-swipe also has a pretty nostalgic vibe.
Thanks for your feedback! I was looking for a voice over that does not sound as polished as a radio ad. Sounds like I went a bit overboard with that :)
Simple curiosity, with no claim of good or bad. Why a Mac app in 2021 when that excludes such a large part of the market?
Mac desktop market is 1/10 of that of Windows. There are however multiple "buts". Windows users are more reluctant to pay for software. When they do, they want to pay less. They tend to have less regard for aestheics and well-crafted UI/UX, but those that do will be sold instantly on the app that have 'em.
Regrettably, the percentage of Windows users that do value build and design quality over the abundance of features and low pricing is, maybe, 10-20%. On the plus side, however, this acts as a natural filter and you end up with the userbase that really groks what you make and how you make it. This alone is a huge plus. "Those who like it, like it a lot."
Long story short, if you can take your well-made Mac app and port it to Windows, retaining the polish - do it. It's totally worth it, in all aspect of it. Just make sure it looks and feels native, and it's not an Electron ;)
Regrettably, the percentage of Windows users that do value build and design quality over the abundance of features and low pricing is, maybe, 10-20%. On the plus side, however, this acts as a natural filter and you end up with the userbase that really groks what you make and how you make it. This alone is a huge plus. "Those who like it, like it a lot."
Long story short, if you can take your well-made Mac app and port it to Windows, retaining the polish - do it. It's totally worth it, in all aspect of it. Just make sure it looks and feels native, and it's not an Electron ;)
I can confirm the first part from my own experience. I ported one of my other apps to Windows (native, had to learn C# and UWP). The Windows revenue unfortunately is way, way less than Mac/iOS.
Usually it's in reverse, but it depends on the nature of the app, how well it's made, and on how it is marketed and promoted. In general, if it's something useful, its Windows version will outsell the Mac one even at a lower price level.
I had similar thoughts. The app looks really good and interesting but mac-only is a non-starter for me as I can only use it on a small subset of my devices.
That being said, congrats to OP for launching. The execution seems to be great with attention to detail and focus on the right things.
That being said, congrats to OP for launching. The execution seems to be great with attention to detail and focus on the right things.
Thanks for the kind words! Re: attention to detail: nobody has discovered the easter eggs yet!
Well, I did a thorough marked analysis, weighted pros and cons and...
...no, I really just wanted a good notes app that had all the features I wished for. So I went ahead and got started (not done yet :). That was 3 years ago. 2 years ago I wrote an importer and transferred all my notes over from the app I was using at the time and have been using my own app ever since. And I plan to use this for the rest of my life to save the things I learn(ed) along the way. That's why the focus on data-longevity.
...no, I really just wanted a good notes app that had all the features I wished for. So I went ahead and got started (not done yet :). That was 3 years ago. 2 years ago I wrote an importer and transferred all my notes over from the app I was using at the time and have been using my own app ever since. And I plan to use this for the rest of my life to save the things I learn(ed) along the way. That's why the focus on data-longevity.
It's often easier to start out with focusing on making a really good product for a single platform first, and then branching out to other platforms. That even counts for things built with Electron, Qt, etc since even if 90% of the app is cross platform there's still a sizable surface between the app and each supported platform that needs to be tested and polished.
Yes, you've got to start somewhere, especially as solo-dev.
When it’s not Electron/Web: wHy nOt an eLEctRoN wEB aPp
When it’s Electron/Web: wHy nOt nATivE
When it’s iOS: wHy nOt aNDroId; 80% oF tHe wOrLd
When it’s Android: i pErSoNALly prEfeR iOS fOr tHe UX
Maybe I should take a break from HN
When it’s Electron/Web: wHy nOt nATivE
When it’s iOS: wHy nOt aNDroId; 80% oF tHe wOrLd
When it’s Android: i pErSoNALly prEfeR iOS fOr tHe UX
Maybe I should take a break from HN
A well-made UX in GTK or QT can look fairly native on Mac with little-to-no effort, and would let you also distribute it to Windows/Linux/Chromebook (the other 93% of the PC market, for those of you who aren't paying attention)
I love Mac apps, I like their silly use of euphemism and laissez-faire design language, but I will outright not integrate it into my lifestyle if I can't run it on my 5 other devices too. Getting work done comes first, and I'm sure as hell not going to boot up my QEMU container just to add a bullet point for my shopping list.
I love Mac apps, I like their silly use of euphemism and laissez-faire design language, but I will outright not integrate it into my lifestyle if I can't run it on my 5 other devices too. Getting work done comes first, and I'm sure as hell not going to boot up my QEMU container just to add a bullet point for my shopping list.
Oh, please, your reddit is leaking. Don't do it on HN.
I don't know, his comment was a pretty accurate representation of common responses of HN.
Though it's just the case of the loudest people voicing these complaints.
It doesn't represent everyone, but it certainly is prevalent and can be demoralizing hearing all the hate.
Though it's just the case of the loudest people voicing these complaints.
It doesn't represent everyone, but it certainly is prevalent and can be demoralizing hearing all the hate.
> Maybe I should take a break from HN
Wouldn't be a bad idea, since it seems to bother you that different people ask different questions, and none of your cases is related to my question. Unless you think "why are you intentionally limiting your market" is the same as the ones you've listed.
PS: I think your keyboard is broken.
Wouldn't be a bad idea, since it seems to bother you that different people ask different questions, and none of your cases is related to my question. Unless you think "why are you intentionally limiting your market" is the same as the ones you've listed.
PS: I think your keyboard is broken.
Did you build this in Swift UI?
Would you make different technology choices if you started today?
Would you make different technology choices if you started today?
No SwiftUI, just plain Swift and AppKit/Cocoa. I considered SwiftUI, but at the time it was not ready and was missing a few core things I needed, like an outline view (this was 3 years ago).
Sometimes I wonder if I should have gone for a Catalyst app like Craft, for example, but again, at the time when I started Catalyst was in a very early stage. Today I'd probably give it another try. I also considered a Swift wrapper around an HTML/JS core (kind of my own slim Electron version) but decided to go for a native Mac app.
Sometimes I wonder if I should have gone for a Catalyst app like Craft, for example, but again, at the time when I started Catalyst was in a very early stage. Today I'd probably give it another try. I also considered a Swift wrapper around an HTML/JS core (kind of my own slim Electron version) but decided to go for a native Mac app.
Congrats, looks great! I'm a huge fan of notes in general and I use a few different apps. I love the idea of quick linking and tags. Layout is polished.
I'll definitely have to try it out.
I'll definitely have to try it out.
Awesome! Let me know how the app works out for you. One pet peeve of mine is that many notes apps make it easy to enter notes, but when it comes to retrieving content all I'm left with is full text search.
I added two additional ways, the spreadsheet view and one page summaries. The summaries are shown towards the end of the demo video. If you take lots of notes, this might be useful for you to extract knowledge from your notes.
I added two additional ways, the spreadsheet view and one page summaries. The summaries are shown towards the end of the demo video. If you take lots of notes, this might be useful for you to extract knowledge from your notes.
Looks great. Are there similar applications for Linux? No remote capabilities and storing data in open format is a must. Preferably native app, not packaged web app.
Obsidian.md is my go to for notes. It also has tons of extensions which take it to the next level.
As the name suggests, all notes are stored as markdown files.
As the name suggests, all notes are stored as markdown files.
When data longevity is a goal, I would expect it to be open source, such that I have a chance to port it over to Linux or other OSs and also be able to port it to future OS in 50 years or so.
I'm also not sure whether HTML is such a great format. Maybe it's fine for reading the files and content in the future but for interop with other tools, I think sth like text or markdown would be better. Or Org-mode.
I'm also not sure whether HTML is such a great format. Maybe it's fine for reading the files and content in the future but for interop with other tools, I think sth like text or markdown would be better. Or Org-mode.
I'm still using Notational Velocity, talking about longevity...
Curious about your workflow since you've been keeping notes for a long time. How often do you refer to old notes and how old are those? What methods do you use to find them (e.g. search, navigate a folder structure, etc.)?
Oh boy, my system is old, didn't say it's good...
I'm not retaining ephemeral notes, no work logs or anything like that. That's on separate "systems", often text files within the projects or actual paper. This makes things a lot easier.
Notational Velocity is mostly search based. I mean, it's a list of messages, a text editing field and a searchbar, nothing more. So system-wide shortcut to pop it up, Cmd-L to search and there you go. I'm mostly doing a bit of "SEO", so intentionally write content in the node that makes it easier to find. Tried tags, but that just added another layer and "Here's another good Bash Shell tip for Linux Servers:" makes it both more readable and provides hooks for searching.
Synchronisation has change a few times, it's just text files after all.
I'm trying to check whether the Zettelkasten method would help me, so I've currently switched to Obsidian and might try some others. They're still writing text files, so I can backport them easily when/if I'm done with it. Right now, I'm not sure whether just having a GUID/timestamp is enough even within NV. Sure, I can't just click on it, but that means that I just have to Cmd-C/Cmd-L/Cmd-V after it.
And being quite fond of Emacs, I try and fail with Org-Mode once a year.
Notational Velocity is mostly search based. I mean, it's a list of messages, a text editing field and a searchbar, nothing more. So system-wide shortcut to pop it up, Cmd-L to search and there you go. I'm mostly doing a bit of "SEO", so intentionally write content in the node that makes it easier to find. Tried tags, but that just added another layer and "Here's another good Bash Shell tip for Linux Servers:" makes it both more readable and provides hooks for searching.
Synchronisation has change a few times, it's just text files after all.
I'm trying to check whether the Zettelkasten method would help me, so I've currently switched to Obsidian and might try some others. They're still writing text files, so I can backport them easily when/if I'm done with it. Right now, I'm not sure whether just having a GUID/timestamp is enough even within NV. Sure, I can't just click on it, but that means that I just have to Cmd-C/Cmd-L/Cmd-V after it.
And being quite fond of Emacs, I try and fail with Org-Mode once a year.
Great, thanks for sharing some details about your setup. I do something similar with my email messages. I never delete anything. Should I later need to recall a conversation I use Mail.app's full text search. Success varies depending on how much context I can recall.
With the app I tried to provide additional access points into the data. Page links are an additional way if you use them like "@ mentions". Let's say you have a person or topic that a note is related to (for an email this would be the sender). I created a folder "Contacts" and added a note for each person. Now if I write something down I mention the page for that person on the note. Later on I can go to that person's page and see all notes connected to that person (the power of backlinks) or simply search for "@james", for example.
Zettelkasten: I'm still trying to wrap my head around this one. What is great about it is that Niklas Luhmann figured out a way to have page links and backlinks between notes in a setup in the physical world on actual paper. With digital notes, I think GUIDs and timestamps to identify notes are not necessary anymore, because the file path (or URL if you will) uniquely identifies a note.
Org mode: yes, same here with the added difficulty that I have a vi background :)
With the app I tried to provide additional access points into the data. Page links are an additional way if you use them like "@ mentions". Let's say you have a person or topic that a note is related to (for an email this would be the sender). I created a folder "Contacts" and added a note for each person. Now if I write something down I mention the page for that person on the note. Later on I can go to that person's page and see all notes connected to that person (the power of backlinks) or simply search for "@james", for example.
Zettelkasten: I'm still trying to wrap my head around this one. What is great about it is that Niklas Luhmann figured out a way to have page links and backlinks between notes in a setup in the physical world on actual paper. With digital notes, I think GUIDs and timestamps to identify notes are not necessary anymore, because the file path (or URL if you will) uniquely identifies a note.
Org mode: yes, same here with the added difficulty that I have a vi background :)
Well, the problem with using file names/URLs for unique identifiers is that they might change. So either you don't do that or you need some piece of software to update this. With a note title (and thus file name) of "[2020091149] Conversation about Note Taking on HN", I can just reference the part within brackets, and it also gives me the timestamp if the file metadata ever gets lost in sync.
But yeah, I don't have that many cross references now, this is one part where I'm looking for better solutions that don't depend on too much technology. Thus my Zettelkasten research. Probably will implement a lot of this with scripts and shortcuts (I'm quite fond of tools like Textexpander/atext for this).
But yeah, I don't have that many cross references now, this is one part where I'm looking for better solutions that don't depend on too much technology. Thus my Zettelkasten research. Probably will implement a lot of this with scripts and shortcuts (I'm quite fond of tools like Textexpander/atext for this).
Yes, I thought about both scenarios and actually added support for both to my app.
If you rename a note through the app it will go though all other notes and update them to use the new name.
The app also adds datestamps, YYYY-DD-MM, to the file name of each note exactly for the reason you mentioned. File metadata might get lost when copying a file around. The added benefit is that if you sort files alphabetically in Finder, they show up in the order you created them.
If you rename a note through the app it will go though all other notes and update them to use the new name.
The app also adds datestamps, YYYY-DD-MM, to the file name of each note exactly for the reason you mentioned. File metadata might get lost when copying a file around. The added benefit is that if you sort files alphabetically in Finder, they show up in the order you created them.
I spent the past 3 years working on a personal notes app that focuses on data longevity. Everything is saved as simple files and folders. In fact, you can open any folder as notebook. External documents/files/PDFs can live alongside notes (the app shows a preview).
Files are saved as HTML to ensure that even in 20 years form now you can still access your notes with a browser even if the app should not be around.
Tags, bi-directional links, rich text, images are supported. I also added a few neat features to extract knowledge from notes like a spreadsheet view and one page summaries.
For example, let’s say you keep monthly project review notes, each with a section “Lessons Learned”. You can generate a page with all “Lessons Learned” sections from all notes tagged #postmortem to see them all on a single page.
I’m very happy that the app finally went live. Many of you will know that the last 20% of actually getting a project out of the door seem to take just as much work as the first 80% (hat tip to Vilfredo).
Looking forward to your feedback!