Thought Delimited

When I created my first Android app, NoteToSelf, I had always intended to release a "deluxe" version with additional features.  Even though this app is essentially that deluxe version, I felt it needed a new name to reflect its most notable new feature (reminder alarms).

So this incarnation of the app comes with the following features:

• It allows you to dictate your reminder instead of typing it via Google's speech transcription service. All you need to dictate your reminder is a network connection (celluar or WiFi) and no concerns about talking to your phone in public.

• It gives you the choice between three different home screen widgets that let you cycle through all of your reminders and add or edit reminders via the widget.

• It lets you schedule an alarm for those reminders that are time-sensitive. You can use the settings in the app to determine how the alarms should notify you (by default, the alarm will cause the phone to vibrate and the notification light to blink).

You can read more about the app and view several screenshots at the following URL:

http://www.thoughtdelimited.org/android/myreminders/

Now...I did decide to charge $1 for this app in the Android Market, because I did put a lot of work into it and I think it's certainly worth that much given the functionality it provides.  However, if you're a contributing member of the ColdFusion/CFML programming community (someone who regularly shares their knowledge or their code to help others) and you have an Android phone that allows you to install non-Market applications, send me an e-mail and I'll send you the install file so you can have the app for free.

I haven't been blogging much lately, but that's partly because I was on vacation for a week and partly because I was working on this:

http://www.thoughtdelimited.org/android/notetoself/

It's a fairly simple app built with the standard Android API, but it meets MY need for a note/reminder list that is right there on my Android home screen and lets me see all of my reminders without having to go into the application. And being able to dictate my reminder (I put in the dedicated dictation button because my Swype keyboard doesn't have a key for dictation like the stock Android keyboard does) makes it easy to add a quick note if you can tolerate a mistranslation here or there.

This version is free, so if you have an Android device running 2.1 or higher, feel free to check it out.

So yesterday, during the first half of the morning keynote at the Google I/O conference, Google made several announcements about the latest version of the Android OS:  version 2.2, codenamed "Froyo."  Here are several links to pages that go through the announcements:

http://android-developers.blogspot.com/2010/05/android-22-and-developers-goodies.html

http://www.dzone.com/links/r/android_22_and_beyond.html

http://www.blog.droidweb.com/2010/05/android-2-2-annoucned-at-google-io-what-it-means-for-you/

A couple of additional notes:

• One of the announcements was that you could initiate actions on your phone via the "the cloud" (the Internet). In the demo, the presenter's assistant was able to get driving directions on his laptop using the Chrome browser and then send those directions to his Android phone by clicking on a certain link. The presenter said that browser initiated an "intent" on the Android device.

  In Android development, an Intent is a messaging object directed at a component (an Activity, a Service, or a Broadcast Receiver) within an Android application and delivers data to the component. Normally, an Intent can either be explicitly addressed to a specific component by name, or it can be implicitly targeted towards any component whose intent filters make them capable of receiving the intent. I'm curious to see how Google will implement this feature to make sure this capability isn't used maliciously.

• Another announcement was that Android 2.2 would allow developers and users to install applications on the SD card in the Android phone rather than in the phone's internal memory, something that many Android users have wanted for a long time.  The Android Developer site already has a documentation page up regarding this feature, which I glanced over.

  When they write an application using the API for Android 2.2 (apps written to an earlier API will NOT be movable to the SD card using the features in Android 2.2), developers can specify one of the following install locations within their application's manifest file:

  • "preferExternal": the app will initially be installed to the SD card automatically unless the SD card is full. The user will have the option to move it to internal storage if they like.

  • "auto": Android will determine the best location for the initial installation for the app, but again the user has the option of moving it.

  • "internalOnly": the app can only be installed in the internal memory of the device.

  The drawback to running an application from the SD card is that all application processes currently active on the SD card are killed whenever the user connects their Android device to their computer and chooses to mount the SD card as an external USB drive. Applications that use certain features can break when this situation occurs, and therefore such applications may have the "internalOnly" install setting in place to prevent problems.

  The documentation also points out that applications installed to the SD card will still store any private user data and databases for the application in the internal memory. So the need for a way to back up the application data was still needed even with the SD installation option, hence the announced feature in 2.2 that application data could be backed up to the cloud.

My last few Android development posts have been kind of long (took long to write anyway), so here's a short one...

Read more...

In my last post, I talked briefly about how the R.java file, a resource file located in the "gen" folder of your Android application project that is automatically generated and updated by Eclipse and serves as a resource map. My example code demonstrated how you could reference layout.xml files via the R.java file and how Eclipse would register the id of the UI objects within the R.java file as well.

I also mentioned that the layout XML files for your Android app are located in a "layout" folder within the "res" ("resources") folder.  There are other folders under the "res" folder as well, and the content within those folders is also registered with the R file, allowing you to access those resources within your Android code.

Read more...