{"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":"55155b2907e9252f00348881","user":"547cd6ac78fd57080023ca99","__v":0,"category":{"sync":{"isSync":false,"url":""},"pages":["55155913fd26132300e74e32","55155b2907e9252f00348881","55156a8307e9252f00348899","553a6a6a2af5f20d000fc2d2","555ca4ee15a89b0d00c1aee9","558154478625220d00429c78","55a5052a750a9a23005332be","55a62e85249a40190051d98d","55e41f711020fe0d00388a00","5609036331beb60d001b6585","5638d42668b11f0d0048c8d5"],"title":"Tips and Tricks","slug":"tips-and-tricks","order":7,"from_sync":false,"reference":false,"_id":"551558324c7c1e39003735a0","version":"547cd7662eaee50800ed108c","project":"547cd7662eaee50800ed1089","__v":11,"createdAt":"2015-03-27T13:16:34.125Z"},"version":{"version":"1.0","version_clean":"1.0.0","codename":"","is_stable":false,"is_beta":false,"is_hidden":false,"is_deprecated":true,"categories":["547cd7672eaee50800ed108d","54c8f8ae0174630d00efa874","54c8f8bd7a11f60d0022a832","54c8f8c60174630d00efa876","54c8f8f10174630d00efa877","55155826bc466623002afe83","551558324c7c1e39003735a0","56052058e266000d008971c7","57909a453b845d0e006a37d5"],"_id":"547cd7662eaee50800ed108c","createdAt":"2014-12-01T21:02:30.851Z","project":"547cd7662eaee50800ed1089","releaseDate":"2014-12-01T21:02:30.851Z","__v":9},"project":"547cd7662eaee50800ed1089","createdAt":"2015-03-27T13:29:13.142Z","githubsync":"","parentDoc":null}
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.