![]() I think I mentioned this once before, but I'd be happy if The Archive offered a subscription option - even something as simple as CAN $5 or $10 or $15 per year. Too many developers following the approach described above at some point lose interest and stop improving their app. I actually favour the subscription approach as it provides greater stability/certainty for the software developer. Usually the cycle from X to X+1 is about 2 years, so this is no different than a subscription approach charging Y/2 per year. I use other software that I feel provides great value, that is sold using the model of: a) buy version X for $Y and get all upgrades to version X, until version X+1 comes out b) buy version X+1 (usually at a reduced price for current users) - repeat for as long as you find the app useful. That's the first time I have taken that step with an app. Not only is the app amazing but the developer is super-responsive to questions and actively improving NotePlan. I felt so strongly about NotePlan that I switched over from using it through SetApp to using it via a "normal" subscription at CAN $80 per year (no, I am not brainwashed in any way). I also believe in supporting software developers that have amazing products. Things and Bear are two of those, and they were both replaced by NotePlan. I have subscribed to a few apps on that basis, but most I dropped at the end of the subscription period because I wasn't using them enough and/or I found alternates. I don't mind subscription if the app provides value, I use it frequently and I feel the cost is reasonable. I already have a subscription to SetApp and already use about a dozen of the apps available through it, so there was no extra cost to load and thoroughly test drive NotePlan. But I gave it a longer trial by accessing it through SetApp. You can "try out" NotePlan to see what is like for free. )Īs much as I liked Things (I used it for about 3 years), I felt there was too much friction compared to benefit. (Sadly, I am highly allergic to subscription. Rather, I differentiate by length when assigning tags: short (20min) audio-visual inputs, because I build both differently into my workday. I don't listen to anything on the side while on the road. ![]() I do both on my computer, because I only listen to both at home with access to my computer. I sit down at my computer in both cases and take notes as I watch and listen.įor me personally, it doesn't even make a difference whether I'm listening to a podcast or watching a video. It is completely irrelevant to me at the action level. ![]() I have started to distinguish whether an audio-visual input is an interview or a lecture. The #tags should be instructive for the nature of the task. But if I prepare some difficult research object or prepare something over a long time, I like the infinite nesting of TaskPaper.īut it seems that TaskPaper will be my long-term storage for all of my research work and Things is more for the immediate and normal tasks (like watering the plants) It is: Areas, Projects, Tasks, Checklists. More difficult for me is that Things doesn't seem to allow very deep nesting. This is my (little) issue with things, too. Things3 is very "click-heavy" unless you learn the relevant keyboard shortcuts.Īh, thanks.
0 Comments
Leave a Reply. |