This is one of the faster founding-fitting-exiting stories I've seen in some time. Five years is quick!
Dropbox Acquires Reclaim.ai
11–20 of 26 posts
Re: Dropbox Acquires Reclaim.ai
#12Waiting for someone to say they could implement reclaim with a 10 line shell script and rsync.
Several years ago, facing the problem that Reclaim.ai started off solving (cross-calendar sync), I started exploring Google's Calendar API and MS's O365 API for the same. Pretty quickly figured out this wasn't side project-sized and dropped it, so I've been happy to give Reclaim my money in the years past!
Re: Dropbox Acquires Reclaim.ai
#13cofounder here -- happy to answer any questions :)
So how much your net worth increase? How well did your employees exit?
Re: Dropbox Acquires Reclaim.ai
#14cofounder here -- happy to answer any questions :)
Out of Dropbox's long history of acquisitions, very few of the products from said acquisitions have survived. Did this factor into your decision to join Dropbox and if so how did you weigh that risk?
Reminded me of their Command-E acquisition from a few years ago (https://blog.dropbox.com/topics/company/welcome-command-e-to...)
Re: Dropbox Acquires Reclaim.ai
#15Waiting for someone to say they could implement reclaim with a 10 line shell script and rsync.
DanG's thoughts on the comment/'meme' you're referring to: https://news.ycombinator.com/item?id=23229275 https://news.ycombinator.com/item?id=27068148 https://news.ycombinator.com/item?id=29178442 It seems he's given up fighting it in recent years, but I doubt his view or the facts have changed, and they're worth reading.
Dang writes:
> about Dropbox's YC application (which is what the word "app" meant back then)
But Drew Houston himself writes in the reply "most apps are written as if the disk was local". So the word "app" could definitely mean a program running on your computer as well.
Re: Dropbox Acquires Reclaim.ai
#16I don’t see this as a good thing. HelloSign was acquired by DropBox and is basically a stagnant has-been, and their security incident doesn’t give me confidence that acquisitions are in good hands there either given the lack of a transparent root cause analysis.
Re: Dropbox Acquires Reclaim.ai
#17Waiting for someone to say they could implement reclaim with a 10 line shell script and rsync.
Several years ago, facing the problem that Reclaim.ai started off solving (cross-calendar sync), I started exploring Google's Calendar API and MS's O365 API for the same. Pretty quickly figured out this wasn't side project-sized and dropped it, so I've been happy to give Reclaim my money in the years past!
Seriously! I've tried a few times off and on and it just isn't something to tackle without having a ton of time and effort and stamina and stubbornness. And then still likely failing.
Re: Dropbox Acquires Reclaim.ai
#18cofounder here -- happy to answer any questions :)
Out of Dropbox's long history of acquisitions, very few of the products from said acquisitions have survived. Did this factor into your decision to join Dropbox and if so how did you weigh that risk?
We definitely considered it and we talked openly with the Dropbox team as well. I feel very good about the future of Reclaim.
Re: Dropbox Acquires Reclaim.ai
#19Earlier quoted context omitted.
Out of Dropbox's long history of acquisitions, very few of the products from said acquisitions have survived. Did this factor into your decision to join Dropbox and if so how did you weigh that risk?
Reminded me of their Command-E acquisition from a few years ago ( https://blog.dropbox.com/topics/company/welcome-command-e-to... )
Command-E lives on: https://www.dash.ai
Re: Dropbox Acquires Reclaim.ai
#20Waiting for someone to say they could implement reclaim with a 10 line shell script and rsync.
Several years ago, facing the problem that Reclaim.ai started off solving (cross-calendar sync), I started exploring Google's Calendar API and MS's O365 API for the same. Pretty quickly figured out this wasn't side project-sized and dropped it, so I've been happy to give Reclaim my money in the years past!
A few weeks ago I got the chance to check out the Google Calendar API for the first time and was very impressed how thorough it is.
- Very easy to retrieve incremental changes to events on a calendar
- Webhooks to be notified when calendars are created, updated, or removed
- Webhooks to be notified when events are added, updated, or removed on a calendar
- Bulk requests
- Select only the fields you need from the event
- Querying events in a calendar with custom properties (I use this so I don’t need to store anything on my side)
Funnily enough to build a sync between my personal calendar and work calendar, and for my wife and I to have a combined calendar for our own personal commitments. I also feed in a few calendars I subscribe to for sporting events to our shared calendar. $100 a year was a bit much for a feature that should be in Google Calendar already. I named it Don’t Double Book Me, felt appropriate.
I only started exploring the Google Calendar API recently after realizing that Reclaim’s policy allows Enterprise customers to take over other individual paying accounts associated with the Enterprise, effectively making it not really my Reclaim account anymore. Didn’t help I wasn’t notified of this either.