{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"required","results":{"codes":[]},"params":[]},"next":{"description":"","pages":[]},"title":"In-app Purchases","type":"basic","slug":"in-app-purchases","excerpt":"","body":"If you want to sell functionality of your application partially (like Mac App Store In-App Purchase), we can suggest you the following workaround.\n\n1.    Add and configure your main application in DevMate as usual.\n2.    Inside your application create as many sub-applications as you want functionality parts to be sold separately.\n3.    Create the Applications in DevMate with the same bundle IDs as the newly created sub-applications.\n4.    Integrate DevMateKit and Kevlar to those applications (no need to copy DevMateKit to sub-applications bundle, just modify *‘Runpath Search Paths’* (`LD_RUNPATH_SEARCH_PATHS`) build setting for them to look for DevMateKit framework in parent bundle);\n5.    In the main app implement the following behavior:\n\n  *         when the paid functionality is requested the corresponding sub-application should be asked if it is activated;\n  *         if requested functionality is not activated, then initiate the purchase (either via in-app store or through the web-interface);\n  *         after the purchase will be done, the functionality will be unlocked.","updates":[],"order":1,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"591f17b321d2ff0f00cf5a67","user":"547cd6ac78fd57080023ca99","parentDoc":null,"createdAt":"2015-03-27T13:29:13.142Z","category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Tips and Tricks","slug":"tips-and-tricks","order":7,"from_sync":false,"reference":false,"_id":"591f17af21d2ff0f00cf5a47","project":"547cd7662eaee50800ed1089","__v":0,"version":"591f17ae21d2ff0f00cf5a3f","createdAt":"2015-03-27T13:16:34.125Z"},"version":{"version":"1.0.1","version_clean":"1.0.1","codename":"","is_stable":true,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["591f17af21d2ff0f00cf5a40","591f17af21d2ff0f00cf5a41","591f17af21d2ff0f00cf5a42","591f17af21d2ff0f00cf5a43","591f17af21d2ff0f00cf5a44","591f17af21d2ff0f00cf5a45","591f17af21d2ff0f00cf5a46","591f17af21d2ff0f00cf5a47","591f17af21d2ff0f00cf5a48"],"_id":"591f17ae21d2ff0f00cf5a3f","createdAt":"2017-05-19T16:05:02.775Z","__v":1,"project":"547cd7662eaee50800ed1089","releaseDate":"2017-05-19T16:05:02.775Z"},"project":"547cd7662eaee50800ed1089","githubsync":"","__v":0}
If you want to sell functionality of your application partially (like Mac App Store In-App Purchase), we can suggest you the following workaround. 1. Add and configure your main application in DevMate as usual. 2. Inside your application create as many sub-applications as you want functionality parts to be sold separately. 3. Create the Applications in DevMate with the same bundle IDs as the newly created sub-applications. 4. Integrate DevMateKit and Kevlar to those applications (no need to copy DevMateKit to sub-applications bundle, just modify *‘Runpath Search Paths’* (`LD_RUNPATH_SEARCH_PATHS`) build setting for them to look for DevMateKit framework in parent bundle); 5. In the main app implement the following behavior: * when the paid functionality is requested the corresponding sub-application should be asked if it is activated; * if requested functionality is not activated, then initiate the purchase (either via in-app store or through the web-interface); * after the purchase will be done, the functionality will be unlocked.