Advertise with Googlier.com pages tagged android http://www.bitpipeline.eu/tags/android/ BitPipeline ikiwiki Sun, 21 Sep 2014 13:40:47 +0200 IParkAmsterdam - opensource http://www.bitpipeline.eu/Blog/20140921-IParkAmsterdam-opensource/ http://www.bitpipeline.eu/Blog/20140921-IParkAmsterdam-opensource/ android iparkamsterdam opensource software Sun, 21 Sep 2014 13:40:47 +0200 2014-09-21T11:40:47Z <p><a href="http://www.bitpipeline.eu/Blog/20140921-IParkAmsterdam-v0.3.png"><img src="http://www.bitpipeline.eu/Blog/20140921-IParkAmsterdam-opensource/192x-20140921-IParkAmsterdam-v0.3.png" width="192" height="320" class="screenshot" align="right" /></a></p> <p>A long time ago (really, it feels like ages) I wrote a small Android application to help people find less expensive parking places in Amsterdam making use of <a href="http://www.parkshark.nl/">Glimworm SharkPark API</a> and OpenStreetMaps.</p> <p>Today, one year and five months after the first release, I decided to set the application free and opensource it.</p> <p>The code is available at <a href="https://github.com/migtavares/IParkAmsterdam">github/migtavares/IParkAmsterdam</a> and I invite everyone to fork it and send pull requests.</p> <p>I can tell you that today's morning was a fun one... lots of remembering how things were done last year.</p> <div style="clear:both"></div> WindsurfBuddy: equipment browser, viewer and editor http://www.bitpipeline.eu/Blog/20131113-WindsurfBuddy_equipment_management/ http://www.bitpipeline.eu/Blog/20131113-WindsurfBuddy_equipment_management/ android software windsurfbuddy Wed, 13 Nov 2013 11:56:14 +0100 2013-11-13T10:56:14Z <p>The implementation of equipment management within <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a> is proceeding although at a pace that is not as fast as I would like.</p> <p>So what's done until now?</p> <p><a href="http://www.bitpipeline.eu/Blog/20131113-WindsurfBuddy-browser.png"><img src="http://www.bitpipeline.eu/Blog/20131113-WindsurfBuddy_equipment_management/192x-20131113-WindsurfBuddy-browser.png" width="192" height="319" class="screenshot" align="right" /></a></p> <p>Browsing the equipment in the database is pretty much done. A rolling tabs header and then a simple straight forward list of equipment. </p> <p>Taping the plus action creates a new equipment of the type of the currently selected tab. Taping on a equipment item brings up a new activity to view that specific equipment. A long tap on any equipment of the list will toggle into the list into multiple selection mode that can be used to remove several item. Maybe in the future it will also enable exporting the selected equipment... we'll see.</p> <p><a href="http://www.bitpipeline.eu/Blog/20131114-WindsurfBuddy-viewer.png"><img src="http://www.bitpipeline.eu/Blog/20131113-WindsurfBuddy_equipment_management/192x-20131114-WindsurfBuddy-viewer.png" width="192" height="319" class="screenshot" align="left" /></a></p> <p>Viewing each equipment is now a activity on its own instead of a floating dialog. I feel that it makes better use of screen space and being an activity allows for future integration with other applications. The layout is similar the one used for viewing contacts making it a familiar display to the user.</p> <p>The little pencil action allows to launch a editing activity for the equipment being viewed.</p> <p><a href="http://www.bitpipeline.eu/Blog/20131115-WindsurfBuddy-edit.png"><img src="http://www.bitpipeline.eu/Blog/20131113-WindsurfBuddy_equipment_management/192x-20131115-WindsurfBuddy-edit.png" width="192" height="319" class="screenshot" align="right" /></a></p> <p>Editing a equipment is still a ongoing implementation. Done are editing the name of the equipment as well as it's brand, collection and description. The real slaving will be over editing the very specific details of each equipment. I don't want to have a implementation that is tide to each equipment but would rather have a more generic approach.</p> <p>The green plus signs right of the brand and collection selectors will be used to quickly create a new brand or collection, speeding up the insertion of new equipment.</p> WindsurfBuddy: equipment database http://www.bitpipeline.eu/Blog/20130826-WindsurfBuddy-databasing/ http://www.bitpipeline.eu/Blog/20130826-WindsurfBuddy-databasing/ android software windsurfbuddy Mon, 26 Aug 2013 15:56:50 +0200 2013-08-26T13:56:50Z <p>Lately I have been working on having a proper database of equipment for <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a> and using the database engine to do most of the processing of providing the best equipment advice. Until now the equipment was a static collection of Java objects and resources.</p> <p>I have several <em>hopes</em> on the result of development:</p> <ul> <li>easier to extend suggestions: for example also provide masts advices according to the sail specifications and brand "affinity" (some sails work better with some mast brands);</li> <li>user management of the equipment (adding, editing, deleting, etc);</li> <li>sharing of equipment data between users and a central equipment repository (still just an idea).</li> </ul> <p>The database schema for now is composed of around 20 tables - not that many but keep in mind that this is running in phones, even older Android phones too. To avoid writing lots of code that translate SQL results into Java objects (a <a href="https://en.wikipedia.org/wiki/Object-relational_mapping">ORM</a>) I'm using <a href="http://ormlite.com">ORMLite</a>. Some, if not most, of the queries to the database are still almost raw SQL.</p> <p>Until now it this approach work well but is still far from being comparable to the existing static objects and resources implementation. That moment is nevertheless getting closer and the next 1.5 release will start using this database for the equipment.</p> WindsurfBuddy: 1K+ active users http://www.bitpipeline.eu/Blog/20130722-Windsurfbuddy-1000-users/ http://www.bitpipeline.eu/Blog/20130722-Windsurfbuddy-1000-users/ android software windsurfbuddy Mon, 22 Jul 2013 15:00:34 +0200 2013-07-22T13:00:34Z <p>Acording to Google statistics <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a> has pass the mark of the 1000 active users on 10th of Jully. It's rewarding to see that this small project is growing.</p> <p>My thanks to the all users.</p> <p>Don't forget that you can join the <a href="https://plus.google.com/communities/102165194897985318092">Google+ Windsurf Buddy.beta community</a> and get early beta versions of <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a>.</p> WindsurfBuddy: beta versions and almost ready to ship http://www.bitpipeline.eu/Blog/20130613-WindsurfBuddy_Almost_there/ http://www.bitpipeline.eu/Blog/20130613-WindsurfBuddy_Almost_there/ android software windsurfbuddy Thu, 13 Jun 2013 19:19:59 +0200 2013-06-13T17:19:59Z <p>Since the last great Google I/O 2013 its possible for android developers using deploying Google Play to distribute their applications to also release alpha and beta versions to a exclusive set of users. The way Google uses to define that set of users is using a Google+ community of a Google Groups. I decided to give it a trial with the former.</p> <p>So now available at Google+ is a community of adventurous people that don't mind trying the beta versions of <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a>: <a href="https://plus.google.com/communities/102165194897985318092">Google+ Windsurf Buddy.beta community</a>. Feel free to join in.</p> <p>Today I am going to release the beta 3 of version 1.4. If everything feels solid and working properly then I'll upgrade to production.</p> <p>So what is new/different in the new version? In terms of features maybe not much has change - added support for dagger fins and removed the wind speed converter that is available as a single application with more capabilities than while a feature of <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a>. The major change is in the UI and the underlying code.</p> <p>Planed for the near future are some improvements in the algorithms used to calculate sail size and fin length. Specially when it comes to racing and speed windsurfing. Then the management of equipment has to be implemented. That is bound to be fun... <img src="http://www.bitpipeline.eu/smileys/smile.png" alt=":)" /></p> <p>I do hope you enjoy it.</p> IParkAmsterdam http://www.bitpipeline.eu/Blog/20130414-IParkAmsterdam-dev/ http://www.bitpipeline.eu/Blog/20130414-IParkAmsterdam-dev/ android iparkamsterdam software Sun, 14 Apr 2013 23:53:11 +0200 2013-04-14T21:53:11Z <p>I've been thinking about implementing a simple Android application that uses mapping for quite a while but never found the time or the right idea to start.</p> <p><a href="http://www.bitpipeline.eu/Blog/20130414-IParkAmsterdam-development.png"><img src="http://www.bitpipeline.eu/Blog/20130414-IParkAmsterdam-dev/192x-20130414-IParkAmsterdam-development.png" width="192" height="320" class="screenshot" align="right" /></a></p> <p>Yesterday I participated in a <a href="http://meetup.appsterdam.rs/events/112812892">Appsterdam event</a> with the guys from <a href="http://www.glimworm.com/">Glimworm</a> showing and talking about <a href="http://api.parkshark.nl/">Park Shark API</a>, the Open API they created for querying the price of parking in the city of Amsterdam.</p> <p>Today, after enjoying a nice bicycle ride (first day of the year were you could go out with a simple sweater), I decided to get my hands dirty and create a small application that made use of the Park Shark API and some mapping solution.</p> <p>I don't really want to use a <a href="https://developers.google.com/maps/documentation/android/">Google Maps Android API</a> key for this small applications and I am a big fan of <a href="http://www.openstreetmap.org/">Open Street Maps (OSM)</a> for quite a long time. Searching for possible ready to go solution that would allow me to use OSM within a Android application lead me to the project <a href="https://code.google.com/p/osmdroid/">OSMDroid</a> that provides a very similar API to the Google Maps API.</p> <p>The name of the application includes a <em>beta</em> but it's really just very preliminary code. I did have fun writing it, and had some struggles to get things going as I desire. Specially when it comes to the interaction with the map.</p> Wind Speed Converter release 1.5.4 http://www.bitpipeline.eu/Blog/20130412-WindSpeed-bugFix-release/ http://www.bitpipeline.eu/Blog/20130412-WindSpeed-bugFix-release/ android software windspeedconverter Fri, 12 Apr 2013 11:36:08 +0200 2013-04-12T09:36:08Z <p>A new release of <a href="http://www.bitpipeline.eu/Projects/WindSpeedConverter/">WindSpeed</a> Started to use the API key for use when contacting the Open Weather Map servers and better user notification of error when updating the weather station information.</p> Windsurf Buddy - continuing development http://www.bitpipeline.eu/Blog/20130411-WindsurfBuddy-development/ http://www.bitpipeline.eu/Blog/20130411-WindsurfBuddy-development/ android software windsurfbuddy Fri, 12 Apr 2013 08:53:39 +0200 2013-04-12T06:53:39Z <p>Work is on going for the next <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a> version.</p> <p>The equipment advisor is getting to be slightly more capable than the previous one, with more rule matching to make sure that only the things that make sense show up. For example if a user chooses a <em>Beginner</em> use case then it doesn't make sense to show windsurf disciplines like <em>wave</em>.</p> <p>The next screenshot is just a view of my desktop while working on <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a>. Would you believe that I have fun this way? <img src="http://www.bitpipeline.eu/smileys/smile.png" alt=":)" /> <center> <a href="http://www.bitpipeline.eu/Blog/20130411-WindsurfBuddy-development.png"><img src="http://www.bitpipeline.eu/Blog/20130411-WindsurfBuddy-development/384x-20130411-WindsurfBuddy-development.png" width="384" height="240" class="screenshot" align="center" /></a> </center></p> <p>Another things that I have been toying is the presentation of the multi-fin information. I don't know if this right/left looks nice (the one shown in the bigger Android emulator window).</p> <p>One good news in regard to fin selection: it will be possible to change the balance of the fins length -- have more control or earlier planning. I'll write more about this soon.</p> Windsurf Buddy - work in progress http://www.bitpipeline.eu/Blog/20130405-WindsurfBuddy-WIP/ http://www.bitpipeline.eu/Blog/20130405-WindsurfBuddy-WIP/ android software windsurfbuddy Fri, 05 Apr 2013 16:30:02 +0200 2013-09-23T09:34:44Z <p>It's has been quite a while and <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Windsurf Buddy</a> is in need of some care. Specially the UI, which feels old fashion -- it has a clear Android Gingerbread feel to it.</p> <p><a href="http://www.bitpipeline.eu/Blog/20130405-WindsurfBuddy-wip-advisor.png"><img src="http://www.bitpipeline.eu/Blog/20130405-WindsurfBuddy-WIP/192x-20130405-WindsurfBuddy-wip-advisor.png" width="192" height="320" class="screenshot" align="left" /></a></p> <p>So it was time for a revamp of the UI and to take advantage of the new features of the Android OS such as <a href="https://developer.android.com/guide/components/fragments.html">fragments</a> and new <a href="http://android-developers.blogspot.nl/2012/01/holo-everywhere.html">Holo</a> style.</p> <p><a href="http://www.bitpipeline.eu/Blog/20130406-WindsurfBuddy-wip-settings.png"><img src="http://www.bitpipeline.eu/Blog/20130405-WindsurfBuddy-WIP/192x-20130406-WindsurfBuddy-wip-settings.png" width="192" height="320" class="screenshot" align="right" /></a></p> <p>It's far from finished. Much work still ahead before the next release.</p> <p>The old dashboard is gone. I think it made sense at the time (so many other applications were also using it) but it became old fashion rather quickly. With good reasons actually. With this redesign when starting <a href="http://www.bitpipeline.eu/Projects/WindsurfBuddy/">Wind speed</a> the user will be presented with exactly what he is expecting to use: some good tips on what equipment to use.</p> <p>The rest of the application can be reached either by using the navigation within the application bar or, for some very specific activities, by using the menu.</p> <p><a href="http://www.bitpipeline.eu/Blog/20130407-WindsurfBuddy-wip-catalog.png"><img src="http://www.bitpipeline.eu/Blog/20130405-WindsurfBuddy-WIP/192x-20130407-WindsurfBuddy-wip-catalog.png" width="192" height="320" class="screenshot" align="left" /></a></p> <p>One feature I think I'll drop from the application is the Wind Speed Conversion but will probably integrate it with the <a href="http://www.bitpipeline.eu/Projects/WindSpeedConverter/">Wind speed</a> application. No duplication of functionality and it will be a lot easier to manage.</p> <p>On the other hand.. I'm dying to squeeze some new features like adding equipment definition which would enable the user to add it's own equipment.</p> <div style="clear:both"></div> Migrating from Google Reader into a better world http://www.bitpipeline.eu/Blog/20130328-TT-RSS/ http://www.bitpipeline.eu/Blog/20130328-TT-RSS/ android atom rss software ttrss Thu, 28 Mar 2013 08:33:35 +0100 2013-03-28T08:54:26Z <p>Here at BitPipeline we do like to read our internet news on a bunch of different devices and the soon to be dead Google Reader fitted that role perfectly (thanks to the easy to use Web and Android applications).</p> <p>With the dismiss of Google Reader on the horizon I set myself the task of during one weekend finding the best alternative. After reading some articles and looking at the different choices out the in the Internet the set of possible solutions was:</p> <ul> <li><a href="http://www.feedly.com">Feedly</a> : too much emphasis on images and a design that might appeal to Mac aficionados but doesn't ring my bell. No API to integrate with other applications/services. Closed proprietary source.</li> <li><a href="http://newsblur.com/">NewsBlur</a> : Really nice except for the abuse of intense colours in the design. Also doesn't seem to export any API. OpenSource, so should be possible to self host. Supports sharing within NewsBlur host.</li> <li><a href="http://tt-rss.org">Tiny Tiny RSS</a> : (also know as tt-rss) Simple elegant design. Exports a API (can be switched on/off). Supports sharing to social Networks, to a rss feed or within the same tt-rss instance. Supports plugins. Can use the same keyboard shortcuts as Google Reader. Open source. Themable (even to the point of looking a bit like Google Reader).</li> </ul> <p>Tiny Tiny RSS was a clear winner.</p> <p>I had lying around a old Asus eeePC 901 and so I set myself to install <a href="http://www.gentoo.org">gentoo</a> and set it up to be the host of my tt-rss. This will be a post by itself - I used some of the great gentoo features to make this install and maintenance as easy and smooth as possible.</p> <p><center> <a href="http://www.bitpipeline.eu/Blog/20130328-ttrss.png"><img src="http://www.bitpipeline.eu/Blog/20130328-TT-RSS/384x-20130328-ttrss.png" width="384" height="240" class="screenshot" align="center" /></a> </center></p> <p>This looks like it has been good of Google to trigger this migration. Good for me, maybe not so good for Google in the long run (I am going more and more for the self hosted services option as cloud services are proving to be just vapour).</p>