The final sprint covers adding some data visualization to the Fitness Explorer app which is otherwise complete. In this article we'll delve into how Xuni was used in the app, and the different types of data visualization it provides.
The sixth sprint deals making an app look nice with different types of image assets and using Material Design. This article will discuss some of the differences in these different types of assets and generally using Material Design.
This article explores my fifth sprint working on the Fitness Explorer app where I look at using the Google Fit API.
In this article I'll delve into my fourth sprint where we cover several design patterns including creation, architectural, and structural patterns.
In this article I'll delve into my third sprint where we go deeper into Android architecture and cover Views, Layouts, and the Object Pooling pattern.
This article covers the second sprint and includes broad concepts like the Repository pattern, MVC architecture, and Unit Testing on Android.
This article discusses the concepts I learned in my first sprint including the Agile SDLC, task management with KanBan boards, and source control with TFS.
As a fitness enthusiast and technology geek I've been using the Google Fit Android app to heavily track and record my fitness activities. With it's proprietary low battery step counting service it keeps track of my steps on my phone, without a fitness tracker! Google Fit is great, for recording my fitness activities that is. But when I need an quick and easy aggregated view of my fitness history it was difficult to easily find this information in Google Fit. This is why I created the Fitness Explorer app during my summer internship at GrapeCity, to get a instant dashboard of my fitness history for the day, week, and even the month!