 |
| Main user screen |
Our app operates as a BAC calculator that takes into account time since drinking, the number of drinks, weight of the user, and gender.
The app has 13 variables, of which over half are input by the user. The user specifies his gender, weight, and the number of drinks he has had. Then, the user will click the button labeled "Whats my BAC?"
This will return the user's BAC value which is extracted from an equation that accounts for all of the data the user has entered, as well as a clock to track the amount of hours each drink has been in the user's system.
 |
| Main calculation code |
The question at the bottom of the page: "Am I Safe to Drive?" will analyze the BAC that was returned previously, and if it is too high, it will tell the user to please, call a cab.
 |
| Other code to gain data for the main calculation |
Reflection Questions:
1.) Reflect on the creative process you used. What was useful? Discuss your reflection with your partner and then write a reflection individually.
Our creative process involved a lot of input from each member of our group, and we then decided on a specific task by weighing a number of factors, including feasibility and usefulness. We think that this was useful because it helped us to develop an app that was both possible and useful. I myself agree because if we had not considered these factors we may not have made any progress at all.
2.) Reflect on team dynamic. What helped the team work well together? Discuss your reflection with your partner and then write a reflection individually.
We used a single computer with input from each other. The computer was mainly used by one person while the other members of the group suggested or drew up plans, or tested other ideas on a different computer. We think this worked well because working over multiple computers sometimes makes for inefficiency. I would agree and found that this method was the best available.
3.) What problem was your app trying to solve? How well does it?
Our app was an attempt to make a simple, user friendly way to check your BAC and determine if you were safe to drive. It solves the problem, however some coding errors make the data difficult to interpret. It correctly calculates for BAC based on input values and time, but represents the data incorrectly.
4.) Describe the two hardest challenges you experienced when coding this app.
The hardest challenge (third screenshot, above) was the timekeeping. We had to create a clock that recorded the time when the "Add Drink" button was first clicked, and then record the time again when the "Whats My BAC" button was clicked, subtract the time differential, and then interpret this data as hours to be implemented into the equation. This works, but the problem still remains that the data is represented incorrectly. Mainly, the data seems to be flawed for as long as "Male" is checked. Our code for the male is identical as that for the female, except with changed variables accordingly, so this error has been difficult to solve.
5.) Given more time, how could you improve your game?
Given more time, we could have fixed the timekeeping issues, the male representation problem, and also implemented additional features such as a variable proof slider, variable oz. slider, and a feature that allows the user to quickly call a cab if his BAC is too high.
AIA File
APK File