
By Magnus Ingelsten
By Bhavya Siddappa, Technology Evangelist, Teleca Bangalore
Droidcon London 2010 – Day Two 29th Oct 2010
It was more of traditional conference the second day. Main topics were App´s, User Experience, Android development in general and a little about marketing. A great day too, read on!
Excellence in the Android User Experience: Romain Nurik from Google
Presented on how to create applications with great UX and great UI and extended his talk with Android design tips with some additional info on giving users great first impressions, and some new prototyping and asset generation tools that have become available.
Android User views: Ilicco Elia from Reuters Mobile
The App Store is not about the app, it’s about people, it’s about the edge that people believe they will get from the app. In-app purchasing is seriously lacking.
Growing the value of the application network: Christophe Francois form Orange
It was great to see Orange committing so many people and so much time to Android. Orange focusing apps: Orange TV with premium events, Connectivity & customer care, News, radio, Orange Map.
Creating Killer Location apps: Alex Housley from Rummble
Location is not a feature, it’s one element of context. Friend finders have been done to death, similarly, there will be opportunities working with existing big players in location “Where there’s a number there’s a game…”.
Android & CouchDB: Aaron Miller from CouchOne
CouchDB is a non-relational database (NoSQL) that stores JSON documents. Instead of queries, create “views” that allow fast lookup by keys. DB is highly durable. Good at multi-master replication and can easily write to any server. Its really powerful on a phone as it can sync with a server or with another phone and can have multiple DBs on net syncd to a single DB on phone.
Monetize your apps in emerging markets: by Chua Zi Yong from MoVend
He discussed the concept of marketing your apps to emerging markets. For a lot of people in emerging markets the phone is the only access to the internet, social networking, and gaming/entertainment device. He had some interesting statistics on mobile phone payments. Asia Pacific accounts for $62.8 million in mobile phone payments and the rest of the world only accounts for $45.8 million. The market for mobile app revenue is estimated at $135million for 2009 and at $4 billion for 2010.
Market is extremely fragmented; An Android market does not exist in certain countries. Tip: Try to get your application pre-loaded onto a phone and target what specific users like.
Android has a “dude” problem: by Belinda Parmar from Lady Geek TV
When surveyed only 5% of women said Android for their next phone, 57% said an iPhone. BUT… more women than men bought smartphones in the last 6 months. Forrester did some market segmentation on women gadget owners:
37% self sufficient, tech savvy
35% neutral, little engagement, low willingness
28% opportunity
Women feel overwhelmed and confused by choice of Android devices. They are twice as likely to have never downloaded a single app as it don’t see most of the apps as relevant to their lives. They want apps to solve a problem, to answer a question.
Recommendation: solve a problem, entertain, don’t educate
Turn good ideas into great apps: by Reto Meier
Shared more details on deadly sins & glorious virtues for android applications. Same Google IO 2010 talk & slides were repeated.
Android beyond the phone; Tablets, eReaders, and more: by Karl- Johan
Dell Streak uses mDPI resources but has much bigger screen. Android dual screen displays and e-Ink displays behave completely differently. Custom device manufacturers are really keen to have apps on their devices. They’ll expect a 20-50% markdown, but no need to pay app store fees. ViewSonic ViewPad 7 now available in the UK for £399: Having 800x400px display and runs Android 2.2 and Wi-Fi, Bluetooth, GPRS & 3G.
The Snapdragon Mobile Development Platform: by Qualcomm
Qualcomm is taking on a new role of being the link in the ecosystem, ensuring that there are great apps for the ecosystem. They want to make sure that apps work well. Snapdragon is a system on a chip for ARM-based CPU, GPU, rich multimedia, GPS, 3G, Camera, power management.
Android reuse models: by Mark Murphey
He discussed some of the ways in which we can reduce lots of android developers reinventing the wheel everytime we need something. There are a few methods that a developer can use for distributional: Souce Code, As an Application, as a jar or Library.
Libraries can be used to solve problems for people who want free and paid versions of the app, and don’t want to maintain two versions of the code. He went on to discuss that we need a place to collect code to reuse and mentioned building a community website for this purpose, also saying “I can’t write a website to save my soul, I ain’t doing it!”
Future of Android panel
Ewan MacLeod moderated the panel:
Questions faced by the panel:
We’re still on the dream phase for Android: consumers “only buy one Android device”… Will consumers retreat to “something familiar”?
Nokia is still a big player but no longer biggest in all mobile developed countries
Android has challenges with fragmentation
One challenge for Android is capturing lower end, but high end phones will trickle down
Breadth of Google’s web services provides a very strong disincentive to leave
Google is encouraging OEMs & operators to fight amongst themselves to get great user experience
If I was your fairy godmother, what would you wish to change in Android?
-A decent automated testing framework on a range of devices
-A working billing infrastructure
-Developers making sure that their app manifests include clearly defined API access and permission
-Google to be a little more open about what they’re aiming at and what they’re not, to provide some reassurance
-Better way of getting hardware acceleration support
Teleca Stand:
We had lots of android developers coming to our stand and wanting to know more about Teleca offerings. The following demos just didn’t fail to amaze them:
-TI Dual Display on Android
-Android ported on Freescale Imax 53 board
-MeeGo phone
-AIM app totally based on Open Source.
We got people to our stand interested in joining Teleca as developers as we are globally looking into hiring many hundreds.
And, our presentation: We had proposed a Talk on “Dual Display” but due to the board overheating the demos for the presentation did not perform thus we couldn’t deliver the talk. Delegates approached the stand to know why the talk was cancelled, as we explained they were fine in just understanding the architecture for Dual Display.
The best compliment was when one of our partner companies with a booth next to ours, also dedicated appreciations of Teleca’s work to the bunch of attendees. It’s was indeed a proud movement.
Finally lots of interesting questions we got from the attendees:
- What can we expect from Teleca in MWC 2011?
- What kind of work are we doing in Automotive space?
- When are the dual display android devices coming in the market?
- Which will be the number one platform by the end of 2011?
- Is Teleca planning to get into products ?
- Are we working on CRM, ERP modules for mobile devices?
It will be an interesting next 3 months to show what we actually are doing on the above.
By Andrew Till
Last week I and several colleagues attended the latest OSiM London event. I had the pleasure of presenting Teleca’s take on the evolving applications landscape and some of the challenges for developers in maximising their success in bringing compelling and profitable applications to market. At the end of the presentation I shared our “Top Tips” for success with applications based on our experience of developing applications for customers across multiple platforms. I thought it would be interesting to share these recommendations on our blog – enjoy and hopefully you will find these insight and useful.
1. Take a position, solve a utility or entertainment problem
It’s absolutely critical to be clear about the purpose of the application you’re developing and to also ensure that it solves a real problem. For example it’s not clear that we need any more calculator applications in the Android Market place given the number already available. Being clear about the problem being solved will help all the way through the development process and when it comes to loading you application on to an application store and the supporting messages you include with it.
2. Focus on User Acquisition, Engagement AND Retention
We see many developers and companies who only focus on the initial acquisition of users for their application but in our experience continued focus on regular engagement and retention is also key not only to the success of the current application but also for future application releases as well.
One interesting way of managing this is to measure how new features or feature removals drives key metrics such as application downloads, uninstalls and user rating.
3. Use the Metrics and know your competition
Many application stores now provide a wealth of data on how your application is performing, where it is ranked, who is downloading it and which market they are in. Using this information on a daily basis significantly improves your chances of success as it enables you to respond quickly to changing market demands, optimize pricing, assuming you are charging for the application, based on what is happing with your application and those it competes with and to critically identify when you hit the sweet spot with different demographics.
Using such metrics can also help you understand who you are really competing with and to plan accordingly. Most people assume they are competing with other applications in the same category but this may not always be the case as you may simply be competing for share of wallet and hence in reality your competition with many different types of application.
Put simply if you’re not using the tools provided by the store vendor they you cannot expect to have a killer app on your hands.
4. Release early and often
Trying to build the perfect application often leads to long overruns and being beaten to market by competitors. Increasing we are seeing that it is much more effective to release early and provide frequent updates to users. This has a number of benefits such as enabling you to “land grab” in new areas, helping to build a regular dialogue with consumers and critically building customer delight each time you provide an enhanced set of features. Typically apps can see > 80% of active users upgrade to the latest version within 30 days of release especially on platforms that provide notification services.
Using this approach can also enable one to identify if a feature is really worthwhile fully developing or if it is only going to resonate with a small number of users thus saving time, money and effort. Another benefit can be to help user re-engage with an application when they see that new features are available and thus helping to maintain a healthy active user base.
5. Integrate Facebook, Twitter and other social engagement channels
Leveraging social networking sites can bring many advantages. The most obvious is that it helps to increase visibility of your application and can stimulate a level of viral growth that is hard to achieve with other mediums. Today most social networks have standard APIs to enable seamless login and posting of a users account and make these available for integration via standard SDKs.
6. Build communication channels with your users to foster a community
Creating an on-going dialogue with your users is often the key to sustained success. Typical App store ratings are very binary (love/hate) and provide limited insights. Increasingly developers are now moving to utilise platforms such as GetSatisfaction, Twitter and other which enable a much richer level of communication and also provide detailed insights as to why users really love or hate what you have done. It also enables you to grow your voice in the market place, provide you engage and respond to users posts and build to app missionaries from your user base.
7. Show focus by Platform and Devices
With such a proliferation of platforms and device types it can be a killer trying to release on everything everywhere. Increasing we are seeing customer decided to focus on getting one platform right before moving to multi-platform deployment. While this may mean that you yield some time to market on a particular platform is also means that when you do move to multi-platform support you have a robust codebase to port and an growing user base, and hopefully evangelists, to support your expansion.
This last area is one in which Teleca has a great deal of experience, extending the capability of the Flash Lite player on mobile and embedded devices to allow OEMs to use Flash content for much more than just games and utilities – enabling tight device integration and using Flash content for the whole device UI, for example. Using Flash and AIR 2 capabilities to provide home screens and UIs on platforms such as Android may help companies to quickly and easily differentiate their products.
Teleca are heavily involved in projects using Adobe’s new Flash Platform run-times including Flash Player 10.1 and Flash Lite 4 and have also created some demos using AIR 2. This is an area we are seeing a growing level of interest in from developers and we can expect more growth over the coming quarters.