Welcome to the repository for the various projects from my CS 360 Mobile Architect and Programming class at SNHU Online! This class focused on the development of a mobile application for Android, starting with planning and researching, and culminating in a working prototype of the application. For the final project I developed an event tracking mobile application for Android, using Android Studio. The application utilyzes a variety of Android subsystems such as RecyclerView for displaying the events, SQL Database helpers for storing both user information, and Alarm Manager to handle notifications for events. Users are able to create a username and password to log into the app, create events, and set a date / time when the event will "fire" as a notification. The events can be updated and deleted, and there is no limit to how many events a user can create.
During the class I developed a number of other applications in preparation for the final project. Some of these were created from various tutorials online, some were from the text, and some were of my own creation as practice.
The culmination of my learning can be found in the Final Project folder. For more information about the project, see the requirements document.
You can also check out the initial user requirements document for my research in regards to meeting user needs, and the initial project proposal to see what the original design was to be and how it changed as development progressed.
Building this application had me exploring the world of app development from start to finish. For the project I was tasked with designing my own app to fit around the specific requirements of the company that had "hired" me to develop for them. Once a design was settled on, I built the application in stages, starting with a simple basic log in feature and adding more features on a weekly basis. The project finished with a short description of a rollout plan for the application, focused on the best plan for releasing the app to market and potential ways to monetize the application.
I've spent some time before this working through the development cycle, and one thing that I've realized is that it is rarely the case that user needs are completely spelled out for developers. In order to supplement this lack of information, I've personally found that researching a ton is really helpful. For this application project, I started off researching similar applications to help me see not only different approaches to solving the same problem, but also what seems to work best and what doesn't. I've had some experience with apps, but I tend to find an app I like and stick with it; I don't download new apps very often and so therefor my own experience is not reliable. Research was key to starting development here. Once I know what the app should do, then I start to think about how I'm going to make it work. It's kind of an outside to inside approach. I think this works well, especially because at this point I don't know that there's anything that can't be done with code. So if it can be imagined, it can be built!
Check out my YouTube channel for more videos about coding projects I've done.
Also, check out my Personal Website for more information about me, and my LinkedIn to see if I'd be a good fit for your team.
much love -L