Even before the spike of Gingerbread, Android has captured the attention of enthusiastic developers. That’s why last March 12, 2016 at KLab Cyscorpions BGC, DevelopersConnect launched a one day Android code camp for thirty hankering students.
Preceding the dev hours, Ed Salinas introduced everyone to the volunteer org’s lifework. Afterwards, Rei Flores, a software engineer at Everest Consulting brought up Beta Realm. It is a community interaction web service that allows app developers to take responses from testers worldwide. As registered testers of the web service, you will be privileged to download, take assessment, and report bugs of the site’s featured apps. Testers can earn points and then convert them into cash. Nice and easy.
All the way from Pangasinan, Jamie Rose Aguinaldo stepped up to start handling the day’s objective . She is a web and mobile application developer from Pixelhub Creative. Starting with a quick introduction to Android with a few slides, the audience were asked to open up their gadgets and prepare to be caught up with application development using the Android Studio. Jamie Rose has explained some tips. She pointed out to keep in mind the target OS version with the most users for the app you are trying to build.
Time for coding. Step one, know your activity. Whether its a login system, a fullscreen wide narrative, a game, whatever. But, for starters, a blank one would be a good icebreaker. An activity represents a single screen much like a window or a java frame. Choosing a template can help you with the basics of what you are trying to accomplish.
There are several layouts to choose from for your interface. An understanding of layouts concept can help you figure the ease and toils of your UI. A layout defines the virtual structure for an interface. You have FrameLayout, LinearLayout, RelativeLayout, Table, and Grid. The mostly used are linear and relative. For declaring sizes, use dpx. That is density pixels. Although five other units are accepted, this is the most recommended.
The basic when it comes to applying actions, is the onClickListener. A button’s action that leads to another. It’s when you want your components to react when users click on ’em. Jamie also pointed out the value of naming conventions. She favors a descriptive name for variables.
After the first few line of codes, the students were asked to run their script with an emulator. Successfully, they were able to show the button Jamie demonstrated for them to do.
Finally, the brainstorming began. Everyone was asked to make an application and present it at the end of the day. As the minutes turned to hours, all laptops appeared with so many lines we ought to think they’re on serious business. Lunch passed, and afternoon snack, too. A few has been able to develop a complete functioning app. Those remaining got stuck with development. Even so, Jamie was thankful that the students were able to get ahold of the three most important steps she thought them. Setting up the activity, the layout, and the action listeners.
Still and all, the students had a wonderful time learning something new. It was indeed a great experience for them. A definitely superb day of Android application development.