it's not every day i get to quote myself, but this should answer why we wanted to use android and appengine...
"The biggest reason we use Android is because it?s open source. It?s not the first open mobile operating system, but it?s the first open and comprehensive system with the wide and viable device support that our users need. Moreover, as researchers we need to be able to transform the mobile device into whatever we imagine, whether it?s a mobile ultrasound unit or a gesture recognizing computer. Android?s open source framework means we are free to innovate however we see fit, independently of what other organizations in the Android ecosystem do. The choice of App Engine is driven by the use cases we?ve seen in the field. It?s difficult for most organizations in resource constrained regions to keep infrastructure running. Simply keeping the power running and the data servers up to date can be quite challenging. For the many places that have connection to the web via the cell phone network, it is often more time and cost effective to use something like Google?s App Engine. Another way to think of it is by analogy with the email infrastructure. Running an email server is hard, but with services like Gmail anyone can have email. We want to build services that make data collection as easy as email." http://www.frontiereconomy.com/2009/11/data-collection-where-its-needed-the-most/ On Sat, Jan 9, 2010 at 21:56, James Dailey <jamespdailey at gmail.com> wrote: > Cory, > Let's keep this on the list in case it is interesting for others. ?The UW > Change group includes several people who have spearheaded an Android toolkit > that runs on a mobile device. ?see http://code.google.com/p/open-data-kit/ > As to why the Android OS comes up in "development lists" and > conversations... I think that the main reason is that Google has positioned > it as the next platform for the smartphone /mobile/ tablet covergence world, > ?Its open, meaning it is being offered to any handset manufacturer and has > the backing of major content players in the market (esp Google), plus the > backing of major network players. ? This is a killer combo for market > acceptance. ? This contrasts with the Apple iPhone approach, which is only > available from Apple, on Apple handsets, and locked to specific carriers and > thus not available in many countries. > > What this leads to is that the Android marketplace follows a very open > approach as well - meaning that applications are created and then made > available - there is no process like that used by Apple's to control what > gets presented to users. ? This makes it ideal for small software > applications to be built rapidly and launched immediately. > > We do see Microsoft trying to make up ground in this space, and Blackberry > cannot be counted out (largest corporate base of smartphone users), but > Android has caught the attention of international NGOs.? Both Palm OS and > Symbian OS on mobile enabled devices have significant followers and continue > to be viable, but both currently lack one of the elements for market > acceptance I mentioned above. > > Regards, > > > James > > > > > On Fri, Jan 8, 2010 at 12:21 AM, Bush, Cory <CBush at tns.org> wrote: >> >> Hi James, >> >> >> >> Thanks for the detailed set of suggestions. ?You?ve very right?we are >> already in discussions with Costco?s coffee roaster to implement a system >> such as this; the trick is that they?re much more likely to pay a per pound >> premium for the information coming from this system rather than funding its >> development and implementation. >> >> >> >> I like the idea of pursuing this with a grocery manufacturer, though think >> you?re right that no such device exists?at least not one which hits a >> pricepoint needed for rural contexts.? Symbol makes some handhelds, but they >> are generally US$1000+.? Also agree that convergence would be more useful >> for the recording/printer device.? People will trust a simple digital (US$20 >> or so) scale. >> >> >> >> One question: I haven?t followed many of the trends in mobile device >> development, but have noticed that Android comes up in many peoples? >> thoughts.? What?s behind this (sorry for my ignorance). >> >> >> >> Thanks again for your help >> >> >> >> Cory >> >> >> >> From: James Dailey [mailto:jamespdailey at gmail.com] >> Sent: Thursday, January 07, 2010 8:40 PM >> To: Bush, Cory >> Cc: change >> >> Subject: Re: [change] Digital scale / transaction recording device >> >> >> >> Hi Cory -? An interesting question and spec.? Hopefully, I'm not too off >> base with this email. >> >> In the Seattle area, COSTCO, which sources its coffee from Rwanda, is >> potentially a good resource - but you probably already know that.? I don't >> have a contact, but you might try finding the local COSTCO purchasing rep in >> Rwanda and/or send an email to the CEO, Jim Sinegal. >> http://www.fastcompany.com/magazine/134/special-report-rwanda-rising.html >> >> COSTCO would have the kind of corporate relationships to perhaps help with >> this type of device sourcing.? And $$. >> >> My guess is that there is nothing quite like what you are describing. >> Embedding of data in devices that are wireless network aware is still an >> emerging field. >> >> Rephrasing the question:? How could you marry the ODK/ Android-device with >> a standard weighing device? >> >> Setting aside the specific data input device:? A grocery equipment manager >> (that you might find at COSTCO), would be better able to send you device >> specs for a scale. >> >> My advice would be to keep the devices separate.? Get a low cost analog >> scale, and have them record the amt on the Android. >> >> But that's not very technically satisfying... so if you do want to try for >> device convergence...most (all?) of the Android phones have a mini-USB port >> that I believe the ODK can access for other purposes (external bar code >> readers?).? So the trick would be in selecting a weighing device (scale) >> with a serial data output and then in getting whatever drivers or API >> changes would be necessary to make the connection work (non-trivial). >> >> Under the heading:? If you can build a solution for more than one >> customer, you have a market, it occurs to me this could also be useful in >> infant weighing programs, a part of many public health programs in Africa. >> So, you might find common cause around that, ie where the "transaction data >> of the coffee bean" is instead date of birth, mother's name, etc. >> >> Best of luck with this. >> >> Regards, >> James >> >> On Thu, Dec 10, 2009 at 1:18 AM, Bush, Cory <CBush at tns.org> wrote: >> >> Greetings all, >> >> I?m trying to scope a solution for coffee cooperatives here in Rwanda that >> will enhance transparency into the sale of coffee at small community-level >> collection points, and would appreciate any thoughts / ideas / device >> recommendations.? Basic requirements would include: >> >> -?????? A digital scale capable of weighing up to 30kg >> >> -?????? Ability to capture transaction information including: ID#, price >> per kilo, KG delivered, coffee grade, collector ID#, payment type >> (cash/bank) >> >> -?????? Ability to generate a paper receipt >> >> -?????? Ability to transmit transaction information in real-time if mobile >> data network available or store-and-forward batches if data network >> unavailable >> >> -?????? Ability to generate daily/weekly/monthly reconciliation or summary >> reports >> >> -?????? Ideally the scale, transaction device, and printer would be >> integrated, but not necessary >> >> -?????? Device(s) should have low power requirements, and be able to >> function for a full day between charges or be powerable via standard >> batteries. >> >> -?????? Device(s) should be rugged enough for use in rural settings >> >> Thanks in advance for any insight, >> >> Cory >> >> Cory Bush >> RW Mobile: +250-788-309287 >> >> RW Office:? +250-252-580414 >> Skype: corycbush >> >> _______________________________________________ >> change mailing list >> change at change.washington.edu >> http://changemm.cs.washington.edu/mailman/listinfo/change >> >> >> -- >> James Dailey >> MicroEnergy Credits >> skype: jdailey >> +1 206 234 8435 mobile > > > -- > James Dailey > MicroEnergy Credits > skype: jdailey > +1 206 234 8435 mobile > > > _______________________________________________ > change mailing list > change at change.washington.edu > http://changemm.cs.washington.edu/mailman/listinfo/change > >
