View the "Price Check Mobile Application Screen Flow" page

9 views
Skip to first unread message

roBman

unread,
Jul 12, 2009, 8:03:22 AM7/12/09
to price_check
Hi,

I've uploaded a basic screen flow (diagram and descriptions) for the
initial Price Check mobile application.

Please click on http://groups.google.com/group/price_check/web/price-check-mobile-application-screen-flow
- or copy & paste it into your browser's address bar if that doesn't
work.

All feedback and suggestions welcome.

NOTE: This is purely designed to show the basic screen flow. It does
not address Information Architecture or Labelling, Screen Content or
the underlying Data Model. However I have checked it to confirm that
all of this process is technically feasible and basically usable.

Release early and release often!

I look forward to hearing your comments...


roBman

Alex

unread,
Jul 12, 2009, 8:53:13 PM7/12/09
to price_check
Looks good Rob. I will put together some initial high level
wireframes based on these keyscreens, as well as breaking out detailed
scenarios that map to this diagram.

alex

Luke

unread,
Jul 24, 2009, 1:41:55 AM7/24/09
to price_check
I like the screen flow current shopping list
I was thinking of doing a similar app for the iphone. using the iphone
camera to "scan the barcode"
but the problem is for it to work there needs to be alot of people
updating the information.
I'll be following this closley :)

Rob Manson

unread,
Jul 24, 2009, 1:59:10 AM7/24/09
to price...@googlegroups.com
Hi Luke,

thanks for joining in and providing your feedback.

We've had some discussion recently about barcode scanning and there
might be a toolkit that works more reliably than the other options we've
tried called "red laser".

However this only works on iPhone.

I think having options for other mobile devices and PC's as well is also
important as you pointed out.

We'll have some more detailed wireframes up next week so please join in
and help shape this to become a really useful project.


roBman

Luke

unread,
Jul 24, 2009, 2:07:45 AM7/24/09
to price_check
Sounds good looking forward to it.
Let me know if you require a developer to help you out

Simon Rumble

unread,
Jul 24, 2009, 3:24:57 AM7/24/09
to price...@googlegroups.com
2009/7/24 Rob Manson <roB...@mobusiness.com.au>

We've had some discussion recently about barcode scanning and there
might be a toolkit that works more reliably than the other options we've
tried called "red laser".

However this only works on iPhone.

This library does it on rather a lot of platforms:

http://code.google.com/p/zxing/

and here's a rather trivial Python implementation for Android:
http://www.mattcutts.com/blog/android-barcode-scanner/
 
--
Simon Rumble <si...@rumble.net>

Rob Manson

unread,
Jul 24, 2009, 3:42:23 AM7/24/09
to price...@googlegroups.com
Hi Simon,

thanks...that's great. We've tried a few others but weren't so happy
with their performance.

As part of phase 2 I think we might line up all the barcode toolkits and
organise a bake-off - that's something the group can really help with by
trying them on their different phones if we can bundle them into simple
test applications.

Feel free to create a page on the google group to list any barcode
toolkits you find and we can all contribute to that list.


roBman

Richard Ferrers, Melb

unread,
Jul 31, 2009, 9:43:32 PM7/31/09
to price_check
Hi all,
Just had a thought after Sat am shopping.

Goals: - get most data in
- with minimum human effort
- maximum system effort

Thought: OCR - optical character recognition

Data Input Use Case:
1. Consumer shops, gets docket receipt
2. Photographs receipt, including location, date, time, product
description, product price, total
3. User emails or MMS photo to price_check@price_check.com

Data Processing Use Case:
1. System receives image file of docket receipt by email or mms
2. OCR software converts image to field data, including sender's email
address/mms user as account details
3. If user puts "anonymous" in subject, then no sender information is
stored, or in body of mms message
4. System records purchases against user, and in master shopping list,
by product, location, time, price
4. OCR exception file created for manual review
5. Manual reviewer examines exception file, and hand codes or deletes
file from exception file list
6. Reporting: Discounts found from Normal prices, by store, by Nearby
Reply all
Reply to author
Forward
0 new messages