101–110 of 255 posts
Does anyone know an app that can do this? Todoist is very close -- you can write "task xyz in 2 hours" but for some reason cannot use "minutes".
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…
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.
It's not really killed. The original Sunrise, Accompli and Wunderlist teams still work at MSFT and they're working on their new apps respectively (Javier runs all of Outlook now). And Chad Fowler (former CTO of Wunderlist), and company are behind the pivot to To-Do. It's the exact same application. I've been beta testing it and it just has few additional features that will show up over time. It's really just a rebran…
“This, milord, is my family's axe. We have owned it for almost nine hundred years, see. Of course, sometimes it needed a new blade. And sometimes it has required a new handle, new designs on the metalwork, a little refreshing of the ornamentation . . . but is this not the nine hundred-year-old axe of my family? And because it has changed gently over time, it is still a pretty good axe, y'know. Pretty good.” That's wh…
I wonder why they didn't just rebrand Wunderlist like they did Accompli (into mobile Outlook).
It's pretty much a replica of the original app. It's being developed by the same team that made Wunderlist as in Chad Fowler and company (he has a larger portfolio now). Most of these comments are probably unnecessary. The original team still works at MSFT The app is simply a rebrand that's trying to add additional features over time. https://www.linkedin.com/in/fowlerchad/
Sparrow, Sunrise, Wunderlist... all the good apps just get bought and killed.
It's not really killed. The original Sunrise, Accompli and Wunderlist teams still work at MSFT and they're working on their new apps respectively. Chad works on Wunderlist. Javier still runs outlook. They just absorbed a bunch of other apps too
Earlier quoted context omitted.
> 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 OP, but once you have a spec, it's much easier to code up. If you're designing while you're coding, you have to switch all the time between 'how should this work' and 'how do I build this'. Thinking and writing down how something should work, should always be the first step - regardless of whether you're on your own or in a big team. (before the obvious objection: exceptions are toy programs which you write to fi…
Earlier quoted context omitted.
It's not really killed. The original Sunrise, Accompli and Wunderlist teams still work at MSFT and they're working on their new apps respectively. Chad works on Wunderlist. Javier still runs outlook. They just absorbed a bunch of other apps too
It doesn't matter where the team is now, the Outlook Calendar is not Sunrise nor To-Do is Wunderlist. I get what you say but the apps are gone (or soon to be in this case) and for the people that used those apps that is killing them.
Earlier quoted context omitted.
It was a hard lesson to learn, but "Weeks of programming can save you hours of planning" holds true in almost all cases.
I totally agree with this statement, but here we're talking about 0.5 year of planning ! 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 ? Yo…
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...
Earlier quoted context omitted.
I mustn't be the only who thinks it's ironic to move to a Google product/service in hope of avoiding something disappearing. ;)
Ha yeah I know what you mean. I am still angry about Reader. For now at least it seems Google is putting work into Keep so I hope it won't disappear anytime soon. Unfortunately having a todo/notes app that allows for account controlled sharing is tricky to do without some kind of service. Unless you want to get all ghetto and build something that works on top of something like Dropbox but that gets problematic as Dro…
I think that's said about every Google thing at some point in time.