That's on separate "systems", often text files within the projects or actual paper. I'm not retaining ephemeral notes, no work logs or anything like that. Oh boy, my system is old, didn't say it's good. 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). ![]() 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. Whereas for a single purchase I have to constantly think "What can I add to attract more users"?. I'm constantly thinking "How can I make the app better for my users to keep my subscribers"? In the end, the argument that convinced me what that with a subscription my focus is on adding features for my existing users. I contemplated the pricing model for a very long time going back and forth between the two options in my head multiple times. I'm not taking this personal, I appreciate the feedback and I knew beforehand that subscriptions are controversial. Thanks for your feedback and encouragement! Also, markdown imports would be great, if it's not already supported. 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. I'd echo the request of introducing mobile apps for this as well. I'd need that guarantee before I can commit to a new note-taking app and migrate all my notes. 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.Īlso I like that you've decided to keep the app usable for all actions other than adding new notes if a user stops paying. 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. ![]() Especially commendable for a solo dev.ĭon't be overwhelmed by the negative comments on the pricing model. Great work! Love the effort you spent on making notes retrieval easy, all while keeping a beautiful and simple UX. 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). I’m very happy that the app finally went live. ![]() You can generate a page with all “Lessons Learned” sections from all notes tagged #postmortem to see them all on a single page. I also added a few neat features to extract knowledge from notes like a spreadsheet view and one page summaries.įor example, let’s say you keep monthly project review notes, each with a section “Lessons Learned”. Tags, bi-directional links, rich text, images are supported. External documents/files/PDFs can live alongside notes (the app shows a preview).įiles 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. ![]() In fact, you can open any folder as notebook. Everything is saved as simple files and folders. I spent the past 3 years working on a personal notes app that focuses on data longevity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |