I have 2 problems with integration of shortcut's capabilities (but the shortcuts themselves work properly) in Android:
Assistant doesn't see my debug application on phrase "Open myappname"
Assistant doesn't see any shortcut capability which I added to the dynamic shortcuts.
If I clearly understand it will be able after publication at the Google Play, but my application is not designed for this store. How can I force Google Assistant to understand my queries?
For app actions, your application needs to be uploaded to the Google Play Store. That being said, it doesn't need to be published to everyone. At the very least you can create an internal or closed test release.
Related
Looking at the documentation here.
On Google Play, when you create an open beta:
Users can find your open test via search on Google Play. Once users find your listing, they can install your app normally.
This is not the behavior we want for our open beta. We don't want the app to be discoverable by searching the store. We only want the app only to be accessible by a link. This is possible using iOS's TestFlight platform.
We don't want a closed alpha because we don't want to manage a list of emails. We'd like anyone with the link to have access.
Is there any way to make a "link-only" open beta in Google Play?
You actually can't. However, you might be interested in creating an alpha test, instead of using mails, using a Google Group.
Reference in Closed test: manage testers with Google Groups.
I have developed a game using Unity and I have used Google Play Games in it. It works good for testers and also for public users when I publish it on Google Play Games. The problem is I want to publish it on a local app store (and not Google Play Games) and it does not work this way! Is there any trick about it?
Yes, this is possible. It does even work if you sell your app through google play and on another platform. But the device needs to have the google play games app installed, so it does not work on Amazon devices.
Let’s assume your app is called “TheGame”.
Go to the Google Play Developer Console to “All application”:
Add another app name call it “TheGame (DRM-free)”
Create an empty APK that signed with a keystore and a different bundle identifier (if you already sell it on Google Play)
Upload the APK to alpha or beta testing, but not production.
Complete the Store Listing and Content Rating
Set pricing to free
Publish your app. (no worries it will not appear on Google Play)
Then go Google Play Developer Console to "Game Services:
If you not already have that add new game
Link your app “TheGame (DRM-free)” to you game services under “linked apps”
Make sure you set the “Enable anti-piracy” option to “OFF”
Publish your changes
This work with achievement, leaderboards and multiplayer.
The users don’t need to be testers anymore.
Also multiplayer between your DRM-free and your Google Play app is possible.
You may want to check this document- Alternative Distribution Options
As an open platform, Android offers choice. You can distribute your Android apps to users in any way you want, using any distribution approach or combination of approaches that meets your needs. From publishing in an app marketplace to serving your apps from a web site or emailing them directly users, you’re never locked into any particular distribution platform.
Distributing Through an App Marketplace
Distributing Your Apps by Email
Distributing Through a Website
User Opt-In for Apps from Unknown Sources
Android protects users from inadvertent download and install of apps from locations other than Google Play (which is trusted). It blocks such installs until the user opts-in Unknown sources in Settings > Security, shown in image below. Users need to make this configuration change before they download your apps to their devices.
Users must enable the Unknown sources setting before they can install apps not downloaded from Google Play.
Note that some network providers don’t allow users to install applications from unknown sources.
Also you can check this SO question about : What is the fall back plan for devices without Google Play Services, this may add information to ensure your app should run.
Hope it helps!
Google states the following regrading there open beta service "For early access apps (new apps that haven't been published to production): Users can find your beta version via search on the Play Store. Once users find your listing, they can install your app normally."
Source
I published my app to open beta last night but when I log out of any google related service and search on the play store my app is not visible. It is titled Fractal Plus. The opt-in URL seems to work fine.
https://play.google.com/apps/testing/biz.MagiTek.FractalPlus
Anyone know how I can fix this?
The 'Early Access' feature on the Play Store may still be being rolled out to users. On one of my devices the play store does not have an Early Access section yet and I cannot see your app via a search, however on another device I am able to see your app in the play store search results.
My company has a handheld application published and in the last release we've added an Android Wear app to it. When the users download and install it, it works on the Android Wear devices too, but it doesn't appear under Android Wear category.
Should I add a flag to it? Is something I missed on Google Play Developer Console?
Here's where it is on the Play dev console. On the Pricing & Distribution page, under the country list and Ads section.
A couple of additional notes, though:
Your app needs to be approved before it'll appear in the category. I've had an app rejected because it didn't deal with a "flat tire" display correctly, for example. I believe this is the offical list of criteria.
Like most of the dev console, changes don't go live immediately. They take some time to filter out through the production Play store.
I'm building an Android app which for various reasons cannot be listed publicly on the Google Play store.
I have found information about the Google Play Private Channel but if I understand it correctly, this can only be used when all your users are within a Google Apps domain (which mine are not).
Are there any similar methods that I could use to deploy my app (and get the benefit of easy installation for users, an updating mechanism etc.), or is my only option to publish an APK file manually?
From what I can tell, manually publishing APK files is the only choice, but this seems strange to me since my situation must be common for "private" business applications.
In particular, I am concerned that it would look unprofessional to have to guide users through the process of turning on the "Allow installation of apps from unknown sources" setting.
Any advice welcome, thanks!
I would just deploy your app using Google Play "Beta testing and staged rollout":
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
Your users have to join a Google Group or Google + community that you create so you can limit you audience and make the app non-public on Google Play but still allows your non-public users to update the app via Google Play instead of manual APK installation.
The only downside is that the members of the Google Group or Google + community will only be as private as their Google account provides. So, app users are known to each other but your app will not be public on Google Play.
Can you not use BETA or ALPHA pushes