Publishing an Android application, is at the same time quite easy and quick, and also quite a pain if you don't know what to do. However, once you know the procedure, it take less than 1h to package the application, sign it, and publish it. There are also a few rules to respect if you don't want to bang your head on the table for hours.
The full procedure can be found here.
Wednesday, May 25 2011
How to sign and publish an application on the Android market
By Hadrien Pierart on Wednesday, May 25 2011, 13:52
Tuesday, April 12 2011
How to use the ADB (Android Debug Bridge) to communicate with the emulator or phone
By Hadrien Pierart on Tuesday, April 12 2011, 11:58
The ADB is a tool that permits to communicate with the emulator(s) or device(s) on which you are developping. This client-server program is most useful for all developping steps of an application. If you want to read the full documentation, you can look here, otherwise, you will find the most important or useful stuff in the following post.
Wednesday, March 30 2011
How to develop and debug on an Android phone instead of the emulator
By Hadrien Pierart on Wednesday, March 30 2011, 11:55
First of all, for the full documentation about this topic, you can look at the google documentation. As you maybe know from our previous tutorials, developping on the emulator is sometimes quite a pain because really slow. So using an actual phone to test your application, before publishing it, is a mandatory requirement if you don't do it, you will most probably get nasty crashes and force close on your first users, and this is not good at all for your developer image.
Tuesday, March 15 2011
Droid Contact 019 – Notify the user 03 : Notifications, a persistent way to inform the user
By Hadrien Pierart on Tuesday, March 15 2011, 14:02
The notifications are another way to notify the user, however, their use is different from what we saw so far. Indeed, this kind is persistent in the way that when you publish it, it appears not in the on the screen of your application but in the bar at the top of the screen. It stays there for a while and then vanishes. However, it stays in the list of notifications as long as it is not wiped.
Wednesday, March 2 2011
Other kind of dialogs : AlertDialog, ProgressDialog
By Hadrien Pierart on Wednesday, March 2 2011, 17:34
As we saw in the previous article, dialogs are quite useful to keep the user informed. There are a few more classes derived from the Dialog class that we can use directly from the SDK. we will see here their basic implementation. However, I won't insert any of this in our main application.
Thursday, February 17 2011
Droid Contact 018 – Notify the user 02 : Dialogs, inform and interact with the user
By Hadrien Pierart on Thursday, February 17 2011, 18:11
Dialogs are another way to notify the user. Although it can display as much as the Toast, it goes with different rules. We will see in this post how to use this class and subclasses, and how it can be very useful in an application. We will create a custom dialog from the Dialog class, and in the next post, we will see what already existing dialog you have at hand from the SDK.
Wednesday, February 2 2011
Droid Contact 017 – Use of Theme . Styles to customize your application : customize the title bar
By Hadrien Pierart on Wednesday, February 2 2011, 15:16
One of the HUGE feature on Android is the control you can have over almost EVERY feature of the display. Everything is ruled by styles and themes, and as the rest of display features, you can override those defined as default and put what you like instead. This topic will be the beginning of a turn in the design of many application. We will see the example of the title bar, and in the further topics, we will apply that to everything we can. The important thing to remember is that a style/theme is a unified pack of references to resources that will define a display. The Google documentation is quite detailled about that.
Thursday, January 20 2011
Droid Contact 016 – Notify the user 01 : Toasts, quick way to inform the user
By Hadrien Pierart on Thursday, January 20 2011, 11:14
Notifying the user is of the highest importance. Indeed, if you want him to know important things happening in the application, then you have to display him some alerts. The easiest way is to create a Toast, but you won't have as much options of customization as with the AlertDialog. Lets see how to do this.
Tuesday, January 4 2011
Droid Contact 015 – AsyncTask : How to execute background task, multithreading and responsiveness of an application
By Hadrien Pierart on Tuesday, January 4 2011, 11:50
You have certainly noticed or realised that there are many task that can require more than a few hundreds of ms to be execute, especially on a phone. Remember that you are not working on a computer. And you don't want your application to be laggy and the user will be bored very quickly. Most of the time, if an application is slow, you tend to either shut it down and do something else. Even more, if it does that all the time, you'll just not bother anymore, uninstall it and problem solved. If you have a smartphone, I think you understand me very easily. So, the good news is that in Android, things were done so that you can (easily) make your users happy.
Tuesday, December 21 2010
Droid Contact 014 – Menus 02 : Context menus
By Hadrien Pierart on Tuesday, December 21 2010, 17:44
This is the second kind of menu. The implementation of the menu is almost the same as the OptionMenu, exept that the OptionMenu is an Activity specific menu, which means that you can only have one Option Menu per Activity (even if you can alter it based on events on your Activity). In the case of the Context Menu, it is a View specific menu, which means that you can have (theoretically) as many Context Menu as views in your layout. This can obviously become a bit crazy if you start putting menus on every view. However, this is the theory. The other difference is that this menu can't be called as the option menu is as you can have several ones on the same screen. Therefore, you call it (usually, but you can change that) by doing a long click on the view. One last hudge difference is that icons ARE NOT supported by context menu.
« previous entries - page 1 of 4