Tom posts some excellent points:
>Why is Android is such a good platform for programming radios that you're willing to rewrite Chirp?
>You should try to articulate this. If you can't, maybe it's not worth your time.(TRUE!!)
- Because I don't carry a laptop or netbook, and don't want to start. I do carry a phone or tablet.
- Android vs. iOS....because Android has a larger market share, and because I think it will be easier. I might be proven wrong!
- I see a few other people have requested it
- Because I have too much time on my hands?? ;)
>If you're going to use the Chirp brand name, we should probably review your work before release.
I concur.
> You have to go to great lengths to run Python on Android, such as not using the standard development
tools.
Based on my short-term research, there are already several python engines already in the Play store for Android. I'm not sure they have all the required modules, but the point is that there are already several tools available. Early thoughts are to write a native Android app for the GUI, with callouts to python scripts to do the real work, including talking to the phone. Based on my limited info on the structure of Chirp, I think this may be a feasible approach, which could (should) lead to comparable radio/driver support to the regular version.
>The app [USB-Serial port driver] is free, but he sells the use of the library that makes it possible, right?
You may be right. In the meantime, I have found several other serial port implementations, including Prolific themselves, as well as certain versions of Android. So there are options, subject to significantly more research. Very much hardware dependent...I sense some cable shopping coming up if this moves forward. I admit I would target those devices I have access to first: Nexus, Moto X, Samsung Stratosphere and Samsung S4. More variety might be helpful.
> Bluetooth is the only interface I can see being popular with Chirp for Android.
Well, I can't say I disagree, however the price point for bluetooth dongle vs a serial cable + adapter for micro may shift the demand somewhat. Personally, I am more willing to spend $10 for a USB adapter than $85 for a BT adapter on the chance that it might work. I have concerns about the reliability of serial communications across BT. A good place to explore - but that's more of a stretch, since Chirp doesn't do that today, right? (or maybe that's the killer feature??)
> #4: Is this list the right place to continue discussions?
>If this gains traction it may be worth creating a dedicated list.
I hope it does...I'm not able to do all the work required!