List of required Android skills - a follow up

So it has been a month since I first blogged about the skills I thought I needed to consider myself a decent Android programmer. 
So here is the list reposted along with updates of how I am doing along with some new additions.


Build arbitrarly complex layouts 
- this is a bit vague. I can certainly build more complex layouts now than I could a month ago, but I would not say that I find this stuff easy yet. Probably just need more practice. 


Services Bound service and a started service
- have done both of these since the original post. A tricky subject, but I think I have it down as well as I need it for now.


Broadcast receivers Create own (with custom broadcast) and Respond to a system one
- Both of these are done. Have written a few broadcast receivers of my own and have an app in the market which responds to the rebooted broadcast from Android.


Database
- This has always been a strongpoint for me. Nothing more required really. 

Shared preferences
- Done.

Intents Create an intent filter
-Not done yet. I need to get on top of this - its a key component of the Android system.

Content providers
-Not yet, but the reason is that none of the apps I have developed have leant themselves to this. I reckon it if  I don't know what this is I will never know where to use it, so time to take the leap with this.

Threads Use Thread class
Use Async Class
- Both done.

Performance management Use of traceview
- Have tried this out, but not used it in anger. 

Action bar Use the action bar (on emulator only maybe)
- Not yet, but I don't have a tablet yet either :( Reckon I will leave this were it is for the moment.

Compatibility library Get understanding of all functionality in this
-Not done.

Notifications Status bar and Toast
-Done.

ListView
- Although this is a complex beast I reckon I know enough to do whatever I want without making any performance killer mistakes.


Custom Compenents Demonstrate familiarity with all methods of doing this
Come up with a useful one and publish it
- I have done some work on custom components and am happy that I can build them when needed. A fairly advanced topic, but I reckon I am up to it at this stage :)

Styles and themes How to make own
How to inherit from or just use the platform ones
-I am fine with these for now. 

Dialogs Ability to create all types
- Fine

Animation
- Done. A nice library even if it is a bit limited before property animation.

Manifest Understand all tags
- Reckon I have enough of this for now.

Media Playing music and video
- Done

Maps
- Yep

Widgets
- Not yet. Current app may present an opportunity to do this. 

Search
- Looked into this, but my apps so far have not had anything to search for! An important feature in many apps, so I should get to this at some stage before a client asks me...


Testing
- Need to get a better handle on this. I think when I first approached this it was reliant on too many aspects of the platform that I did not know about. This should not be the case now. Another swing needed I think.


Tools
- Mostly done, but a quick check that they have not added anything sneaky in the last month or so.

Webapps
- I use html web pages for all of my help files. Works well and I don't think there is anything else in this for me at the moment.


New stuff which I have added since last month:


Use of the canvas to draw graphics directly on screen.


Analytics
- Done


Ads
- Done


Creating attractive images with vector tools.
- I have done a lot of work on this, but have a long way to go. Tons of practice required I reckon.


Localization
- Done

Comments

Post a Comment

Popular posts from this blog

Building a choropleth map for Irish agricultural data

I wanted to create a choropleth map  using Irish data. The Irish Government has made a large quantity of data available at data.gov.ie. The set I chose was for Bovine TB across Ireland over a number of years. You can get geojson for a variety of countries and Ireland's county boundaries are available. All I had to do was get the data labels to match. In the data some counties are split into 2 parts. I merged and summed these data points to get the choropleth to work with normal county boundaries. You can see the results here . A link to the github is included at the top of the notebook.
Read more

Early Stopping with Keras

Steps to train a model There are a number of things you have to do when working on a Machine Learning problem. Import your data and transform it as appropriate Define  your model using something like Keras - this includes your chosen hyperparameter values Run the training phase Evaluate the model If at the end of this process the evaluation shows that your model is not sufficient for your needs you will need to make some changes and rerun the training.  Ideally you should have a way to spot that training is not going as you want and stop it. This is one of the uses of early stopping. The other is if your model has reached a sufficient quality standard for you to use and further improvements have slowed, stopped altogether or an unnecessary.  Early Stopping Keras provides a way of doing this using the EarlyStopping callback . There are a range of callbacks in Keras and you can define your own. Details are here . The EarlyStopping callback works by choosing a metric
Read more

AutoCompleteTextView backed with data from SQLite in Android

Image
This is a handy piece of code. As your database gets bigger you can allow the user to pick the correct value by typing. If the db gets very big, you can always increase the threshold, so that the query does not run until there will be a suitably sized resultset returned. Running it at a threshold of 1 is fine for very small resultsets.  Here is the code you need to back your AutoCompleteTextView with a cursor adapter. @Override protected void onResume() { super.onResume(); text = (AutoCompleteTextView) findViewById(R.id.autoCompleteTextView1); final AdapterHelper h = new AdapterHelper(this); Cursor c = h.getAllResults(); startManagingCursor(c); String[] from = new String[] { "val" }; int[] to = new int[] { android.R.id.text1 }; CursorAdapter adapter = new MyCursorAdapter(this, android.R.layout.simple_dropdown_item_1line, c, from, to); adapter.setFilterQueryProvider(new FilterQueryProvider() { public Cursor runQuery(Cha
Read more