https://blog.opensourcecurrency.org/tags/android/ Recent content in Android on Open Source Currency Hugo en-us Thu, 14 Jun 2012 07:25:00 +0100 https://blog.opensourcecurrency.org/2012/06/14/opentransact-on-android-2/ Thu, 14 Jun 2012 07:25:00 +0100 https://blog.opensourcecurrency.org/2012/06/14/opentransact-on-android-2/ <p>[youtube=http://www.youtube.com/watch?v=EZefmK1tndc&amp;w=560&amp;h=315]<br> <strong>Update (June 15)</strong>: <a href="https://play.google.com/store/apps/details?id=org.opensourcecurrency.hack">Cyberwire on Google Play App Store</a><br> <a href="https://github.com/herestomwiththeweather/cyberwire">Cyberwire</a> is an open source proof-of-concept for <a href="http://opentransact.org">OpenTransact</a> on Android. In the screencast, we see the Android app used to transfer 10 imaginary <a href="http://coffeebucks.herokuapp.com">coffeebucks</a> using one <a href="https://github.com/herestomwiththeweather/opentransact_example/tree/bearer">OpenTransact provider implementation</a>. Even with a different OpenTransact provider <a href="https://github.com/oscurrency/oscurrency/tree/rails31">implementation</a>, we see the same functionality accessed by the same Android app.<br> <a href="http://tools.ietf.org/html/draft-oauth-dyn-reg-v1-03">OAuth Dynamic Client Registration Protocol</a> is used to allow the Android app to start communicating with a new OpenTransact provider. A custom <a href="https://github.com/herestomwiththeweather/cyberwire/blob/master/src/org/opensourcecurrency/hack/AddProvider.java#L204">application_type</a> request parameter is set to &ldquo;noredirect&rdquo; to indicate to the provider that instead of the client providing its own redirect_uri, the provider should choose a uri within its own domain and after authorization, the client will snarf the authorization code parameter from that uri instead of its own.</p>