Sunrise
Sunrise was a cross-platform calendar app for people who wanted one polished calendar across providers and devices.
View original storyProduct snapshot
What it was
Sunrise connected multiple calendar providers and services into a polished cross-platform calendar experience.
Who it was for
Problem / value
Give users one better interface for viewing and managing upcoming events across devices.
Core workflow
- combine calendars from multiple providers
- view and manage upcoming events
- use a more polished calendar interface than bundled defaults
Product form
Pricing model
Microsoft said Sunrise would remain free after acquisition; no standalone paid model is disclosed in the sources used.
What happened
Summary
Sunrise gained major adoption and was acquired by Microsoft, then shut down after the team moved its calendar work into Outlook.
Outcome
Sunrise shut down as a standalone app; public sources do not disclose standalone revenue, paid conversion, retention, or acquisition economics.
Demand signal
Sunrise had millions of downloads and strong product love, but public sources show it remained free, was acquired, and later shut down into Microsoft’s Outlook roadmap.
Distribution issue
Calendar apps compete with bundled defaults from Apple, Google, and Microsoft, so downloads and praise do not prove standalone pricing power.
Timeline
- Failory lists Sunrise as started in 2012.
- Microsoft announced the Sunrise acquisition on February 11, 2015.
- The Sunrise team announced the app would be removed from stores and shut down on August 31, 2016.
Before you build
Why it matters
Users may love a replacement for calendar, email, notes, or files while still expecting the core job to be free or bundled.
Primary check
Validate paid urgency before building a default-app replacement where users already have free bundled alternatives.
Checklist
- Test willingness to pay before polishing broad consumer UX.
- Map free bundled alternatives and incumbent roadmap risk.
- Separate product love from paid urgency.
- Find a narrow workflow where the default tool has a costly gap.
Relevant if
- You are building a calendar, email, notes, task, or file-client replacement.
- Your product competes with free bundled defaults.
- Your main advantage is polish, integrations, or interface speed.
- Acquisition seems easier to imagine than a paid standalone business.
Less relevant if
- You solve a specific paid business workflow inside the calendar category.
- You already have strong paid retention in a narrow segment.
If you build this today
Pick one paid calendar workflow, such as team coordination or revenue-critical scheduling, and prove retention and willingness to pay before optimizing general calendar polish.