Kicking Off the Healthizer – User Stories

To get the ball rolling on the development of the Healthizer app, I should start improving my own understanding of what it is exactly that I think I want to build. So, here is my first attempt at brainstorming some User stories to capture what I think the end user would want to see from this app, in the order in which I thought of them!

# User Stories
As a(n)… Grocery Shopper
I want to… easily scan the published ingredient list on any consumer product
So that… I will find out immediately whether the product contains any known carcinogens
As a(n)… Grocery Shopper
I want to… scan many products in rapid succession
So that… I can scan items as I pick them off the shelf, without slowing down my weekly shop
As a(n)… Grocery Shopper
I want to… quickly and clearly see whether the last-scanned product contains a known carcinogen
So that… I can determine which products are potentially dangerous without slowing down my weekly shop
As a(n)… Grocery Shopper
I want to… be able to scan items effectively regardless of the current strength of my Internet connectivity
So that… my weekly shop is not slowed down due to poor connectivity
As a(n)… Grocery Shopper
I want to… be able to see the names of the ingredients that were read by the app
So that… I can verify that the app correctly read the last-scanned ingredient list
As a(n)… Grocery Shopper
I want to… be able to see which specific ingredients were recognized as carcinogens by the app
So that… I can become better aware of which ingredient names in the last-scanned product are potentially dangerous
As a(n)… Grocery Shopper
I want to… receive some indication of how dangerous a recognized carcinogen might be
So that… I can make a judgement about whether I’d like to purchase the product or not
As a(n)… Grocery Shopper
I want to… See the source of the information which led the app to flag a given ingredient as a carcinogen
So that… I can satisfy myself that the app is flagging ingredients according to information provided by trustworthy authorities that is both accurate and unbiased
As a(n)… Grocery Shopper
I want to… be able to visit the original source of the information used to identify an ingredient as potentially dangerous
So that… I can verify the accuracy of the information and learn more about the ingredient from a source that I trust
As a(n)… Grocery Shopper
I want to… get a sense of how probable it is that a given ingredient is dangerous
So that… I can make a decision about whether or not I want to purchase the product
As a(n)… Grocery Shopper
I want to… quickly get a sense of how potentially dangerous the last-scanned product is, given the whole ingredient list
So that… I can determine whether I should read more about the product before deciding whether or not to purchase it
As a(n)… Grocery Shopper
I want to… scan ingredient lists according to the most recently published information on carcinogens
So that… I am able to assess my grocery choices according to the best possible information
As a(n)… Grocery Shopper
I want to… update my application data using the cheapest method possible
So that… I keep my data charges low
As a(n)… Grocery Shopper
I want to… be able to access the application quickly at all times
So that… I can scan my grocery list at any time, without slowing down my weekly shop

Ingredient List Scanning – A new idea?

Well it’s certainly been awhile since my last post announcing my intention to build the Healthizer app. I’ve been coding my little butt off for my startup company for several months, and as it turns out have had little time left in my schedule for anything else! However with me once I’m interested in something it never quite dies, it just goes on the back burner for a little while…

So now that our startup has published its app (I’ll post that link soon) I finally want to dig in and get on with this plan. Also I need a vehicle to mess around with some new development technologies I’m interested in.

Since I posted the app concept there have been quite a few apps cropping up containing similar functionality to the concept of Healthizer:

Don’t you hate it when you get an idea, and then find out someone else has already run out and done it way better than you ever could have?! Curse this manic business of high tech and all its brilliant people and wonderful apps! However, I believe there is still hope for the Healthizer.

  1. None of the existing apps use OCR technology (Optical Character Recognition – ie. computer reading) to parse ingredient lists. The preferred method out there for product lookup seems to be to scan UPC codes (ie. bar codes) and look up the associated ids in product databases. This method has a few drawbacks that I think would be avoided with my method:
    • it incurs a cost for accessing product databases through services such as Scandit.
    • a successful scan requires that the scanned product be registered in such a database and that the ingredient list in the database is accurate
    • it requires a working Internet connection, which has its own set of issues. For one, while the Internet is ubiquitous, having a good connection to it is still not a guarantee at all times (let me tell you), even in this day and age. Also, accessing the Internet in itself increases the cost of using the app, and slows it down.
  2. Most of these apps are not specifically geared at cancer prevention, with the exception of Think Dirty. Many of the apps are intended to assist shoppers make healthier decisions for weight-loss or lifestyle reasons, which means that the apps rate the healthiness of products based on some criteria. Therefore there is some subjectivity being introduced in their recommendations, and there is a question as to whether the user agrees with the criteria being applied – certainly not a straightforward question. Instead, I’d like to make an app that doesn’t recommend, it only points out to users the existence of a known carcinogen in the product they are considering buying, according to the product’s own manufacturer and lists of known chemicals published by mainstream authorities.
  3. Finally, it’s unclear whether the companies that produce these apps are for-profit companies. If so, there may be commercial motivations inherent in their recommendations. I feel that to gain users’ trust within the highly political fields of food manufacturing and cancer treatment, it’s important for the app to be strictly non-commercial, with a simple, straightforward algorithm, and transparent sources.

So I think there’s still room out there for a very simple, single-purpose app with a slick user experience that can be used very quickly and easily to flag a carcinogen-containing product with next to no fuss or fumbling or having to interpret the results. The main use case would be to scan products as you pick them off the shelf during your weekly shopping trip, so it has to be a streamlined experience.