AppOwlDev,
+1 +1 +1
I am with you on the wifi, local connection feature. There may already be something like that, I don;t know of, I haven’t had time to keep up on all the sdk updates. I cringe at having to use GC and GPGS. I am leaning strongly toward CoroniumGS (in alpha) for cross platform multi-player.
Naomi
Thanks for your input!
You may want to check out the CoroniumGS by Develephant. In alpha at this point. Of course it will require server cost.
I do wonder wether (even though Rob makes excellent points about support and server cost long term), that there might be a solution.
I am thinking if a developer wanting/needing to use a server based multi player setup, could setup in-app-purchase as a ‘consumable’ (not subscription) for say .99 cents to enable multi-player feature. Once purchased it would set a flag on your server which allows that user to use multiplayer feature for lets say 3 months. It expires after 3 months and then the user can ‘purchase again the consumable’ for another 3 months of multi-player feature. Not really a subscription, but acting like a subscription, not some ‘auto-renewable’ type.
I think the possible strength of this solution is, if there is activity and use of the server, the cost are more then covered with the in-app-purchase. You could possibly update that cost with a app update if 99 cents fails to cover the cost. Then, if it seems in-effective, or for some reason you no longer want to bother/support that feature, possibly post a notice to the users that ‘3 months from then’ the multi-player will no longer be an available feature. The still get the product that they paid for till it expires.
If the user buys the app (or gets it free) and understands when buying the multiplayer feature, that their .99cents(or whatever you need to charge to be profitable) will last for 3 months… they are not charged for something they are not getting. If the initial cost of the app was a small reasonable price, with notice that multi-player was additional cost thru in-app-purchase, I think reasonable users will accept that practice and be understanding.
I do think it important to follow ethical business practices, and in being honest to the users what they are paying for. Users should understand app developers, who have made every reasonable effort to provide a good product for a fair price, cannot be expected to carry on an expense that is cost prohibitive, and understand if a developer needs to drop the feature(with proper notice).
If it is deemed to be a bad business practice or un-ethical, I would not do it. I personally, feel it is open/honest pricing, and if in anyway it would be unethical I would not consider it.
Bob