FHU Mobile for Android (Starting the Process)

by Lance Williams
September 27, 2011 5:00 PM

Recently I have begun the development of FHU Mobile for Android. At first it seemed rather daunting, and while there is a definite difference in building web applications and native application, Google has given developers all the tools they need to build responsive, powerful applications that take advantage of the mobile state of an Android device. 

After consulting the Android documentation, I was able to figure out just how to get everything up and running. The Android uses Java, so as far as I know, any Java-based IDE will work to develop Android apps. The developer's guide suggests using Eclipse, so that's what I went with. In the past I have used both Eclipse and Netbeans as development environments, but I must say I feel most at home with Visual Studio. First let me say that in my humble opinion, when it comes to IDEs, Visual Studio is second to none. Microsoft has developed a very intuitive (Microsoft?) powerful program that almost makes me feel as if it teaches me to code as a code. In the little time I have had with Eclipse I must say that it does offer most of the "perks" of Visual Studio, such as good error checking and an intelligent auto-correct, however it isn't as fluid as VS. Eclipse runs slow on my machine, whereas Visual Studio is rather snappy, even on my 2008 Macbook (Windows 7). Visual Studio's Intellisense shines even more after using Eclipse, in which its auto-prediction is rather slow and not that smart. 

As mentioned earlier Android apps are written in Java which is particularly awesome because it allows you to use most any of the large number of java libraries floating around on the internet. With that mentioned the actual logical coding of the applications are very similar to any other language I have used. It is the view-based components, and how the different methods work that have caused the biggest challenge to me. I am slowly learning my way around the Android framework and I believe I will continue to enjoy this challenge.


Only1 Version 4

by Michael Clark
September 1, 2011 3:37 PM

When I was tasked with revamping the current iteration of Only1, I was initially overwhelmed - especially given what was requested. The idea was to increase the security around our password management so that we no longer relied solely on the last four of SSN and DOB to verify a user. The solution was a set of three security questions set up by the user when they first log-in to change their password. Sounds simple enough, right? Kind of.

The first question comes from a set of pre-defined questions. These were pretty generic and similar to the ones you might see on other sites (mother's maiden name, high school mascot, etc.).

The second question allows the user to type their own question and answer. This was so it would be difficult for two users to have the same security questions and thus knowing one another's answers.

The third question, and one that I initially thought would be difficult to program, involves a set of images unique to the user. When a user logs in, their username is assigned a set of 10 images - these images will always remain the same for the user and will always appear in the same order. This type of user verification is similar to what you might see on a banking website. With this third question, we can be sure that no two users will have the same answers.

Once the account is set-up, the user is given three options to proceed - the old username/SSN/DOB combo and two new methods. The first new method allows the user to enter their username and current password which would take them directly a change password page. The second new option allows the user to enter their username and then answer the three security questions previously set-up as verification before proceeding to the change password page. The existing username/SSN/DOB method still exists and requires answering the verification questions.

Once logged in, the user can also manage their account. This is helpful in the event a user feels their verification questions have been compromised or forgotten.

Only1 version 4 has been live since Monday and seems to be running smoothly so far.