
How To Rock Mobile App Localization
Posted on September 30th, 2015
Make no mistake, the mobile explosion and migration from the web to apps is not just an American or even Western phenomenon.
Want more ASO Tips?
Contact UsMake no mistake, the mobile explosion and migration from the web to apps is not just an American or even Western phenomenon.
Just when marketers caught up with websites, social media disrupted the digital marketing landscape. While providing new ways to reach customers, navigating how businesses should use Facebook, Twitter and LinkedIn (not to mention Instagram and Pinterest and many more) continues to be a challenge. Now mobile has arrived to the scene, faster and bigger than any technology before it. The only reason they are called “mobile devices” or “smart phones” is because “personal computers” was already taken. It is not just the use of mobile devices that is the story that is changing everything, but the use of mobile apps. To add to the intrigue, mobile devices and apps are not just used while waiting in lines or “on the go”, but while sitting on the couch as the second screen. Like social media and the rise of the web before it, the rapid transition to mobile and mobile apps provides opportunities and challenges.
Congrats - you have a mobile app ready for submitting to Google Play! If you don't have a Google Play Publisher account, which provides access to the developer console, you are going to want to sign up for that here.
The best pace to start with estimating the costs of developing a mobile app is in understanding there is a big range. Functionality, design, service level and development language all impact the final costs of developing a mobile app, and that’s before marketing costs are included. With cars or houses, function and design is often easier to conceptualize for the non-developer. We expect the engine, the suspension, the design, the interior and the add-ons all to impact costs and have some idea of how. For software, specifically mobile apps, it can be hard to know if a specific feature or function is even possible, let alone how much it would cost to add. Let’s remove some of the mystery related to the costs of developing mobile apps by looking at the variables that impact the cost of developing a mobile app the most.
The world of apps has boomed since it began to form in 2008. App stores like Google Play or Apple’s own App Store have become saturated with apps, making competition fierce and standing out an even harder task. As a company, we get asked questions ranging from the beginning of the app development cycle, all the way through an app’s marketing life. With all the right tools, you can get your app from concept to download.
As the dust settles from the wild adoption of mobile devices over the last few years, there appears to be some clear winners and losers. The businesses of Blackberry and Nokia were negatively affected, and attempts to enter the device market by Amazon and Windows are largely failures. But instead of having one clear winner (as is often the case in technology), we have two. Both Apple and their iOS mobile operating system, and Google's Android appear to have carved out significant space in this new mobile world. But the segmentation looks like this: 
To create an app that makes money, mobile app publishers and developers need a validated idea, and a plan for acquiring and monetizing users. We have covered user acquisition in various posts, from optimizing an app store listing to paid Facebook campaigns. Here, we will explore common monetization methods for mobile apps and trends likely to impact how apps make money.
After some limited volatility in the App Store in mid-July, there were lots of theories as to not only what happened, but if there were some longer-term implications to Apple’s App Store ranking algorithm. The primary claims was that Apple was penalizing apps with long app titles.
Is it better to try and rank for 1 or 2 targeted keywords, or to rank for 100's?
Help!
A common request from our mobile marketing, agency and app publishing clients is for a forecasted app store rank and/or expected install volume increase (or decrease) metric. This desire for data is understandable and frequent enough that I felt a short post here could add some insight into how we view providing these types of metrics. We have opted against forecasting the increase of rank or install volume inside our software. There were several reasons for this decision, but the most important one was that this kind of representation is almost always disingenuous.
"I have an idea for an app" - this statement