This project is a part of The SOOMLA Framework which is a series of open source initiatives with a joint goal to help mobile game developers do more together. SOOMLA encourages better game design, economy modeling, social engagement, and faster development.
Haven't you ever wanted an in-app purchase one liner that looks like this ?!
SOOMLA's Store Module for iOS
September 15th, 2014:
NonConsumableItem class was removed.
To create a non-consumable item in your
IStoreAssets implementation, use
June 20th, 2014: v3.4.0 presents support for "Soomla Core" (which separates some objects common to ALL SOOMLA's modules). It also removed the usage of SOOM_SEC. Getting Started has changed! see CHANGELOG.
March 31st, 2014: SoomlaStore will automatically try to fetch prices for PurchasableItems that has a purchase type of PurchaseWithMarket. The product ids that'll be found in the App Store will update the associated 'AppStoreItem' in special fields: appStorePrice, appStoreLocale, appStoreTitle, appStoreDescription.
September 29th, 2013: Server Side Verification is now implemented into ios-store. The server is a complimentary server provided by SOOMLA to help you get your in-game purchases a bit more secured. This feature is not enabled by default. In order to enable Server Side verification go to StoreConfig.m and set VERIFY_PURCHASES = YES.
Want to learn more about modelV3? Try these:
ios-store is the iOS flavor of SOOMLA's Store Module.
Check out our Wiki for more information about the project and how to use it better.
Pre baked libraries:
WE USE ARC !
Before doing anything, SOOMLA recommends that you go through Selling with In-App Purchase.
The static libs and headers you need are in the zip you downloaded from the link above.
- Set your project's "Library Search Paths" and "Header Search Paths" to that folder.
-ObjC -lSoomlaiOSStore -lSoomlaiOSCoreto the project's "Other Linker Flags".
Make sure you have the following frameworks in your application's project: Security, libsqlite3.0.dylib, StoreKit.
Initialize Soomla with a secret that you chose to encrypt the user data. (For those who came from older versions, this should be the same as the old "custom secret"):
[Soomla initializeWithSecret:@"[YOUR CUSTOM GAME SECRET HERE]"];
The secret is your encryption secret for data saved in the DB.
Create your own implementation of IStoreAssets in order to describe your specific game's assets. Initialize SoomlaStore with the class you just created:
[[SoomlaStore getInstance] initializeWithStoreAssets:[[YourStoreAssetsImplementation alloc] init]];
And that's it ! You have Storage and in-app purchasing capabilities... ALL-IN-ONE.
What's next? In App Purchasing.
When we implemented modelV3, we were thinking about ways people buy things inside apps. We figured many ways you can let your users purchase stuff in your game and we designed the new modelV3 to support 2 of them: PurchaseWithMarket and PurchaseWithVirtualItem.
PurchaseWithMarket is a PurchaseType that allows users to purchase a VirtualItem with the App Store.
PurchaseWithVirtualItem is a PurchaseType that lets your users purchase a VirtualItem with a different VirtualItem. For Example: Buying 1 Sword with 100 Gems.
In order to define the way your various virtual items (Goods, Coins ...) are purchased, you'll need to create your implementation of IStoreAsset (the same one from step 4 in the "Getting Started" above).
Here is an example:
Lets say you have a VirtualCurrencyPack you call
TEN_COINS_PACK and a VirtualCurrency you call
VirtualCurrencyPack* TEN_COINS_PACK = [[VirtualCurrencyPack alloc] initWithName:@"10 Coins" andDescription:@"A pack of 10 coins" andItemId:@"10_coins" andCurrencyAmount:10 andCurrency:COIN_CURRENCY_ITEM_ID andPurchaseType:[[PurchaseWithMarket alloc] initWithProductId:TEN_COINS_PACK_PRODUCT_ID andPrice:1.99]];
Now you can use StoreInventory to buy your new VirtualCurrencyPack:
And that's it! iOS-store knows how to contact the App Store for you and redirect the user to their purchasing system to complete the transaction. Don't forget to subscribe to events of successful or failed purchases (see Event Handling).
Storage & Meta-Data
When you initialize SoomlaStore, it automatically initializes two other classes: StorageManager and StoreInfo. StorageManager is the father of all storage related instances in your game. Use it to access the balances of virtual currencies and virtual goods (usually, using their itemIds). StoreInfo is the mother of all meta data information about your specific game. It is initialized with your implementation of
IStoreAssets and you can use it to retrieve information about your specific game.
The on-device storage is encrypted and kept in a SQLite database. SOOMLA is preparing a cloud-based storage service that will allow this SQLite to be synced to a cloud-based repository that you'll define. Stay tuned... this is just one of the goodies we prepare for you.
Give the user 10 pieces of a virtual currency with itemId "currency_coin":
[StoreInventory giveAmount:10 ofItem:@"currency_coin"];
Take 10 virtual goods with itemId "green_hat":
[StoreInventory takeAmount:10 ofItem:@"currency_coin"];
Get the current balance of a virtual good with itemId "green_hat" (here we decided to show you the 'long' way. you can also use StoreInventory):
VirtualGood* greenHat = (VirtualGood*)[[StoreInfo getInstance] virtualItemWithId:@"green_hat"]; int greenHatsBalance = [[[StorageManager getInstance] virtualGoodStorage] balanceForItem:greenHat];
If you want to protect your application from 'bad people' (and who doesn't?!), you might want to follow some guidelines:
- SOOMLA keeps the game's data in an encrypted database. In order to encrypt your data, SOOMLA generates a private key out of several parts of information. Soomla's secret (before v3.4.0 is was known as custom secret) is one of them. SOOMLA recommends that you change this value before you release your game. BE CAREFUL: You can change this value once! If you try to change it again, old data from the database will become unavailable.
SOOMLA lets you get notifications on various events and implement your own application specific behavior.
Your behavior is an addition to the default behavior implemented by SOOMLA. You don't replace SOOMLA's behavior.
In order to observe store events you need to import EventHandling.h and then you can add a notification to NSNotificationCenter:
[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(yourCustomSelector:) name:EVENT_ITEM_PURCHASED object:nil];
OR, you can observe all events with the same selector by calling:
[EventHandling observeAllEventsWithObserver:self withSelector:@selector(yourCustomSelector:)];
Our way of saying "Thanks !"
Other open-source projects that we use:
SOOMLA appreciates code contributions! You are more than welcome to extend the capabilities of SOOMLA.
Fork -> Clone -> Implement -> Add documentation -> Test -> Pull-Request.
IMPORTANT: If you would like to contribute, please follow our Documentation Guidelines. Clear, consistent comments will make our code easy to understand.
SOOMLA, Elsewhere ...
Apache License. Copyright (c) 2012-2014 SOOMLA. http://project.soom.la