I just finished making an android app and i want to upload it to my website so users can download it. The problem is that i don't want them to be able to share the application, so in order to install the app they must purchase the app and get a key from me.
Is it possible? If it's not, is there any other way for making sure that only users who purchase the app can use it?
BTW, the app doesn't have any web service or online features.
Related
I have an angular/ionic website that has registration, login, and dashboard pages. I want to build an android & ios app with the same code base.
When users download the app from the play store, if I add a new page/make a change to the existing page I have to submit the app for review, and then it will show the option for the update. Also, the user may not update the app. I want to show the latest changes to users as soon as I am ready with the update.
To achieve this I have followed the below steps:
1.I have built and deployed a web app(without native code). Let's call it xyz.com
2.I created a new ionic project for the APK file. I have placed an iframe with src=xyz.com
When I take the APK build of a new project, because of the iframe tag I can see the complete web app loaded. Whenever I make changes to the main web app project, after deploying to xyz.com just reopening the mobile app I can see the latest changes.
3.I have to read OTP during user login. So, after validation of user credentials in the web app, the next step is to enter the OTP. Now I have sent the event from the web app to the parent window(mobile app) like this:
window.parent.postMessage('ReadSMS','*')
In the mobile app, I listened to events from the website loaded in iframe like this:
window.addEventListener('message', handleMessage, false);
function handleMessage(event) {
if(event.data === 'ReadSMS'){
// Start native plugin cordova-plugin-sms-receive to read incoming sms
// After reading the SMS it is sent to the web app(in iframe)
myIframe.contentWindow.postMessage('SMSResult', '*',{OTP:otpfromsms});
}
}
In the web app, I listen to the events sent from the mobile app and auto-populate the OTP in the input box.
With the above iframe approach, users can use the new pages/bug fixes without updating the mobile app from the play store.
Since I use very less native plugins and they are not changed frequently. If I make any native code changes, then users have to update the app from play store, I am ok with that.
We have a tool called Ionic Appflow which has Live Update feature lets you update the UI and business logic of your app remotely, in real-time. Push HTML, JS, and CSS updates directly to your users without going through the app store to instantly fix bugs and ship new features.
The ionic Appflows is a paid tool and we can't afford it. However, I'm able to achieve live update feature and native functionality with just iframe and window message events.
Is there any disadvantage in the approach I have taken? Will, there be a problem while getting approval for listing my mobile app in the android play store and ios app store?
Can somebody please tell me the cons of the approach I have followed.
Thank You
Since a few days, users of my android mobile application are getting a warning, because the app is using sensitive data.
My app requests the daily steps count from fitnessAPI to display it.
I have read that I should go through the verification process of the oauth screen.
But I do not really know what data I should put in it. It seems rather "web" oriented, because it asks me a application homepage link, and application privacy policy link.
I do not know what I should put in these fields for a mobile app.
Should I put a link to the google play store page of the application?
Or a link to my website that shows my work?
You need to have a registered domain to host these files
Preparing for verification
I am making an android application.To use my application user has to first create an account on a web server.He/She will be provided user id and password while creating Account on that web server.After that when he/she try to install my apk from Google play or from SD card,he/she will be asked to provide that user id and password that is given from that web server.If he/she enters correct user id and password then only my apk will be allowed to install on user's android device else my apk will not be installed on his/her android device.How is it possible?Any help will be appreciated.
I am not sure you can accomplish exactly what you want. I have never heard anything about a protected password .apk.
A possible workaround would be to not upload your app to google play store, making the only possible way to download it through your server. There you can postergate the download of the app behing the user registration.
In addition, you can also implement some code in your android app to ask for some credentials in the first launch (obtained in the registration process), and if thery are not provided, the app doen't let the user have access to its services.
There are multiple combinations.
Hope it helps!
You usually don't protect the installation process, but the sign in instead. When user starts an app, he'll be prompted to enter credentials. What you describe doesn't make any sense. Just take a look at other apps(Whatsapp, Facebook, Gmail etc.)
How can I allow multiple users to log in via facebook SDK?
It seems that the sdk is using the local native facebook app, so the user currently logged in is who gets authorised, but I want to be able to authorise others.
Is there anyway to force it go through the web dialog view where maybe a user can log in?
I ask this as some users of my app will have a personal and work account and want to be able to access both.
Any help would be great
Checkout the SwitchUserSample that ships with the SDK.
I want to design an android app for a website
The app will be downloaded through a unique link from my server
I want each user to download the app WITH HIS USERNAME LOGGED IN ALREADY FOR HIM
Is there a way to do that with an android app?
My aim is to let my users download an app and find themselves logged in without having to do it themselves
In order for the app to be installed pre-aware of the credentials, you're going to have to have the website you're having them download the app from be wired up to compile a custom version of the package for each user.
Is it really that necessary for the user not to have to log in once and then have credentials remembered from that point on?