Got really excited when I discovered this Google IO video recently. Adding YouTube features to an app easily is very attractive compared to current options (intent, iframe embed)
I was surprised that despite several months since the annoucement, there is virtually nothing out there beyond this video. The session itself didn't even cover the schedule for release.
Does anyone know where to get a jar, beta or otherwise, to play with?
Does anyone know a schedule for when this might become widely distributed?
I'm hoping someone from the YouTube API Blog and YouTube API Team can address.
We don't have anything else to share at this point--the team remains hard at work at getting this launched, but I can't provide a date. We are not distributing beta versions of the Player SDK publicly.
(Also, I'm not positive this is the sort of question that belongs on Stack Overflow--apologies to any moderators if that's the case.)
The API is now available. It works very nice.
Related
So I have used App Actions in my app for a couple of years, last week I pushed a maintenence update that has been rejected by Google. After some to and fro with Google Play support, the best I have managed to get out of them for the reason is "App Actions", and I should read the program requirements (the link they sent me has no program requirements section).
It's odd, as I have changed nothing in my app-actions area of code for a very long time, so I can only assume Google have quietly tightened some rules, and my app is no longer complaint. Unfortunately, my crystal ball is currently away for cleaning, so unable to use it, I'm hoping someone else might have some real-world specific examples of how an app may not be compliant in the area of app-actions.
Thanks.
Unfortunately, there are no straightforward rules specified by Google, so you have to go with some trial and error here to see what red flag(s) is your app raising. You can check this article to see all the potential reasons on why Google may reject your app.
An app called Bass Booster has the functionality of displaying a list of installed applications that are possibly incompatible with it.
I plan to implement in my app a similar function, which shows the list of apps that may be incompatible and the following message: "The following apps may present conflicts with XBooster. Please check them and take the necessary actions to avoid conflicts between your sound apps. "
This function would be very useful to identify installed apps that can interfere with each other and hinder the operation of all installed equalizers (including preinstalled).
But in the following link of developer policies:
https://play.google.com/intl/en/about/privacy-security-deception/deceptive-behavior/#!?zippy_activeEl=deceptive-settings#deceptive-settings
It can be read that they do not allow the following:
"Apps that encourage or incentivize users into removing or disabling
third-party apps or modifying device settings or features unless it is
part of a verifiable security service."
Does implementing the function that would show a list of apps that could be incompatible, somehow incentivize users to take the action of removing or uninstalling them?
I would like to know the opinion of the other developers about it.
I don't know how to contact the Google Play support team to ask about my question and avoid implementing a function that could cause me problems.
If this is not the right place to post this question, help me know where I should post it.
I would like to know the opinion of the other developers about it.
SO is a question and answer site - not an opinion forum. Questions like "will this violate Google Play policies" are best directed to a lawyer.
I don't know how to contact the Google Play support team to ask about my question and avoid implementing a function that could cause me problems.
Try the Android Developer Console help. Click the "?" icon in the top right, then down to "Contact Us / Need more help".
However, it's highly unlikely you'll get any good / direct answer. Google Play "support" is notoriously vague about what constitutes violations of the policy (presumably so people don't game the system / sue them).
If this is not the right place to post this question, help me know where I should post it.
Maybe try Twitter, Reddit, or some such platform where you can query the masses for their hot takes on a question.
Hope that helps!
I hope this question isn't too broad. I realize the answer to my question is "Anything, it depends on the particulars." I'm just looking for ideas here. I have a published Android app that has been in the store for years. People download it every day. Suddenly, on July 2, 2018, I start getting messages from tons of users, both new and old, saying they can't get past the startup screen, where the app does a series of checks (read-write to storage, check license, etc). I haven't changed anything in the app.
Oh, and of course it doesn't repro for me.
I asked my users for information about the device they're using, their build of Android, their physical location, and I don't see any patterns. It's all kind of devices including official Google devices, and the OS ranges from 6.0 to 8.1.0. Users are from all over the world.
Based on what users are telling me they see on the screen, it seems that the Google Play license check might be the place where things are going wrong. (However, no exceptions or error messages are shown.) Also pointing in this direction is the fact that the free apps (which have otherwise identical logic) seem to work okay.
Did Google deprecate something a licensing library starting on July 1 or something like that?
Any ideas would be greatly appreciated.
Big thanks to #MorrisonChang in the comments to my question pointing me in the right direction. I have confirmed that this was indeed a problem with the Google Play Store app, and customers who upgraded to 10.7.19 report that my apps are working properly again.
I know Apple has this API I can hit:
http://itunes.apple.com/lookup?bundleId={id}
However, for the PlayStore, I'm looking for something similar, rather than parsing the app page
https://play.google.com/store/apps/details?id={id}
and then looking for the <div> that contains itemprop="softwareVersion"
There are a few questions about this here on SO and elsewhere on the web, but they are outdated, and make reference to unofficial APIs.
There is no Official API for grabbing the App version from the Play store.
I'd be curious exactly what you would use such an API for, if you wanted to add it in a comment. There may be a better way of achieving what you want.
Edit:
For forcing an update to your app there are other recommendations. We normally recommend that you don't have "always update to the latest version in the Play store" to developers. For example, the user might want to use your app, but be in a place where they don't have much battery or wifi. Forcing them to update in such a situation is rude, it's much better to give them a week or two until a more convenient time.
If you want to do "never have a version that is more than a couple of weeks old", can I recommend Firebase Remote Config. This would let you on the server update a configuration options for your app saying "the user should have at least this version" and change the behaviour of your app accordingly. It is much more flexible at robust than polling the Play store.
Another approach can be the Support In-app updates besides Firebase Remote config.
Google has released the Support In-app updates feature in which the apps can nudge the users to update their apps without even going to the play store. If an update is available, the users will see a dialog or a full blocking screen where the UI is generated and controlled by google play.
In-app updates works only with devices running Android 5.0 (API level 21) or higher, and requires you to use Play Core library 1.5.0 or higher. After meeting these requirements, your app can support the following UX for in-app updates!
references are here and this helpful blog. Check this out, hope it will help.
did not want to revive an old thread.
OMA DRM v1 & v2 support on Android
we are trying to implement a DRM solution for video content for both streaming and offline. And have searched both high and low, these where are the few which repeats itself every time.
http://www.irdeto.com/documents/HL_CW_OMA_DRM_Android_EN_H.pdf
http://www.discretix.com/Android_Security.html
http://www.haihaisoft.com/customize_android_media_player.aspx
http://www.authentec.com/a/Production/Home.aspx
we are targeting phones & tabs
so android 3.0 can be helpful, went through the sdk docs, still couldn't make out how to use them.
also read somewhere android 2.4 (for phones) will support the DRM framework, in the meantime the market we are targeting may not upgrade to android 2.4 so soon. this requires us to find some custom implementation.
have been hitting the wall on all sides. please give your invaluable insights.
if i have missed something very obvious, correct me as well.
Security through obscurity. It's the only way that DRM can work on a device owned by someone else. Obsfucate your code and require updates to the latest version, which changes every week.
It's like putting a lock on a box, then putting the key in the lock, and hoping that no one finds the lock and key. The solution is to change the location of the lock and key every few days, so that the vast majority of users can't be bothered to find it themselves or even to get the latest "crack".
Old thread -- but you may want to look at Adobe Access as well (http://www.adobe.com/support/documentation/en/adobeaccess/). Supports Android with both streaming and offline possible.