Skip to main content

Getting back into Android development

After learning both iOS and Android development about 18 months ago we've not really had many enhancements needed in our mobile applications, with any changes just needing our existing knowledge. In reality this has probably meant my knowledge has actually decayed; which is a shame given the challenge of intially learning mobile development we went through. To try and remedy this; as a side project I'm looking to rebuild our existing application from scratch with an updated UI. Our current application is built using Eclipse and has a standardised screen for all format which only works in portrait mode. So as part of this work I want to "improve" the UI so it makes use of the additional real estate of larger screens and landscape mode. I also want to see how Android studio works to see if it is worth porting the application across and making that our standard Android IDE.

It's always fun starting out with a new, empty project. Typically you do hope that everything will just work, which wasn't the case this time around. Opening the new project displayed 3 errors; the first two were that the project requires Java 7 to be installed and that it should be compiled against JDK7. As I already had Java 8 installed; I did a quick dig around (a Google search) and found the following Stack Overflow article. So updated the path and that resolved the first errors. The next error occurred when trying to view the activity; which failed with an error "java.lang.NoClassDefFoundError:$styleable". Again looking online I found this Stack Overflow article which solved the problem, for some reason the view wouldn't render when set to be the most recent API; backing it down sorted out the problems.

So now the project compiles and deploys to my device, let the fun begin.


Popular posts from this blog

Why do my Android Notification only appear in the status bar?

I'm definitely getting back into Android development, I'm remembering that feeling of 'Surely this should be easier than this!'. All I wanted to do was to schedule a local notification which behaved similar to a push notification pop-up. That is, as well as showing the small icon in the status bar I wanted it to pop up on screen to notify the end user. All seems fairly easily, I found this code for how to schedule a notification. That all worked perfectly, apart from the notification would only appear in the status bar. Searching around I found loads of different answers / solutions, mostly all saying the same thing:It only worked if you used 'NotificationCompat.Builder' in place of 'Notification.Builder', orYou had to set the priority to 'NotificationCompat.PRIORITY_HIGH'As usually happens, none of these solutions worked for me until I added in the missing piece of the jigsaw:- '.setDefaults(Notification.DEFAULT_ALL)'. For me this…

IPhone hangs when running from XCode

I've had this happen a couple of times now and the first time was a little worrying that I'd bricked my iPhone. Basically I was running an application on my phone via XCode and when rebuilding an updated version it failed with a "busy" error message. Stopping XCode and unconnecting my phone had no effect, the phone was stuck displaying the loading screen of the application and wouldn't respond to any key commands. To fix you have to hard reboot, holding the power and home button until the phone reboots - doesn't lose any of the data you have on your phone (a concern the first time I did it).

Do "Task Hours" add anything in Scrum (Agile)?

What do task hours add to the overall process in scrum?This was a question that has arisen from all team members in both instances that I've helped teams switch over to scrum. The benefits of artifacts like the comparative story point estimation, the 2 week sprints, stand-ups and the end of sprint demo have been self evident to the team, but as one I think every team member has expressed dismay when it comes to task planning and estimating each task in hours. Left unchecked there is a natural tendency for people to actually begin to dread the start of each sprint purely due to the task planning session.In my current role we've been lucky to investigate this further as a team.The team sat down to discuss the problems it was experiencing with estimating tasks in hours and the following common themes appeared:It is hard: Maybe it shouldn't be, but time estimation is hard! Story points are comparative and abstracted making them easier to determine, but time estimate is gen…