You missed the point. I don't want to simply cut and paste the sample (singular) app into studio and chop it about to get something working.
I want to be able to add a dependency on the JAR, stick the relevant imports at the top of my activity and write the code myself and there is no documentation that I can find that says 'here's how to talk to ANT+ on Android' apart from some pretty much uncommented, poorly documented and complex java code samples in what could charitably be called a legacy environment. It's almost 7 years (March 2015) since any updates were made to the API. Android was at version 5 Lollipop, we're currently at 12 (Snow Cone) which is seven releases since (more if you count minor releases...) and ANT haven't updated the API in all that time...
After initially posting this I realised that I didn't actually need to talk to ANT devices, the sensors I have are dual ANT/BLE so I can use BLE.
I went off to the android developer site, grepped for BLE and found the guide. 45 minutes later I was reading the data from my BLE cadence sensor. This is 45 minutes from deciding I want to try something that I've never done before and it's all due to the quality of the documentation and samples that are provided by the Android development team.
The demo code is not released for this app as some people were taking the source, rebreanding it and putting it on the play store. We hope for a higher quality app experience than that from developers and don't need a bunch of clones all over the play store.
This is a direct quote (including spelling mistakes) from Sample/README.md from the downloaded ANT+ SDK. I would argue that instead of creating that text, the ANT people should have asked themselves, why developers are just cutting pasting and rebranding rather than developing their own apps.
It could be that all developers are lazy cut and paste merchants just out there for an easy ride and want to get their name on something so they will rip the code off or it could just be that the developers couldn't quite get their heads round how all this worked and just used what they found at hand to make the best of a bad job. I'd like to think it's the latter.
ANT is losing(has lost) the battle with BLE, it may be the Betamax of wearable BUT lack of support and clear documentation and an arrogant attitude from ANT just isn't endearing developers to the project. If ANT want more takeup, they need to offer better support than they are doing otherwise developers are just going to do what I did, take the path of least resistance which is BLE.