Without seeing what you have, a general remark would be that everyone and his cousin has clocked at least some time developing at least one ToDo app. It's a right-of-passage thing for a lot of developers, just like a Weather app is the same for UX designer wannabies.
BTW, what set Wunderlist apart is not the features first and foremost, but their bold in-your-face marketing rooted in very pretty visuals and a fake arrogance routine. Whether they had proper hierarchies / first-class subtasks was quite secondary.
I'm absolutely aware of the rite-of-passage thing, but I'm doing this because I NEED a proper, working todo app. My life will crumble without it. And I'm prepared spend my time and money on it. In any case, there's no going back to Wunderlist now.
As for marketing, I'm not worried. All I want is a working todo app, and it will be great if it turns out to be useful for other people.
Never liked there UX though, but the concept.
My 2 cents - "Tuskarr supports first-class subtasks" might be a fine description on HN, but an average user won't know what that implies
(Which reminds me that I should be doing the screenshots now.)
This sounds awesome, I'm looking forward to testing!
A nice wood texture (not even joking, was totally sold on the visuals in the early days)
20 year UX veteran, this is the first I've heard of this (o; Not a criticism, certainly made me smile, but I've not heard or seen this before.
(that said, I work mostly in enterprise, this might just be a mobile thing)
UX primarily starts with user research, then a metric shiton of postit notes, paper prototypes, a bit of testing and then some hi fidelity mockups
Its funny, because it true. :D
right of passage is probably more like the right of way :)
https://books.google.com/ngrams/graph?content=rite+of+passag...
As Wikipedia says, "[rite of passage] is the Anglicisation of rite de passage, a French term innovated by the ethnographer Arnold van Gennep in his work Les rites de passage."
"Right of passage" may mean something similar to "right of way", and may be used my mistake when people mean "rite of passage" but there was never a switch in how "rite" is spelled.
Compare:
Wow. It's nice to see extensive planning like that. I usually just throw anything that seems like an important idea into a text file on the assumption that it'll be fully hashed out during production at a later time. That method entails far less work, with the caveat of occasionally wondering if you're delusional from time to time.
In any case, good luck. I hope you kick ass. If Microsoft employs their usual design aesthetic, doing so should be very possible.
The app combines four intersecting concepts:
1. Infinite timeline with addressable days. 2. Recurring tasks that support this infinite timeline. 3. First-class subtasks, which have all properties of normal tasks. 4. Contexts, which hide tasks from the list based on certain conditions.
I simply couldn't create a working mental model that accounts for all possible interplay of these concepts without speccing it out in advance.
How many times did you make paper/cardboard mockups and user-test the interactions?
If you have this and an iOS version, then you have my money.
But I definitely think that there should be a legal way of protecting existing users of an app from "Our Incredible Journey". Maybe some clause that permits the authors to open-source the app.
Are there any examples of this in the industry?
Of course, the buyer may just ask you to remove that clause prior the acquisition.
Android essentially represents only a subset of phones and tablets. An app like yours is useless to many people unless it has desktop equivalents, as mobile-only access heavily restricts a user's ability to be productive where and when they need it. I might be an edge case, but I use Windows, OS X, an iPhone, and an Android tablet. Your app could be the most functional and usable todo app out there, but a competing product with 10% of your features is going to wind up being my choice simply because I get to use it across all my workflows. Platform support beats out the quality of the app, every time.
Based on your screenshots, the app is wonderful. I simply suspect you have focused too much on launching a 100% complete product instead of starting with an MVP. Obsessing over having a perfect product that launches too late to market, while your competition launches early and takes your cake, is all too common a scenario.
(Under "the concept" I mostly mean the approach where all non-snoozed or dateless tasks are shown in Today, and you swipe away the tasks that are not yet "ripe" to be done -- whereas in traditional apps you do the reverse - you select tasks to do by starring them during a review).
Now that I found out that the concept clearly works well at least for one user (me), the next step would be to validate the concept on a wider group of users. An Android-only soft-launch, or even a closed beta should be enough for that.
And if the concept is valid, we'll definitely develop for other platforms, the ones you mentioned. iOS and Android clients will be native, and the desktop apps (Windows and macOS) will probably use some cross-platform technology.
And thank you for the kind words :)
When you get around to desktop clients, ignore the seemingly negative consensus regarding Electron[1] if you think it's the right fit for you. All the negativity I've read about it is from "purists" who aren't specifically singling out Electron; rather they are hating on all non-native implementations. I noticed the mention of Xamarin on your site; never heard of it, but I'd be weary as they seem to be oriented more towards mobile whereas you're looking for a cross-platform desktop solution which is where Electron shines.
If your goal were to be the gold standard for apps, you should be developing using native OS X APIs; the performance you get from a native implementation on OS X is astounding. However, if you do native OS X you're putting yourself in a position to do native Windows and possibly Linux apps, and the collective work required for native-everywhere obviously does not come easy or cheap - particularly if you are doing this as a solo project without assistance from a team.
Electron is a perfectly fine balance for most UIs that are fairly simplistic, which is going to be true even for the most advanced todo-type app. Extra bonus being that if you put in the effort to plan out the Electron app side-by-side with your web/browser-based app, you can share the frontend development between the two, resulting in less overall work.
I won't do that :) I stopped working on the spec the moment I handed it down to coders, and my total time spent on the spec since then is around one week. When the spec is written well, and you simulated all important situations in your head before encountering them in the wild, you actually don't need much extra time.
There's almost no tinkering happens on the app right now. I'm fixing critical bugs and smoothing out rough details that manifested after months of my dogfooding.
Regarding the desktop solutions: yes, going native would be perfect, but that is not feasible for a 4-man team. We'll go with Electron or Xamarin or, less likely, Qt - we haven't decided on the exact technology yet.
[For heavy-duty use and project planning, I use org-mode. But there's still no really satisfactory mobile org-mode story.]
Currently I use OmniFocus, primarily due to the start dates which hide things until they're relevant, which so many apps (including Wunderlist) lacked. Sadly the Android support is poor and only covered by 3rd party clients that lag massively behind in functionality.
Why would you write a ~9k “loc” long spec over 6 month instead of coding it directly ? The only reason I can think of, is if you want to out-source the development. Is there any good reason to work this way on a one-man project ?
(before the obvious objection: exceptions are toy programs which you write to find out how to build something, in which you focus on the technical aspects. The technical aspects ('how does it work') don't matter for the end user (= your potential customer), they only care about 'what does it do'.)
Most colleagues of mine and a few managers see them as a waste of time ("you're over thinking this", or "we'll figure it out later") yet somehow the projects with a specification always end up being done more or less on schedule.
The thing about specifications is that you need to be open to changing them if you find it's not working out. Specifications are not synonymous with waterfall development, and it's harmful to treat and view them as such.
Planning is important, and cautiously thinking about your features before diving in can save you weeks later on. But spending 6 month in a tunnel, writing specs you'll spend at least a year to implement, is a huge risk : what if your users only use 30% of the features you designed, and lack a missing feature you didn't plan ? You could have figured it out way sooner have you built something earlier and released it.
Also, your time to market is way slower and you don't risk losing years of work by missing a deadline …
> Damn, now I need to move faster. My app must be ready by the time they close Wunderlist. I expected an eventual closure, but not that soon.
Or worse, what if different segments of users only use 30% of different feature sets? See also: Evernote's 5% problem [1]
[1] https://venturebeat.com/2016/01/05/evernotes-5-problem-offer...
Yeah but that's not necessarily in man-years. Maybe he worked on it an hour or two a day. Now we're talking around two man-weeks of planning.
(Not the OP.) At least for me, emphatically yes.
From your question, it sounds like you're only considering the communicative value of a spec. That's of course important, but I consider it secondary.
Writing a good spec forces you to think through what you're developing in an orthogonal way. You're thinking through flow, cohesiveness, design, some implementation, UI, etc. together at a high level.
I love having the time to write a spec when I'm building something nontrivial. I've found numerous problems that I wouldn't have otherwise by doing so, ranging from simple UI problems/contradictions to spotting unconsidered assumptions that would have lead me down dead ends.
A spec and the application should naturally co-evolve during development to some extent. But the spec also provides an anchor for what you're doing, as well as a map. It is very, very helpful if you Do It Right(tm), no matter the size of your team.
(OP here). This. A thousand times this.
- Shut down Wunderlist
Now let's hope they procrastinate just like everyone else.
Something else that was critical is that I could use Cortana to add tasks to lists while driving or without typing on the keyboard.
I think when I want to go deeper in organizing tasks, todo apps are often bad for that simply because a document format tends to do better once you're in the thick. It's better if those things are stored, tracked and organized with the work itself most of the time and todo apps tend to be outside that context.
If you had released it earlier you might have been able to get some traction right about now when people are forced to leave wunderlist.
You want to move faster, then release the app. Customer feedback positive and negative will get you making changes quick smart and you'll get a good sense of initial demand. App development is a continuous process that requires constant input from users. No point in adding features no one asked for, you're just wasting your time.
As a wise man once said 'It's better to have released and failed than to never have released at all'.
Basically I don't give a shit about a walled garden to do app anymore no matter how good it is. I don't want a new app. I'd rather use something that puts my existing apps on steroids.
And somewhere in several years it'll grow big.
And Microsoft or Apple will buy it.
And someone will need to move faster to release his to-do, which is much better, of course.
I use WP8 day to day but dabble in Android, I'd love to give your app a spin...
What are the checks and balances if any to keep the astroturfing binge to a minimum and encourage discussions instead of traffic channeling bait.
I've spent the last two years developing a todo app that would be a good replacement for Wunderlist (and Astrid, if anyone still remembers that).
The app will include with some major / critical features both those apps lacked: proper hierarchies / first-class subtasks, automatically-activated contexts (e.g. location), snooze for arbitrary durations, a robust implementation of recurring tasks, and an infinite calendar-like timeline to look ahead.
I went full waterfall on it, the spec is 266 pages long and took half a year just to write. I'm currently testing an Android alpha version, and, for me, it works ridiculously well, much better than Wunderlist, which sat on my homescreen since August 2013.