How can I tell if someone has an earlier version of the app in the latest version

Solar2D General Questions/Discussion
#1

So I finally got an app made and it’s in the app store. The person I made the app for wanted a “light” version with minimal features that would lead them to purchase the main app. I did this only to miss the fine print when submitting that Apple no longer allows “light” versions.

Apple’s suggestion was to make the next version of the app free with minimal features and then make it an in-app purchase to unlock the rest of the features. Problem is, if I do this, how do I tell the app that someone has the full original (1.0) version that they’re already good to go and don’t need to pay to unlock the features when they upgrade to the next version (1.1)? [import]uid: 17341 topic_id: 17557 reply_id: 317557[/import]

#2

Good problem.

Do you have any thing saved in the system.DocumentsDirectory?

Lets say you do and its a file called “settings.txt”.

When you upgrade, that file should be there. Have 1.1 use a different filename, then try and open the older settings.txt. If that file exists, you know they are an older version. There is a drawback that if they delete the app, the Documents directory is also deleted and you’ve lost track of that.
I know Apple is discouraging lite versions, but I thought they were still accepting them. I understand why they want to stop the practice because it makes the app store a pretty polluted place. But I think it puts an undue burden on the app developer to keep track of what has been purchased. [import]uid: 19626 topic_id: 17557 reply_id: 66741[/import]

#3

Unfortunately, no, I don’t have anything saved out in the 1st version. I could make a new paid version that saves a file, and then the 3rd version becomes the in-app purchase version, but if they don’t upgrade the app to the 2nd version before getting the 3rd, then I’m still screwed and have unhappy customers.

Thx for your input, but I’m not sure I feel comfortable with the two flaws you and I bring up with that particular solution. I gotta think there’s something more solid.

Any other ideas? [import]uid: 17341 topic_id: 17557 reply_id: 66749[/import]

#4

I have a setting file that includes the version number of my app. If you have a published app that does not do this, the only workaround I can think of is get this value from a new version and the value returning nil is an older version. Also if you happened to change any settings in the config files - check to see changes are present to guestimate the version of your app. Was there something to indicate a Lite version?

Just donned on me, wouldn’t the new version have the in-app purchase logic and the old version not?

Agree with what Apple suggested, post a new version with some find of improvement to induct download with the new version that has in0app purchasing.
-David [import]uid: 96411 topic_id: 17557 reply_id: 66757[/import]

#5

Perhaps I’m misunderstanding, but to my knowledge, when they upgrade the app to version 1.1 with in-app purchases, the original version gets stomped. The only thing that would’ve remained is in the documents directory had I saved anything, which I hadn’t. So if there is no file in that directory, I will have no way to tell if they had the first version, or just installed version 1.1 for the first time, right? [import]uid: 17341 topic_id: 17557 reply_id: 66776[/import]

#6

I don’t know if bumping a thread is taboo but I really need to solve this problem. Any other suggestions? Corona devs have any ideas? [import]uid: 17341 topic_id: 17557 reply_id: 66878[/import]

#7

Unfortunately no, without having saved some information you could access there’s no clear way of knowing what version is installed.

Sorry :frowning:

Peach [import]uid: 52491 topic_id: 17557 reply_id: 66895[/import]

#8

PS - The idea of a mid-version in between the two would solve the problem as irritating as that is; people who have left the game on their phones and are interested will usually update. It’s not perfect, I know, but it’s the most logical step forward. [import]uid: 52491 topic_id: 17557 reply_id: 66896[/import]

#9

Hehe, yeah, I had a feeling there wasn’t a really solid solution. I’ll definitely present the mid-version idea to the guy I’m developing for and see what he thinks. Thx for your help! :smiley: [import]uid: 17341 topic_id: 17557 reply_id: 66899[/import]

#10

Sorry there’s no really easy way to do it, I hate it when I can’t just say “Ooooh, do this!” - I guess it’s one of those things you learn after the first time then implement with great paranoia in every future app :wink:

Peach :slight_smile: [import]uid: 52491 topic_id: 17557 reply_id: 66946[/import]

#11

Haha…exactly! Luckily I was able to convince him that the best route in this case is to just leave the app as the full paid version and instead to just make a video showing off the interface and link it in the app description. That way we have a little more control on how the interface is perceived rather than let them muddle around my horrible programming. :stuck_out_tongue: [import]uid: 17341 topic_id: 17557 reply_id: 66987[/import]

#12

I’m sure your programming isn’t horrible but in any case I’m very pleased you were able to solve it without tearing your hair out :slight_smile: [import]uid: 52491 topic_id: 17557 reply_id: 67012[/import]