Android SMS Popup - Part Three: The Activity

in part one , we captured sms messages using a broadcastreceiver. in part two , among a set of options, we chose to pass the needed sms information (sender, message and timestamp) as a serializable 'popmessage' object from the background to the foreground. in this section, we will construct the screen to show to our users.

what do we want?  three things basically:

1. get the sms information from the background
2. show that information to the user in a popup window
3. allow the user to react to that message within the application, either by dismissing it, or by responding to it by using his/her phone's favorite sms program a button click away.

by now, you must have read the android developer guide section on activities . so let's start coding our popsmsactivity class which will provide our ui. for now, that class will be our only and main activity, declared in our android manifest:

<application ...>

     <activity  android:label="@string/app_name"
                android:name=".popsmsactivity" ...>
                  <intent-filter >
                     <action android:name="android.intent.action.main" />
                     <category android:name="android.intent.category.launcher" />
                  </intent-filter>
     </activity>
     ....
</application>

we declare a single activity, the popsmsactivity , as the main entry point to our little application. for our development purposes, we can launch our application anytime and see how the popup looks like, without having to wait for an sms to arrive. for the ui, there are several kinds of layout to choose from, and that is a lot of xml. what we need right now is something as simple as possible, so we will program dynamically an android alert dialog.

when we will start building more features, we will have to use a more sophisticated layout ui and replace the main launcher by a settings screen where we would do all kinds of customization, like choosing colors, sound effects,  having a popup only for specific 'vip' phone numbers etc... and even have a "preview" button to see how our popup window will look like before use, instead of launching the dialog directly as we will do now. but for now, here's the activity class:

 public class popsmsactivity extends activity {

    /** called when the activity is first created. */
    @override
    public void oncreate(bundle savedinstancestate) {
        super.oncreate(savedinstancestate);
        // no need for xml layouts right now
        // we will use a dialog instead
        //setcontentview(r.layout.main); 

        // retrieve serializable sms message object
        // by the key "msg" used to pass it
        intent in = this.getintent();
        popmessage msg = (popmessage) in.getserializableextra("msg");

        // case where we launch the app to test the ui
        // i.e. no incoming sms
        if(msg == null){
                 msg = new popmessage();
		 con.setphone("0123456789");
		 msg.settimestamp( system.currenttimemillis() );
		 msg.setbody(" this is a test sms message!");
        }
        showdialog(msg);
    }

the showdialog() method creates a very basic ui, i.e. a typical android dialog with a text and two buttons:

      /***/
    private void showdialog(popmessage msg){

    	final string sender = msg.getphone();
    	final string body = msg.getbody();

    	final string display = sender + "\n"
                + msg.getshortdate( msg.gettimestamp() )+ "\n"
                + body + "\n";

        // display in alert dialog
    	alertdialog.builder builder = new alertdialog.builder(this);
    	builder.setmessage(display)
    	.setcancelable(false)
    	.setpositivebutton("reply", new dialoginterface.onclicklistener() {
    		public void onclick(dialoginterface dialog, int id) {
                      // reply by calling sms program
    		      smsreply(sender, body);
    		}
    	})
    	.setnegativebutton("close", new dialoginterface.onclicklistener() {
    		public void onclick(dialoginterface dialog, int id) {
                      // go back to the phone home screen
    	              gohome();
    		}
    	});
    	alertdialog alert = builder.create();
    	alert.show();
    }

this is how it looks like on the phone's screen:

what is left in order to have a very basic working application, is handling those two button clicks, and talk a bit about implicit intents . in part four.

source: tony's blog .