Author Archives: Aaron

Writing iPhone Apps using Java

[Update 7/27/16: The Cronote Reminders iPhone app is no longer available but may return in the future.]

The Cronote Reminders iPhone App was released ahead of schedule last Friday (a post about this is forthcoming). The app itself differs from conventional iPhone app development in that 98% of the code is Java. We used the Google Web Toolkit (GWT) in conjunction with the PhoneGap library to develop the app. GWT compiles Java source code into highly efficient and compact JavaScript webapps, while PhoneGap wraps the generated webapp into a deployable form in Xcode. Our model has been discussed at length on other sites such as:

http://blog.daniel-kurka.de/2012/02/mgwt-and-phonegap-talk-at-webmontag-in.html

http://turbomanage.wordpress.com/2010/09/24/gwt-phonegap-native-mobile-apps-quickly/

Some would ask why such a model is necessary. The simple – and powerful – answer is that we use the same Java POJOs for our REST API, our reminder-timing program, our website and our iPhone app. The website and iPhone app share the same code that calls the REST API.

Cronote REST

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.

Aaron

Website Redesign

A lot of the structure for the main Cronote site came from Joshua Porter’s book, Designing for the Social Web. His work highlights the importance of a user’s initial experience. He points out that being able to try a service without a commitment assures potential users of the quality and reliably of the service. We agreed with this assessment, and added the ability to send an anonymous cronote right from our main site.

Of course, we’re concerned about robots (aka spam bots) scheduling cronotes. We’re taking measures to block spammers, as well as developing a “do not cronote” list for users who do not wish to receive anonymous cronotes (or cronotes at all).