We need to add support to accept HbA1c readings to the DB and in the add recording UI

We will need a SQLite DB and also to ensure that Android M native app backup occurs between flashes and when users change hardware see: https://developer.android.com/preview/backup/index.html)

Edit this to add any remaining DB work this will track it for Noce!

For our initial release we will want users to be able to:
Set Demographics (Age, Gender, Language, Country, City)
Set Measurements mmol/L or mg/dl
Opt-In to Academic Research (Although backend wont be live till future version)
Input Category Customization (Measure before bed, after meal, fasting etc)
Notification Settings (Hourly, Daily or other interval reminders to input Glucose)

FAQ (view) added and implement bug reporter library.

We should allow users to track carbohydrate or meal intake and will need to add support to the DB and UI for this

• Spacing should be even on all 4 sides, there is too less space at top and way too much at bottom
• The buttons don't behave like buttons, basically they don't have any padding around them and hence the touch effect isn't visible at all
• Also, dialog shouldn't be full width
• In the dialog, I'm entering details at night, and it still says "Before breakfast" under "Measured"
• In the history panel, there is way too much shadow below the items
• The history items should be categorized by day
• The language should be pre-filled from system language if translations are available, otherwise english
• The time should be like "11:36 pm" or "23:36", according to system preferences
• The date should be formatted like "Tuesday, 1st September 2015" or similar human readable format
• The concentration amount should include the unit.
• Concentration amounts throughout the shouldn't be decimal, coz we don't allow entering decimal points, hence no use of showing it
• Amount should be orange if it goes above the average conc.
• The number below it should indicate how much does it fluctuate from average
• In the snackbar which appears on deleting an item, should have yellow text, not pink
• There seems to some empty space below the snackbar
• The background of history cards should be white
• The design of tips cards should be similar to history cards, e.g. - full width separators, white backgrounds
• The line height should be at least 1.5 for all paragraphs, paragraph spacing should be .75, e.g. - for 16dp, line height will be 24dp, and paragraph spacing will be 12dp.
• On scrolling, the titlebar and tabs should move up and the titlebar should hide
• Switching tabs seems to be unreliable, sometimes tapping on a tab does nothing. e.g. - Open app > Swipe 2 times to go to TIPS > Tap on OVERVIEW (doesn't work)
• If the design of the graph could be closer to the mockup, it would be better, especially the numbers on x and y axes. Basically, instead of writing the date on x-axis, it can be the heading, and x-axis can have the time only in bigger font. y-axis can get rid of decimal places, and can have bigger fonts
• In the overview mode, as well as everywhere else, separators should be full width
• Currently tips don't have a title, also try adding some tips which have actions, like update weight, set reminder etc.
• The tips tab should have a badge indicating number of tips
• In "Hello view", the button doesn't have any effect of tap (ripple/highlight)
• In "Hello view", the button should have an icon on it's right (chevron-right)

We want early feedback from users we should have a submit feedback option in settings. Can you add this to settings mockup.

We should add Google Fit integration and sync the following data in to Glucosio from Google Fit:

• Weight
• Activity
• Others ???

We should export to Google Fit:

• Any data Google Fit supports taking

We will need to update Terms of Use and add a privacy policy to cover this data sharing if users opt-in to Google Fit connection.

On my device, Samsung Galaxy S5, "Get Starting" is not viewable without scrolling.

We need to make sure our UI will scale to translated words as they may be larger than the UI is currently intended for instance overview translated to spanish is longer and so its tips.

Note from Mozilla's l10n lead staff:
Since they're translating strings out of context, they'll need to be able to test them within a build to ensure that the meaning is accurately represented in the translation, that the app is properly internationalized, and that their translations fit within the UI constraints of both a mobile device

We should add the ability to record weight and track weight in DB and UI

We should add Google Drive Backups to Settings so users can configure Glucosio to keep a backup of their data on Google Drive. We should integrate this so that backup syncing is automatic but also that there is a manual import feature to recover backups.

Add Customer Category Creation in settings so custom categories are then choosable when doing entries.

Settings (view) add backup options, implement code (backend) for occasional sync of glucose data to server or managed cloud provider for users who opt-in to academic research, add signup for newsletter

We need to create a backend framework or library (this might be better so other projects can use it) that will power our backups and can connect to a few providers such as Box, Dropbox, Google Drive, etc.

Settings lacks anyway to go back to main activity

Tips (view) to provide general diabetes tips to help users make choices that improve their outcomes.

@paolorotolo When you get to working on this lets discuss how this will work early on and I can help source a collection of tips that we can include. And later on perhaps we can make it more expansive.

I think we want to be sensitive about some users being in low bandwidth countries so we should ship some tips local but also have the option to have maybe a RSS feed to add more to the rotation.

Readings History Activity:

• Show Reading Entries
• Allow Editing & Deletion of Entries

Paolo,

Lets try and implement MVP https://github.com/konmik/konmik.github.io/wiki/Introduction-to-Model-View-Presenter-on-Android

The version in settings is input field

http://square.github.io/dagger/
https://github.com/square/dagger/tree/master/examples/android-simple

I worked a bit on the Glucat mascot today on my own. I'm pretty satisfied honestly. What do you think?

Once we start integrating third-party services and have support for recording weight, activity, bp etc we should investigate adding Balance Rewards Support.

https://developer.walgreens.com/api/balance-rewards/apimethod/balance-rewards-api

Since this wont be till way down the line I wont target this for now

In addition to before breakfast, etc, there needs to be additional categories.

Feedback from Jacob Park:
I recommend someone to clean https://github.com/Glucosio/android/blob/master/app/src/main/java/org/glucosio/android/db/DatabaseHandler.java, Cursors are a resource which must be closed after use. Furthermore, utilizing raw SQL and indices within inline code is not the best practice.

We need mockups for our initial design based on the specifications distributed to the team.

Jacob Park Remark:

I find the object oriented design of the project a bit weird. For example, in https://github.com/Glucosio/android/blob/master/app/src/main/java/org/glucosio/android/fragment/OverviewFragment.java why interact with the business domain object through parallel lists? Why not maintain one list of an object of those properties?

Add Hello View to ask more information about user on first start.

We convert reading_type from int to String to make sure user can add custom categories (issue #44).
@ahhmarr can you take care of this please?

We should have a way in Overview to display a daily/weekly/monthly graph and easily switch between them.

The trend over last month text we should maybe consider making "month" a selector and let users tap it and select day, week, month or year and have it display different averages with a tap.

Lets get @chrispecoraro feedback on this

an area dedicated to inputting glucose levels including level and picking a category such as fasting input, after meal, feeling sick, or a specific meal time.

See example of other apps input view

Since we will be optimizing and changing the database in the future undoubtedly we will need a ORM to help us ensure the future DB changes are not putting existing local db on handsets at risk of loss of glucosio data.

If we proceed without a ORM we will be digging a hole in terms of more work and problems

http://guides.codepath.com/android/Persisting-Data-to-the-Device#object-relational-mappers

@paolorotolo @ahhmarr @chrispecoraro please discusses the pros and cons of each of these and pick one and we do need to implement one sooner than later and likely for Noce.

We will want a dedicated graph view/activity powered perhaps by https://github.com/PhilJay/MPAndroidChart or another library that @paolorotolo finds suitable.

Additionally we may want to consider having the main view or main activity be a sort of dashboard that shows some smaller graphs and data see the blow example:

I like the main screen idea but theirs is kind of busy and we can do better on layout and design.

About (view) to list licensing information of the app and of open source libraries used and with a short paragraph about the project and current version of the app being ran. We could also have a link to our website, github etc here.

We will need to get a final build to our translators before we release so they can test their translations in the UI and make sure the context works.

Note from Mozilla's l10n lead staff:
Since they're translating strings out of context, they'll need to be able to test them within a build to ensure that the meaning is accurately represented in the translation, that the app is properly internationalized, and that their translations fit within the UI constraints of both a mobile device

https://developer.android.com/tools/building/configuring-gradle.html

11.1 mmol/l (200 mg/dl) is hyperglycemia while symptoms may not show till 15–20 mmol/l (~250–300 mg/dl) we should warn the user in the input dialog when they enter a glucose level that enters this range and say something like "The value you have entered is within the hyperglycemia range, consider consulting a medical professional." but still record the value.

Below 3.9 mmol/L (70 mg/dL) is diagnostic for hypoglycemia so we should woarn "The value you have entered is near hypoglycemia" if its not yet below but if it is below we should warn "The value you have entered is within the hypoglycemia range, consider consulting a medical professional."

In discussion with Paolo and Christopher it seems obvious that the database will need some changes to ensure it can scale to the kind of data we will be handling long term.

Lets identify with Christopher what changes he thinks are best and either he or @ahhmarr can implement them.

Paolo I will assign this to you can we get Christopher's email on Telegram and I can invite him so we can maybe assign to him. We have a very short window to release so lets push on this.

Add Gitty Reporter

We should consider having the glucosio icon in the top lefthand side of the app above tabs

https://github.com/Glucosio/brand-assets/blob/master/logos/png/PNG-07.png

At this point we should ensure the strings.xml is up to date with all strings in latest release and should begin translation.

Please convert preferred_language from int to string in Database.

We should add blood pressure tracking to DB and UI