Do I need to create a new app in iTunes connect, for a lite version? I just want to make sure, can't find any articles on it.
If you plan on releasing a full version and a lite version that are separately downloadable from the app store, you will need to create a separate app for each in iTunes connect.
Here are two fantastic links, I used them both with success:
From Full to Lite in Under An Hour by Noel - technical one, describes Xcode project settings, targets and building
The Right Light by Trainyard's developer Matt Rix - much more content and marketing orientated, nonetheless a must read
Related
I have an app created for internal use. I have not published it on the play store, but I have to update it regularly.
Can anyone help...with which library should I use for implementing a self-upgrade system to my app. Any answer would be appreciated.
The answer is - yes,
You can upload your app to the Apple Store and Google Play but Not publish it to the public, instead, you can use internal testing
So only users that you define will be able to see or download your app in the Google Play and Apple Store
Google Play internal test https://support.google.com/googleplay/android-developer/answer/9303479?hl=en
Apple test flight https://developer.apple.com/testflight/
Yep it has some limitations, for example, Apple allows up to 10000 testers but I hope it's ok for your company, but its only way to share app internally without any issues on iOS (android allow you to download apps from anywhere, iOS don't)
The answer is - no, you can't do that - not at least the Flutter* apps. As #Abion47 said, you can publish the new APK and ask users to install it. If you app involves back-end then you can check the (client) mobile app version and display the alert if the version is below minimum version required.
On the iOS side, it is slightly more difficult. For internal use, the organisation needs to sign-up with Apple's enterprise program. You can then distribute the app internally.
*- I've seen certain apps downloads the zip (or whatever) file, and updates themselves without actually going through App update process via AppStore/Playstore. However, it is more of a web part within the particular app which gets updated. The app version as such remains same.
I have an app on the App Store. After the first version, I decided to create a free Lite version of the same app.
I've followed the instructions all over the web to create a multi-target application and I managed to install both version on my iPod.
What is the correct procedure to upload both my apps in the app store? Should I create a new app, named "Myapp Lite", and upload the binary as a completely different apps or maybe is there a way to tell Apple that those two apps are fundamentally the same?
If your lite version is a separate target, it's a separate product in iTunes and you have to do all the same steps as for the regular version.
The only alternative would be to make the lite version the only product and use in-app purchasing to upgrade to the full version.
You will need two create to app, one 'Lite' and one normal one.
yap you should create a new app, named "Myapp Lite", and upload the binary as a completely different apps. If you upload as same app it will be considered as newer version.
I have read on an article that Apple is applying a policy by which an app can't promote selling another apps, but i dont know the exact details of this. What about a DEMO version that haves a link to the store for the full version? can this still be done?.
If anyone haves more precise information on the subject i'll appreciate it.
You are just not allowed to offer services (in app currency or similar) for app downloads.
You won't have a problem with a link to the pro version in a lite version.
You won't have a problem with a "My App Store" link that shows all your apps either.
Don't reward your users for downloading other apps and you should be good.
I am developing a messaging app. It uses an SQLite database to store the user's registration. It also uses push notifications. Right now I am using a development push notification certificate.
My client now wants a "Lite" version to be built, and I am not sure how to go about it. I have read several articles on Stack Overflow and elsewhere. I am confused by all the versions I have read online.
Can anybody suggest to me what to do, specific to my situation? I don't want to lose the registration data in the database while updating from Lite to Paid version.
One more question: when someone downloads a paid version of an app, will it install as a different app or will it overwrite the existing Lite version? I am guessing it depends whether you are using a separate app ID or the same one, but I am not sure.
Please help.
Thanks.
To your first question, what I do is just create a second target in my Xcode project. One for the Lite version and one for the paid version. Then I create a preprocessor macro for the Lite version in the Xcode build settings for the Lite target. Usually I just do LITE=1. Then in the code when I want to do something different for the Lite version, you can just do
#ifdef LITE
//lite version
#else
//paid version
#endif
And for your second question, the paid version will not overwrite the Lite version. It will be installed as a different app.
EDIT: You should consider having just one free version and providing the "paid" features via an In-App purchase. This would allow the user's preferences to migrate over from the Lite to paid version since it would actually be the same app.
I want to create two version apps: lite and pro.
I look through purchase in app guide , but it is not allowed to change the lite version code to add functionality. you can just pop up an store UI to link the user to pro version, right?
But in this way, we can do it ourself, we copy the link of pro version in the appstore ,then pop up a dialog guide the user to app store?
I know that purchase in app can download new resource to the app,I may miss something about adding new function to the app?
thanks for your guys!
What programming language is this in? I don't have an 'app store' structure in my language...
As far as I understand, "in app purchases" on iPhone apps are not meant to download new code, but rather to unlock new features in your app. By the way, the iPhone OS does not allow applications to dynamically link and execute code at runtime (security reasons) that is why your application must be shipped with all the features inside, and the "in app purchase" feature will allow you to unlock features paid by the user.
You can, however, enable your application to access new data (for example a new URL or another embedded database) but not new binary code (like plugins or extensions). This new data might unlock more features, after the payment is approved by the App Store.
Given that now you can add "in app purchase" in free apps (this wasn't possible a couple of months ago), you can release a free "lite app" which can be upgraded with options later on. Which defeats the purpose of having a separate lite app with a link to the paying "pro app".
I hope this answer helps you!