Looks like Google is cracking down on updates outside Google Play. http://www.cultofandroid.com/26707/google-bans-android-app-updates-outside-of-google-play/ I know most of us will do updates via the control panel and then make live. Sounds like this is a fine line. -Shane

Interesting stuff.

Wow.. that IS a fine line. Hope bt can clarify this as cp updates are integral to the bt platform.

The buzztouch binary doesn't really change when you change the bt_config. IMO this shouldn't be an issue.

I agree i doubt it would concern us. if so it would hit big companies such as espn and news outlets that rely on continuous updates and changes right?! i agree with with @nadthelvad BT doesn't allow the binary changes..

As said above, correct. From the horses mouth, so to speak. Apple's always prevented this. The key is the "binary" part. You can't push updated binaries (compiled code). We send data to previously compiled apk's, not new apk's.

Hope you're right. I mean, with bt although the binary doesn't change, it's possible to create a whole new app. My worry is that google shoot first and don't bother asking questions later!

I hear you buddy. Luckily we all trust our tech co's never to do anything evil or in haste! Ha!

True.. Google doesn't have anytime for excuses lol.. Definitely learned my lessons years back haha Lets hope all is true.. or whats 5 more minutes to upload a new apk? :) Patience is a virtue, right?!

I think it all depends on how picky Google wants to be. I'll continue to do the same in the time being. -Shane

Things will continue to continue on. As said above, it's the binary. Just my $0.02 Cheers! -- Smug

Food for thought. Facts: --Google is for sure referring to BINARY updates, not content updates. --Apple has held this position from the start. --Several outfits, not just Facebook have begun inching in on Android (it's open source) with Binary updates outside the Play store. --Hundreds of thousands of apps rely 100% on CONTENT updates. --BT does not do anything with your binary after you compile it. Nobody does. It remains the same. It's content changes, not it's Java source code. With that said, and those facts understood, we must also understand this "app" concept and the idea that you can "create a new app" by changing the content of the config.txt file. This is ONLY TRUE in a non-technical sense. Technically, you are NOT creating a new "app." because you're not re-compiling. For sure most folks will think you're creating a new app (lots of folks in our audience don't fully understand these minor semantics and words we use to describe technology) but the fact it, you're not. Without going on-and-on about this....this new position announced by Google doesn't affect that idea. But.. EXISTING POLICIES IN GOOGLE'S TERMS AND APPLE'S TERMS ALREADY DO. The fact is, we've never understood, or advocated that anyone fundamentally change an app's behavior, or overall design or functionality after distributing it to end users. Sure, you could do this but it's just not a good idea. And, it goes against Google and Apple developer terms anyway. It always has, this isn't anything new. Make good apps, update content as needed to fulfill the general purpose of the app and all will be well. Make sneaky apps, update them dramatically with a very different motive each time and you'll run into trouble - as you should :-)