Mobile analytics is about understanding your mobile customers. It seems that every day a new analytics vendor releases a “must have” analytics product for your app. Instead of trying or adopting every new product, I recommend mobile app publishers focus on a “mobile analytics maturity model” - a model that promotes building up your analytics capabilities along different axes.
This blog post describes the three levels of analytics in our maturity model, who in the organization needs to be involved, and which analytics vendors can help you get the metrics to enable better decision making for your apps to support your users.
In a recent blog post, @kevinswiber covered the importance of building mashup-friendly APIs. Another pattern that's important to the success of your API is comprehensive queries.
Crafting a delightful API and creating an enterprise database both require knowledge, talent, and a subtle design touch. Oftentimes, a database system is made for a specific business application. It might show which territories belong to a specific agent or which stocks belong to a certain mutual fund, or all the products purchased by a specific customer.
In large companies with big systems of record that have been around for decades, queries often go one way but don't work the other way around. What do we mean by that?
As enterprises adjust to the new reality of business having moved beyond their core and legacy systems of record - to millions of mobile devices and social networks at the edge of the enterprise, to new distribution channels in the shape of apps which are often built by third party or partner developers - the question of end user privacy becomes increasingly important. As the app economy matures, it’s participants will have to quickly move from self governance to establishing standards or even regulation to address end-user privacy expectations.
Who is responsible for security and privacy when...
Inside nearly every company is an API Machine, a powerful engine that activates latent business value from enterprise systems and databases by plugging directly into the app economy.
Now is the time for companies to turn on the API machine. So, what's important? How do we learn from and avoid the now obvious mistakes that API pioneers have made in the past? How do we create an API initiative that maximizes impact and relevance? We'll review the key patterns for success: Easy Grab Data Handles, . . .
API facade is an important design pattern in an API designer's toolbox and a powerful tool for app developers who need to work with APIs they don't control. In this first episode of a four part series, Brian Mulloy and Santanu Dey discuss the Composition pattern and how it handles data formats, performance, security, and more to enable mash ups and service compositions.
To uncover the expectations and ratings criteria for mobile apps on smartphones and tablets, we recently conducted a Mobile App Review Survey* of over 500 American mobile app users, aged 18 and older. The survey found that fully 96% of American mobile app users say there are frustrations that would lead them to give an app a bad review, including: Freezes – 76%, Crashes – 71%, Slow responsiveness – 59%, Heavy battery usage – 55%, Too many ads – 53%.
In this stop on the API Design Tour, the Dell API Team talked about the approach that Dell takes to designing and implementing their API. Check out the video and slides for the webcast.