Android App Development - A Simple Unit Converter Application
Everything you need to know to get your hands dirty to design and develop your first native Android app
After working for so many years, i must admit that developing native Android App is not easy. And it is even more difficult for the newbies. They not only have to know about programming concept, but at the same time they must be fully aware of the Android OS architecture.. For example, they must know how they should handle the situation when the screen rotates from landscape to portrait view or the vice versa. Similarly they must know how to handle different screen sizes of Android phones. Keeping all these things in mind i have developed this training course so that the newbies can get enough confidence to get their hands dirty to develop their first native Android app. In this series of lectures, the students not only know about how to develop a simple Unit Converter app, but also how to apply the concept of design pattern to design the App. However, this training course assumes that the students are already familiar with Android Studio, they have developed a simple helloworld application and they are a bit familiar with Android Layouts and such basic things of Android. So again welcome and i hope you will enjoy this training course....
The source code of the Sales Tax problem which has been used to explain the Strategy Design Pattern used in the App can be cloned from https://github.com/sommukhopadhyay/salestaxinjava
The source code of the actual Unit Converter app can be cloned from https://github.com/sommukhopadhyay/UnitConverter
Your Instructor
The best way I can describe myself is as a dream chaser. In the beginning of my career, being in the marketing department of a big telecom company, which hardly added any values to my curiosity, I was hell-bent to jump into the software because that was the only way to know about the nitty-gritty of the hardcore technical aspects. Hence I started with learning C++/VC++. But in the beginning it was really difficult without much idea about programming. Moreover, there was no Google. I took a little more time to pick up. There was no training. Absolutely no help from anybody. No broadband internet. No computer at home. It was really difficult for me. But I did not stop dreaming. I used to dream and tell my colleagues that C++ is not as much about programming as about designing. It is more about a technique for moving from the problem domain to the solution domain. However, I hardly got any supports from the organizations where I worked. It was only when I got a PC at home, I started walking towards my goal. The early morning rise, innumerable visits to technical book stores in Bangalore, googling and traversing from one link to another in search for technical and C++ contents, becoming tired after the office hours, all were part of it. But still the road was difficult. I was not able to join the dots. And then, when I started going through the GoF's Design Pattern book, the actual joy of learning began. Still I remember how I used to go through the MFC source code to map different GoF patterns in Doc-View architecture, the command-routing architecture and so forth. However, I was not much aware of the Open Source communities. Then when Google made their Android framework open, it was a boon for me. I picked up many unknown areas and started looking into code from a designer’s perspective. When i started understanding the Android framework code, I thought I was really able to join the dots.The dots between the dream and the reality to become an able software engineer...