Lately, I’ve been exploring some new ideas on how to attract new users and maybe also developers. There are many people out there that prefer using a web-based calendar, which is fine, but I believe they can find added value by storing their data locally.
Surfing the web, you probably make a lot of contact with calendar related websites. The most obvious is a web-based calendar like Google or Yahoo Calendar. But there is actually a lot more. Have you ever used a short-term scheduling service like doodle.de or tungle.me ? Or to go one step further, you’ve surely visited a site that contains a massive amount of calendar data, for example local event sites like eventful.com or upcoming.yahoo.com.
So what happens when you visit a scheduling site? You’ve probably been invited to participate by a friend. So you look at the site to see what times are suggested. Then you switch back to your calendar to see if you have time. Then you switch back to the site and after a few clicks you have set up your availability. But then you forgot to check for the next week. You see whats going on here? You are switching back and forwards, wasting a lot of time. If you could allow the site to access your calendar, you could see all the data in one place, no need for switching to your calendar application or website. The same goes for upcoming events. If you’re looking for a nice concert to go to, it would be swell to know if you are free on those days.
This post is the start of a series, I will be posting more about this topic soon. Next up I will be writing in more detail about the possible consumers of your calendar data. Please stay tuned, you are welcome to leave your feedback and ideas.