radiocells-scanner-android
radiocells-scanner-android copied to clipboard
openbmap
Update app on Google Play
openbmap 0.4.999 is available from Google Play at
https://play.google.com/store/apps/details?id=com.googlecode.androidcells
Why not update it?
Original issue reported on code.google.com by [email protected] on 10 Mar 2015 at 10:29
Mumble, mumble, bad execuses :-)
You're right, this issue makes perfect sense. Google Play hasn't had the
highest priority in the past, since we focused on the F-Droid releases
(https://f-droid.org/repository/browse/?fdfilter=radiobeacon&fdid=org.openbmap)
Nevertheless I fully agree with you that the outdated 0.4.99 release available
at GP can cause some confusion, so I'll add this to the TODO list
Original comment by wish7code on 11 Mar 2015 at 8:17
- Changed state: Accepted
I have to say I was also a bit confused by all the different names: The app is only referenced as "radiobeacon" but it eems to be called "openbmap" in the Google store. What's involved in updating the Google store version? I assume that the huge majority of potential contributors is more likely to install something from Google's store than bothering with sideloading.
Well, you're absolutely right! Really sorry for the confusion. Radiobeacon once started as a 'rescue' client for the openbmap project, as the Playstore client wasn't working anymore due to server-side changes. That was back in 2012 if I remember correctly.
Since then the 'rescue' client has become the only and official client, but since I'm more the technical guy I confess I didn't pay enough attention to the communication side ;-)
Personally I prefer the open source playstore alternative FDroid, so you'll always find the latest official client there (https://f-droid.org/repository/browse/?fdfilter=radiobeacon&fdid=org.openbmap)
Recently I've been in contact with Nick, the initial project founder, to clean up the domain issues (radiocells.org vs. openbmap.org) and the Google playstore issues. I hope to solve this issues very soon with the kind help of Nick to make this less confusing...
- I hate FDroid and it is overkill for users just to get this one app which doesn't violate Google terms anyway and might as well be on Google Play.
- Your website should give users a choice, instead of only FDroid download logos.
- Yes glad there is an .apk link... but until you guys can figure out how to properly put your app on Google Play, you can't blame potential users for lacking confidence.
On https://radiocells.org/ there is no Google Play link to your app. All other such apps are on Google Play. If you were serious about this project, you would put it on Google Play. There is no legal barrier.
Being the gold sponsor, who financed the radiocells.org projects with +1000 bucks last year, I'm looking for a silver sponsor, who is sponsoring the $25 registration fee for the Google Play dev certificates.
OK but you will have your sum anyway in $ perl -wle 'print int 25 / ( 1000 / 365 );' 9 days.
However your app is already on Google Play, https://play.google.com/store/apps/details?id=com.googlecode.androidcells
You just need to add the link to https://radiocells.org/ .
Place it next to the link already there to https://f-droid.org/repository/browse/?fdfilter=radiobeacon&fdid=org.openbmap which by the way is 404.