android development beginners guide

A while back I decided to make an Android app, and take the world by storm and make millions and be carried off by the townspeople. And I decided to document the process for any newcomers trying to do the same. Alot goes into making a mobile app, and it is very different than making a web application or a windows application. And no, I did not make millions, nor can I show you how, that is up to you. But I can show you how to set up your IDE, create a menu, spit back output, and save user data. And if those sound like things that you would want to learn then read on.

. . .
Continue reading
beginning android development part 7 - file saving

File Saving

In the previous post we learned how to save data to the SharedPreferences files in Android, which is great for small bits of data. But things are seldom that simple. Sometimes we need to save larger bits of data, or images, or spreadsheets, or any of a hundred other file types. This is when we dive into good old fashion file saving. Android provides us with the File API in order to work with the native Android file system. A File object is suited to reading or writing large amounts of data in start-to-finish order without skipping around. Android has two types of storage means, Internal and External. . . .

Continue reading
beginning android development part 6 - saving data

It's hard nowadays to find a website or Windows application that doesn't make use of a database in some way. Android apps are no exception. Android offers several ways to store user data, or application data each with it's own pros and cons and use scenarios. You can store small bits of data into key/value pairs into a SharedPreferences file, or files. You can store your data into files, great for larger amounts of data or images. And lastly you can use a database, if you require organized data that needs to queryable. This isn't the most exciting topic, but again, the basics will help save time when the real work starts.

. . .
Continue reading
beginning android development part 5 (fragments)

User Controls, Modules, Fragments, call them what you will but they all do the same job. Reusable snippets of code with their own state and properties that can be inserted in your projects where it is needed. Good code separation leads to more maintainable projects and less clutter to sort through when there is a problem. Android provides us with the Fragment class in order to get the job done. Fragments can be dynamically added and removed at runtime depending on the current layout. We see this frequently with email apps on tablets that show the email selected on the 2nd panel and the listing on the first when flipped to landscape mode.

beginning android development part 4 (life cycle)
android activity life cycle

Every Android app goes through a series of steps in order to get where it's going in a user friendly fashion. Normally, you get a splash screen, followed by a home page, then maybe you take a trip to the settings page before you hit start and begin your awesome gaming journey. Because each page you see on an Android app is an Activity of some type, in the diagram above we see the steps that each Activity takes from its creation to its inevitable destruction.

Android, unlike many other programming frameworks which bei . . .

Continue reading
beginning android development part 3 (action bar)

The action bar that is. A very important part of almost any Android application, the Action Bar lives at the top of most applications and it makes the most related and important tasks visible. It also allows any other app actions that you may have real estate within the action overflow area. By default the Action Bar displays the name of the current Activity and the app's icon next to it. And if we're on any Activity but the home Activity, it also gives us an Up button to get back to the parent.

beginning android development part 2 - controls

So Day 2 of Android development is about to commence. I went through the SDK installation and AVD creation in the previous post, and this time around we're looking to get some controls onto our android pages, or Activities, if you will. A basic Android app layout consists of a hierarchy of ViewGroup and View objects. View's would be the buttons and text fields that we see when we load an app, and the ViewGroup would represent containers for said controls. And as you can see, ViewGroup's can contain Views and other ViewGroup's as well.

beginning android development part 1 (sdk, adt and avd)

I've recently decided to begin my adventures in Android development after years and years of doodling down ideas that I thought would make awesome apps. Developing for the same platform day in and day out gets to be very tedious at times So before I give on software development and become an Alaskan fisherman I'll take a dive into making phone apps. I'm brand new to Android development. I've never touched it or read up on it, so this is a first hands on look at the process from installing the SDK to configuring the emulator to getting those first strings of "Hello World" to appear on the screen. I'll be writing this as I myself progress, so let's see what develops.

Download the . . .
Continue reading

lg g watch unboxing and review
lg g watch

Smartwatches like the Pebble and Continue reading

Score in the top 10 and leave your Instagram handle.
snake left
snake up
snake down
snake right