CSC 490: Team Dugong Project Blog

Posts

Week 6

This week we were mostly working on responding to the comments that we got form our first sprint demo. Things like cleaning up the UI, adding a few small features, starting to add a few larger features, and then some general bug fixes. We were very happy with how our app did in the demo but there were many things that we thought we could improve upon and features we could be add. For example, although we were very pleased with how our one to one chat function worked, one of the original pieces of functionality that we wanted for this project was a many to many chat feed sort of like a message board or chat forum for all of the different specific hobbies. This week, An started to build out this many to many chat functionality. It is still in development, as it is very complicated, but thankfully since we already had the one to one functionality up and running that made figuring out the many to many easier. Currently, An has the many to many chat feed working but it is not integrated int

Week 5: First Sprint

The first Sprint is done. We got some good feedback from both our professor and classmates. No one found any major bugs and mostly offered ideas for enhancemets, so all in all, a good first demo. Features complete for sprint one: Login/Sign up authentication Profile with database synchronisation Ability to add hobbies Search for specific hobbies Basic chat with other members of your hobby Navigation between functions Features in development: Location based member filtering. Will only list members of a hobby that are within a certain distance of you. Clean up chat screen UI and backend Enhance login and sign up with fogot password and email + password confirmation respectively Create a new navigation menu Notifications for chat, and marking members you have or are chatting with Ability to add new hobbies to list Clean up and enhance UI Various bug fixes About us page As you can see, we have a lot of work to do before the last sprint! However, the basics of

Week 4

This week the focus was on making connecting the profile page to the firebase database, starting work on the chat function, and starting the hobby list. Profile page now has age selector and gender selector that work correctly Profile page now sends updates for these, and all previously existing data fields to Firebase database Work on chat function has begun. Currently does not work, but the framework is set up for both the display and connection to Firebase. Expect more progress next week There is now a list of hobbies! Hobbies do not do anything when selected, functionality coming next week Connected to database Search function is now up and running Progress is being made for the first sprint at the end of next week, when we will have a working prototype of the final app. -This blog is slightly late, and all progress discussed occurred last week.

Week 3

This week everyone in our senior inquiry class was working on tech demos for various technologies in Android. For example, things like how to integrate camera functionality into the app, text-to-speech, speech recognition, GPS location data and GPS functionality, etc. Because we were all working on these tech demos throughout the week we didn't make very much progress on our app. James made some small quality of life changes to the code so that it would be more readable and would utilize more resources, Nick worked a little bit more on setting up the Firebase database and getting the hobby activity for the app setup and An did some research on Geo Location data. Although we didn't do all that much work this week on the app itself we learned a lot about different Android technologies that we could maybe include in our app. For example, since our app does need some GPS functionality because it is about connecting with people in your area who share your hobby, being able to use

2nd Week: Firebase and Design Choice

On this week, we focus on discussing and fine-tuning our proposal for the first sprint in week 7. We first look at different possible back-end database for our app. When deciding between a SQL or NoSQL database, we looked at the differences between scalability, data storage model, and database schema. Looking deeper into this, and listen to Dr. Stonedahl recommendation of Firebase, we concluded that it is the most fitting choice for its inherent compatibility with Android, cross-platform potential, scalability, and tutorial/resources availability. However, since all of our members have no experience with a NoSQL database, we think there might be a learning curve to get used to. About our design choice, we gathered feedback from our cross-group discussion from last week, as well as brainstorming about the difficulty of different functions of LocalHobby. With the 2-3 weeks timeline in mind, we decided to take some functions out of our original proposal, namely the nested tree design

Hello World!

Hello World! This is the inaugural post for the Augustana College CSC 490: Team Dugong Project official blog. In this blog we will sort do a run down of the different things we are doing each week with our project. Our team consists of three members, James Compere, An Nguyen Dang, and Nicholas Dippner. The project we are doing is an app called LocalHobby, which was thought up by An. The general idea is LocalHobby will be an app that people can use to find other people in their area who have the same hobby as them and while using the app they can interact with those people through chat rooms. Currently we are in very early stages of the project, still making use cases and user stories and story boarding. This week our main progress was making a detailed proposal of our project for the CSC 490 class that we are doing this project for. The proposal consisted of a four page write up where we gave a detailed description of the rationale behind the project, the features and requirements