This week in class we had the opportunity to listen to Chuck Hudson from Control4 speak about mobile application design. He opened up his talk with a discussion on the "device market", and it's recent revolution from the mobile way of thinking. It's not about the fact that it's mobile, it's about the devices that client's are trying to connect with, i.e. smart phones, tablets, TV, car displays. He spoke a bit about the major market players and the market trends. Android and iOS are leading the pack in the U.S. He then detailed out the various markets that individuals apps can fall into:
- pure application sales
- outside mobile license
- advertising supported
- referral/affiliate fee
- complimentary model
- in-app purchases
After that we dug right in to the meat of developing an application, starting with the design and the challenges faced by mobile development. He shared with us the statistic that "1 in 4 apps downloaded are never used." And that's huge. There are so many considerations for determining whether an application is going to succeed such as the orientation, the envisioned usage, the platform, space size restrictions. He also could not more highly emphasize the need to storyboard and protoype as well as test, test, test, One prototyping program he recommended was Balsmiq (www.balsmiq.com). He also highly recommended getting involved in user groups such as those located here: developer.android.com and developer.apple.com/ios.
After that, we broke it down to the platform level. For the Android, we discusses screen resolution support
(4 generalized sizes; 4 size densities), graphics and layout complexity, device testing and compatibility, and device fragmentation. When developing for the Android, the environment is open sourced (eclipse and the android sdk). The key differences include a community fed library and diverse widget availability. The example that we went over is located here. When you are ready to distribute your app, you can upload it to a couple of different sites, but mainly the Android Martketplace or Amazon. The process includes code signing, incorporating any marketing information, and submitting to each site. You also should think about any legal action you'd like to take before making the application public.
We then spoke about iOS development. iOS development uses an MVC design pattern that is coded in Apple developed objective C. The development tools are more mature than the Android's since it's been on the market the longest and include xcode, an interface builder, and instruments. Apple also has the iOS Ad Hoc Program to help get your product in beta testing. To release your app to the public, you need to add your app, upload it via the Application Loader, go through the certification process by Apple, then release it when you are ready. Some common issues experienced during this include improper UI usage, over-throttling web request pulls, and memory leaks.
After that we talked about the considerations that need answering before a deployment.
- Which OS versions do you support? A good general rule is the current version plus one.
- How will licensing be handled? A tip for handling licensing is to balance the level of licensing with the effort needed.
- Will you implement localization? If so, how? And how will you maintain it in the long run? In-house, contractor, or community group?
- Beta Test, Beta Test, Beta Test.
Then we talked about how to measure your applications success. It's unique to each application and it's developer, but you could gauge it by number of installs, amount of traffic, utilize any statistics available through the market, or even create your own measurement by using built-in logging. You should also have a process ready for supporting your application. Always welcome feedback, create new updates, and build in code support mechanisms. A few tips and tricks that he left us with include: know that development will always be a continual investment; market yourself, get out there and get noticed; test, test, test; and launch! Don't hold back. Always look back on your 1.0 version and be embarrassed.
No comments:
Post a Comment