I have a comprehension question. I have an Android project in which there are two modules. One is a mobile application and the other is a wearable application. Both apps communicate with each other when they are running. Now I want to upload both apps to the Google Playstore, the mobile app can run alone the wearable app cannot. Since both have the same package name I can't publish them separately. How to proceed in such a case? I have the same problem with Firebase App Distribution.
Related
We have successfully configured enterprise-owned Zebra TC57 android handheld devices to be managed via Microsoft Intune for mobile device management. We are currently using the Managed Google Play store for app distribution, and it generally works well.
But the current week or longer review time, even for the "open beta" channel, is hampering our ability to react to quickly changing needs or identified defects. While we could look at "closed testing" and "internal testing" tracks, but those don't play well with our Azure-based logins, and doesn't work around the week-long review cycle.
Based on these Microsoft MDM Docs, it seems like an Android "line-of-business" app would work well, since we can immediately distribute the APK files via the Intune "Company Portal" app. However, I've hit a major hangup with the Intune "Company Portal" app.
It is simply not visible as an icon / app to launch on the devices. I can verify via Settings => Apps that "Company Portal" is installed, but there is no "Open" button there, or via the managed Play Store. I simply cannot launch the Company Portal app in order to install our in-house Line-of-Business apps.
Why is the Company Portal app missing on our devices? How can I install it, or launch Android line-of-business apps on our Intune managed enterprise devices?
I am new to firebase and android development, therefore, I have not totally understood how it works. I want to know if after adding project to firebase, does it mean the app is launched and will be accessible by anyone who have android or how do I tell someone to try the app when it has not been uploaded to playstore?
You are misunderstanding Firebase with Play store console. Firebase is a BaaS (backend-as-a-Service). In simple language Firebase is platform which allow to build web and mobile applications without server side programming language.
Adding your android project to firebase have nothing to do with publishing app. It will not publish your app.
Play store console is what that is used to publish android apps.
What is Firebase?
In a simple way, firebase as a server and many more log details related to your app and user behavior. It's a complete package to monitor app, users and many more. It will also give you scope to build app without having your own server and also no need of any language.
I want to know if after adding project to firebase, does it mean the app is launched
No adding project does not mean your app has been published or launched, but you can see crashes, save data, authenticate and can use available features in firebase.
and will be accessible by anyone
What you want to make accessible? If it is app, then it will be only accessible to users when you publish app in play store in production. There are some other options such as alpha, beta, internal test - each of these have some own functionality. Here you can add users email ids as tester and invite them to test or about your app. When you have not published an APK in production mood it won't be visible publicly.
how do I tell someone to try the app when it has not been uploaded to playstore
After adding firebase project nothing mean to release/publish your app. Publishing in play store does mean that. Here I will suggest you upload your app APK in play store ALPHA/BETA/INTERNAL test release mood then add/invite people to test your app.
I am trying to test a Facebook Ads Management application, for advertising for mobile apps specifically. I don't have a real mobile app but need a mobile app registered on facebook and in ios and android app stores in order to reference its facebook app id when testing ad creation. Is there a way to have a mobile app like this, just for testing purposes?
I registered a MobileTest app on Facebook, but I don't have a mobile app in the stores for the Facebook app to point to.
if you are just testing you can use any other apps available on app store (google play or ios). If you are just checking the functionality or your Code then its a good option. We also don't have any mobile app so we used other play store apps to publish ads (didn't run those ads). Use any app which has fewer downloads.
I'm working on SDK for Android app developers.
My idea is to provide interface to app developers and have implementation on Service side.
I want to deploy the service as standalone through Google Play.
Is it possible to deploy app to Google Play that contains only service (no activity)?
From what I understand this is perfectly fine, an app doesn't need to have a main intent action, such as live wallpapers etc.
I remember reading about the Account Sync system in android and that actually encourage you to create a separate APK for your service if it's going to be used by multiple apps rather than deploying the same service into multiple APKs
I uploaded my signed app to the android market, I made some in app contents that I've published (but not the app).
Now I trying to purchase my own products on a real device: do I need to test with the same signed .apk I uploaded to the market? Or a "normal" one I can launch with Eclipse?
Cause when I launch my app with Eclipse and send a requestPurchase(), a pop up tells me that this app version is not ready for market purchase...
You do not need to publish your application to perform end-to-end testing with real product IDs; you only need to upload your application as a draft application. However, you must sign your application with your release key before you upload it as a draft application. Also, the version number of the uploaded application must match the version number of the application you load to your device for testing.
And as it's write on google's doc, the version number of the app on the market and of the app on the device are the same :/
You need to use a signed APK, the same one you uploaded to the app market.
You also need to use a different gmail account to your developer account to access the market.
There's a good tutorial here: Simple In App Billing with some alternative explanations
The testing developer guide is pretty thorough: Testing Billing Statically
You just need to sign the apk (in Eclipse : Android Tools -> Export Signed Application Package...) and reinstall it on the device (with the device attached to USB : adb install _YOUR_APK_).
There's also a way to test your app on the emulator with your own products before going to the real money : android test billing library.
This library is the In-App billing implementation for the emulator, which was tested in the application Horer horaires de RER.