We have published a new Android Tutorial over at the Android Studio Tutorial site.
In this first tutorial we will do the traditional thing and write a “Hello World” Android app. This is very simple with Android Studio and doesn’t require any actual coding since the default app says Hello World. Nevertheless, it does demonstrate how to build an Android Project from scratch and understand the options in the New Project Wizard.
We are using the Developer Preview (version 0.4.0) of Android Studio at the time of writing. Installation details may change so visit the Android Studio site to check out the latest instructions and to download the relevant setup program.
From the Android Studio site:
javac -version. If JDK is not available or the version is lower than 6, download JDK from here.android-studio-bundle-<version>.exe.Select Start menu > Computer > System Properties > Advanced System Properties. Then open Advanced tab > Environment Variables and add a new system variable JAVA_HOME that points to your JDK folder, for exampleC:\Program Files\Java\jdk1.7.0_21.
android-studio-bundle-<version>.dmg.android-studio-bundle-<version>.tgz, into an appropriate location for your applications.android-studio/bin/ directory in a terminal and execute studio.sh.
android-studio/bin/ to your PATH environmental variable so that you can start Android Studio from any directory.sdk/directory. For example:\Users\<user>\AppData\Local\Android\android-studio\sdk\Mac: /Applications/Android\ Studio.app/sdk/
Putting together a rough sketch or wire frame of your app design is always a good idea. Doing this will provide the following advantages:
There are many tools and resources available to help make prototyping and generating wire frames easier. Below are 26 resources which can be used to generate your wire frames:
It is difficult to calculate how difficult an app will be to build, but it can be useful to know this when developing a quote for an app. There are a few different approaches that you can take.
You could use Halstead complexity measures which are software metrics introduced by Maurice Howard Halstead in 1977 as part of his treatise on establishing an empirical science of software development. Halstead made the observation that metrics of the software should reflect the implementation or expression of algorithms in different languages, but be independent of their execution on a specific platform. These metrics are therefore computed statically from the code using the following:
For a given problem, Let:
= the number of distinct operators
= the number of distinct operands
= the total number of operators
= the total number of operandsFrom these numbers, several measures can be calculated:
The big problem with this approach is that you can’t calculate the metrics until you have written the code. This is problematic at the quotation stage of a project.
Our approach is based more on heuristics (i.e. educated guessing). By completing the following quick questionnaire we can come up with a score out of 100 which approximates the complexity and hence development effort required. This is used as an input into calculating the number of hours required and ultimately the cost.
Reefwing Complexity Matrix
Once you have calculated your complexity score by adding the results from the five questions above you will get a number out of 100. We segment our apps into the following categories:
We haven’t seen any other attempts to model app complexity but we would love to hear about the practices or thoughts of other developers.
At Google I/O 2013, Google launched a new Integrated Development Environment (IDE) based on IntelliJ IDEA, called Android Studio.
Android Studio provides integrated Android developer tools for development and debugging. On top of the capabilities you expect from IntelliJ, Android Studio offers:
Android Studio includes a powerful code editor, which supports smart editing, advanced code refactoring, and deep static code analysis.
Smart editing includes inline resource lookups that make it easier to read your code. Code refactoring allows you to transform your code across the scope of the entire project.
Static code analysis helps you identify bugs quickly. On top of the hundreds of code inspections that IntelliJ IDEA provides, Google have added custom inspections. For example, metadata to the Android APIs, that flag which methods can return null and which can’t, which constants are allowed for which methods, and so on. Android Studio uses that data to analyze your code and find potential errors.
Be aware that Android Studio is currently available as an early access preview. Several features are either incomplete or not yet implemented and you may encounter bugs. If you are not comfortable using an unfinished product, you may want to instead download (or continue to use) the ADT Bundle (Eclipse with the ADT Plugin).
Instructions for downloading the latest version of Android Studio are available here: http://developer.android.com/sdk/installing/studio.html. Versions are available for download on Windows, Mac OS X and Linux.
For many people the whole point of writing applications is to see them published in the App store and available for download from iTunes. Before you quit your job and go out and buy matching Porsche 911’s you would be wise to get a few months of sales data under your belt. Like most endeavours, there is a bell curve of app sales. Everyone hears about Angry Birds developers making $70m, but there is a lot less media coverage at the other end of the bell curve.
In a recent survey of more than 1,500 developers in 83 countries, it was found that the average per-app revenue is roughly $1,200 to $3,900 depending on the platform. Additionally, the survey noted that an app has roughly a 35% chance of generating between $1 to $500. This obviously means that most developers cannot rely on app development as their main source of income. However, it does mean that if you put the effort in you can make enough to fund your development habit.
Our own experience is that you can never tell which Apps are going to be regular sellers (LifeGoals) and which will sink like a stone (LifeMovie). The Reefwing stable of Apps currently nets us around AUD$10k per annum, which is sufficient to purchase a MacBook Air, a new iPad, external development costs (Apple Developers Licence, App Sales Analytics, web-site and forum costs, etc.) plus a bit of change for the highly caffeinated beverages which programmers run on. Working mainly on on our contracted 3rd party apps we only work on these on the odd night and weekend so with more application we imagine the rewards would be better. The thing that we are no where near recovering is the time spent developing. The average App takes us about 3 months from start to finish and while the proceeds roll in for some years to come, it isn’t really passive income because sales quickly decline if you aren’t frequently updating your app.
However, lets face it – we would code if we didn’t get paid anything so anything we do get is a very pleasant upside. There is also something addictive about tracking the daily “sales” of you app (even if it is free).
The other thing that most developers don’t realise, is that the apps which are successful in the App store, have as much time and money spent on marketing their Apps as they do on developing them. There is the odd exception but these are an exception. Books have been written on this subject and we will provide our thoughts on the best approaches to marketing in another blog post.
14 Ways to Monetize your App (courtesy of yourAppreport.com)
1. Paid Downloads aka Pay Per Download – Paid downloads work as users pay up-front to download your app once it’s available in one of the app markets. Paid download apps work well for apps in the gaming, entertainment, productivity, navigation and news categories. However, the more users pay up-front, the less tolerant they may be of advertising or in-app purchases. You might try considering to offer a free version plus a paid version of your mobile app with additional content that contains fewer or maybe even no advertisements.
2. In-App Advertising aka Mobile Ads – One of the most popular among mobile app developers. In-App Advertising works by allowing ads run on space sold within your app and revenue is based on number of user impressions and/or clicks. These really work well on the gaming, news, chat and entertainment category apps. However, the small drawback with in-app ads is that your app will have to bring back users regularly, and basically be designed for heavy use.
3. In-App Purchases or Subscriptions – In-App Purchases work by allowing users additional purchasing privileges, badges or subscriptions inside the app once they’ve downloaded it. These work pretty good for apps in the gaming, lifestyle and news categories. However, this type of app really requires a very loyal following of users that are willing to pay for virtual or ongoing benefits. You will need to regularly add fresh content as well.
4. Sponsorships – Sponsorships can work by individuals or businesses basically under-writing your app in exchange for recognition type benefits. An example of this would be maybe an ad or logo within your app. These work best for Local + Event focused apps and narrow focused audiences. The drawback here is that these are typically a one-shot source of revenue. They usually aren’t ongoing or scalable. However, it’s a pretty good way to get a first app off the ground.
5. Push Ads: Ads are displayed in the notification tray of an opted-in user’s device. CTR’s and conversion rates are sky high with this format, since there are no accidental clicks like with in-app ads. Advertisers pay on a CPC basis. Unlike traditional mobile ads, these ads are not placed inside apps. Each ad is also tagged with a permanent opt-out link, as well as the name of the app which delivered the ad. However, on iOS systems, you can get really crafty with Apple’s push notifications availability. (Be careful with that).
6. Icon Ads: Similar to the pre-installed apps which come with a new smartphone, Icon Ads are sponsored shortcuts (icons) placed on the home screen of an opted-in user’s device. Advertisers pay on a CPI basis for each icon installed on a device.
7. Dialog Ads: Ads are displayed as a dialog box inside an app, presenting the user with a 1 sentence call-to-action along with an OK and Cancel button. For example, the ad can ask the user “Check out a free new 3-d game” with an OK and Cancel button underneath. Advertisers pay on a CPC basis.
8. OfferWall Ads: Ads for individual promotional offers are placed in a single in-app interstitial and can be selected by a user for participation. Advertisers pay on a CPC or CPA basis.
9. Video Ads: High-quality Video Ads are shown in-app. Our proprietary ad server only displays Video Ads to users on a wi-fi or 4g connection, ensuring a positive viewing experience. Advertisers pay on a CPM basis.
10. Rich Media Ads: A full landing page is embedded inside an app, with a fixed close button at the top. Advertisers can build rich experiences which are directly embedded in another app.
12. Full-Page Banner Ads: Ad is displayed as an in-app interstitial to users, with a fixed close button at the top. Advertisers pay on a CPC basis.
13. AppWall Ads: AppWall a new interstitial mobile ad format that Advertisers can use to generate huge CTRs and higher engagement than virtually any other in-app ad type. Displayed within an app session, AppWall displays a variety of different offers and actively optimizes their placement in order to drive results that were never before possible in the mobile marketing space.
14. Affiliate Offers: A great way to monetize your app is to leverage affiliate offers. There are 1000’s of affiliate offers available for almost any topic. When you hear “affiliate” you may be thinking someone has to pull out their credit card and purchase something from an online store and you will get a percentage… this is true, but there are also PPA affiliate offers (Pay Per Acquisition)- where you can get paid if one of your app users simply registers for a newsletter or website. I have found these offers work great in apps. Most people prefer to make affiliate purchases, with a credit card on their desktop computer, most people don’t want to pull our a credit card and type all those digits into their little smartphone screen. With PPC offers- you can show the user a relevant ad, the user can signup for a newsletter and you can get paid $1,2$ or more each time
Here are some affiliate sites to check out for PPA offers you could add to your app:
Building the greatest app in the world means very little if nobody can find it. Marketing considerations are a critical aspect of any app launch. This is true now more than ever, as the app store becomes more and more competitive.
Most developers have processes and checklists around app development prior to go live, like testing on multiple devices. What about a checklist for app marketing prior to go live? Below is an App Marketing & Go Live Checklist (courtesy of AppReporting.com) that we like to go through before we launch an app.
Marketing Checklist:
You have decided that your business needs an app, so what is the best way to ensure that you get what you want?
Well you could follow the App Happening four step framework:
This is a best in class solution for getting the app you want, at the lowest cost, in the shortest possible time. App Happening provides free marketing tips, app concept templates, strategy guides, development timelines and even an eBook on creating a successful app (http://www.apphappening.com/ah/appbuildingguides). So why does (almost) nobody use these? I suspect the reason is a combination of, “too hard”, “why bother” and “I just want to get started”!
As a Developer, I’m not too worried about whether your app is going to sell well or deliver on your business case. My job is to deliver the app you specified at the cost I bid and within the agreed time frame. If you have reached the stage of hiring a Developer, I assume that you have already worked out that the cost and effort is worthwhile. If not, then I suggest that you go and have a look at the Concept, Marketing & Viability section (http://www.apphappening.com/ah/conceptmarketingviability) of the web site.
I’m also assuming that you have a clear idea of what your app will do, because if you don’t, explaining the concept to me will be difficult. I don’t need a complete Functional Description and fully laid out screen shots initially but I need enough to be able to provide you a price and how long the development process will take. Before going into the bare minimum specification requirements, I would like to discuss why the specification step is important.
How to spend a lot of Money and NOT get what you want!
If you have ever renovated a house you will know that the cheapest time to modify the design is before construction start. It is exactly the same for app development. You want to have a very good idea of the outcome before you start. Sooner or later you will need to make decisions about what the app will do and what it will look like. Given this fact, doesn’t it make sense to do it at the beginning? I guarantee that if you do, it will save you money and reduce frustration.
There are generally two ways that you can engage a Developer:
1. Fixed price; or
2. Hourly rate.
If you choose to go the hourly rate route then you could just make it up as you go along (some people call this AGILE development) but it can become expensive. If you select the fixed price approach, it is much more important that you get the definition phase correct. Do not assume that a feature that you want is included in the design, if it hasn’t been explicitly specified then your developer hasn’t costed it and it is unlikely to end up in the final product. Assumptions in the design phase of fixed price contracts lead to disputes, which waste everyones time and energy.
I have enough stress in my life…
If the specification of your app consists of something like “i need a game built in 1 week for a fixed price of $100”, don’t be surprised if no developers bid on it (what game? what platform? what device? what???). The level of design specification required depends on where you are in the development cycle. If you just want indicative pricing to plug into your business model then simple dot points which describe the objective, functionality and target platform (e.g. iOS or Android) are probably sufficient – just be up front with the Developer.
If you are committed to building an app then I’m afraid that I’m going to direct you back to the App Happening website page (http://www.apphappening.com/ah/designspec) on Design and Specification. It is in your interests to specify the app as fully as possible. You should include the Developer in this process if possible. Start with your simple dot point functional specification. Your Developer can tell you what is technically possible on a particular platform and what is possible but difficult (i.e. expensive). Once you have a good idea of app functionality, sketch up some indicative screen shots (wire frames), pen and paper is fine. Alternately get the Developer to suggest something. You want these wire frames to be low fidelity so that people are comfortable playing around with the design and changing them. The combination of the Functional Spec and the Wireframes will give you a flow diagram or flow map which describes how users will move around your app. Make sure that key functional screens are at the top of your navigation stack.
If your Functional Spec is detailed enough, the data base design (if required) will fall out of this. For a people based app, you may want to save information like name, address, phone, favourite colour, etc. Consider whether you think the data model will change in the future, if the ability to update and migrate data models isn’t built into the original design it can be expensive to retrofit it.
If you follow the above suggestions, your Developer will be in the best possible position to assure you get what you want, when you want it.
What are five ways that you can harness the power of mobile apps?
If you decide to have an app built for your business, it’s important to be clear about your objectives from the start and strategise around them:
