151–160 of 255 posts
* Material design
* Apple-like design
* Dropbox-like design
Even when I goto Dribble, its the same thing, different colors.
And the worse thign is, even when I am designing something. I conform to that norm!
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. 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, automatica…
> I've spent the last two years developing a todo app 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…
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.
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. 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, automatica…
It's too late to edit my original comment, but I've set up a temporary website, where I explain this app in more detail, and show some (temporary and very messy) screenshots and designs: http://tuskarr.tilda.ws/
Earlier quoted context omitted.
> I went full waterfall on it, the spec is 266 pages long and took half a year just to write. 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 t…
IMO your biggest competition is probably just whatever comes installed on the phone.
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. 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, automatica…
> I went full waterfall on it, the spec is 266 pages long and took half a year just to write. 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 t…
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.
Sparrow, Sunrise, Wunderlist... all the good apps just get bought and killed.
The question I ask is, were all those apps just created to be bought? In other words, were they 'startups' always aimed at some kind of buy-out or IPO or whatever? If so, I have to question that whole model (shock, horror). After all, it's one thing to expect everything to get cannibalized into, well, Microsoft I guess, and consider that an ideal world. It's quite another to get used to the idea that all good things…
This is normal, why would you be shocked by it? Consider going for open source apps only that supports open standards. That is not full proof and not always convenient but it's a good way to avoid some of thse shocks and horrors.
Sparrow, Sunrise, Wunderlist... all the good apps just get bought and killed.
Can you blame the developers, though? These acquisitions are life changing. I mean, heck, if someone offered me crazy money for an app, yes please!
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. 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, automatica…
> I went full waterfall on it, the spec is 266 pages long and took half a year just to write. 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 ?
(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.
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. 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, automatica…
It's too late to edit my original comment, but I've set up a temporary website, where I explain this app in more detail, and show some (temporary and very messy) screenshots and designs: http://tuskarr.tilda.ws/
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. 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, automatica…
> the spec is 266 pages long and took half a year just to write How many times did you make paper/cardboard mockups and user-test the interactions?