I'm not sure how well this metric works for Supercell and Clash of Clans. I sometimes play that game, and I can tell you that during the Superbowl, there was an in-app notification sent to all it's players to watch the youtube ad, which greatly increases the number of views of the ad beyond what the other company ads could do.
If you're looking for someone that provides the database component with the ability to upgrade to moving your entire stack to the cloud, Catalyze has both BaaS and PaaS offerings.
I think HIPAA-BaaS are great products to get storing PHI (Protected Health Information) immediately. I'm working with companies in health tech right now that are working with hospitals, but not storing patient data. BaaS, from startups like Catalyze/TrueVault/Medable, provide a quick and easy way to get started on that path and determine if it's a good long-term strategy for your company. But, once you're dealing with enough patient data crunching, the rest of your application stack will really need to be secure. That's where PaaS products like Catalyze/Aptible come in.
TrueVault is one piece of a HIPAA-compliant solution. We're providing complete end-to-end compliance. We're able to do this by:
1. Providing an end-to-end PaaS that supports all app services and databases that a customer needs to run.
2. Providing a compliance management dashboard, where customers can track their compliance status and maintain all the documentation they'd need to show to an auditor, or a customer concerned with their compliance status. Because we manage the entirety of a customer's technical operations, most of this documentation can be generated with minimal input from the customer.
For any that are interested, Couchbase Mobile is essentially, in its current form, a NoSQL database in SQLite. They might port to ForestDB in the future though, but that's an implementation detail.
No, comparison of text rather than comparison of ASTs is is better for that purpose. There are many good reasons for ASTs to be equivalent and few good reasons for text to match.
I started using NS_ENUM, but I noticed that if I used it in a header file, if I tried to make a property or variable of the enum type: @property (assign) EnumType, it would require this to prefaced with enum, i.e. @property (assign) enum EnumType.
If you just type typedef enum {...} EnumType, you could write @property (assign) EnumType. I prefer this format in my source code, so I quit using NS_ENUM.
I'm not seeing the same behavior. Just whipped up a test project and I'm able to define an enum with the macro and import it into a view controller which declares a property of that type.
What your describing would suggest that perhaps you left out the 'typedef' before calling the macro.
