The Cronote System is coming along well, and while we have our core timing logic down, there are several areas where we’d like to improve.
None the least of these is a central REST API for registration, logins, and, of course, cronote scheduling! While working on the iPhone App, it was clear that having separate gateways for the website and mobile apps made maintenance a huge issue.
REST stands for Representational State Transfer, and it basically means that all devices can communicate with cronote using the same protocol that is used for web pages (HTTP). Many other social media sites (like Twitter) use a REST interface to provide developers access to their system.
Our grand vision is to allow anyone to use our API to perform timed tasks, even beyond text messaging. It’s a lofty ambition, but it’s why we’re so excited to be working on cronote in the first place.