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.
- Download the Android Studio package from above.
- Install Android Studio and the SDK tools:
Mac OS X:
- Launch the downloaded EXE file,
- Follow the setup wizard to install Android Studio.
Known issue: On some Windows systems, the launcher script does not find where Java is installed. If you encounter this problem, you need to set an environment variable indicating the correct location.
Select Start menu > Computer > System Properties > Advanced System Properties. Then open Advanced tab > Environment Variables and add a new system variable
JAVA_HOMEthat points to your JDK folder, for example
- Open the downloaded DMG file,
- Drag and drop Android Studio into the Applications folder.
Known issue: Depending on your security settings, when you attempt to open Android Studio, you might see a warning that says the package is damaged and should be moved to the trash. If this happens, go to System Preferences > Security & Privacy and under Allow applications downloaded from, select Anywhere. Then open Android Studio again.
- Unpack the downloaded Tar file,
android-studio-bundle-<version>.tgz, into an appropriate location for your applications.
- To launch Android Studio, navigate to the
android-studio/bin/directory in a terminal and execute
studio.sh.You may want to add
android-studio/bin/to your PATH environmental variable so that you can start Android Studio from any directory.
- Launch the downloaded EXE file,
sdk/directory. For example:
Putting together a rough sketch or wire frame of your app design is always a good idea. Doing this will provide the following advantages:
- It will assist you in communicating your idea to the developer, visual designer or others. It is much easier to get feedback on your ideas if you have a straw man to start the discussion with. The wire frame or prototype becomes your app blue print. You wouldn’t start building a house without plans (hopefully), similarly you should have a set of plans for your app.
- It will save you money. It is a lot easier and cheaper to change something in the prototyping phase than it is once the app is finished.
- It will save you time. Although taking the time to do a wire frame may seem like more effort, this will be repaid many times over during development and prevents false starts.
- It will improve your design. By sketching out the design and explaining how a user will move from screen to screen it will quickly become obvious what will work and what won’t. Doing this will also prompt other ideas, work as a creative catalyst and ensure that you have thought of every eventuality.
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:
- Keynotopia – Use PowePoint/Keynote to Prototype Like a Pro
- Justinmind – Rich interactive wireframes to define web and mobile applications
- Proto.io – Mobile prototyping
- UXPin – UX design tools built by UX designers
- AppGyver’s Prototyper – Turn wireframes into an interactive mobile app prototype
- App Mockup Tools
- WireKit – An iPhone app wireframe kit
- DevRocket – Photoshop panel plugin for iOS developers
- Fluid UI – Mobile Prototypes for iOS, Android and Windows Apps
- UI Stencils – Stencils, sketch pads and accessories for UI design
- App Cooker – Advanced iOS mockup generator for mobile applications
- Flinto – Quickly create iOS prototypes
- App Icon Template – App icon template for iOS 7
- PortKit – UX Metaphor Equivalents for iOS & Android
- iOS 7 Wireframe Kit
- SketchMirror – Preview your mobile apps directly on your devices
- Invision – Free Web & Mobile Mockup and UI Prototyping Tool
- Framer – Prototyping tool for animation and interaction
- Marvel – Free prototyping tool
- POP (Prototyping on paper) – iPhone App Prototyping Made Easy
- Mockabilly – App for creating mockups on iPhone
- Interface – Advanced mockup and prototyping for iOS
- Blueprint – Mockup iPad app for iPhone and iPad applications
- Proptotypes – Turn static designs intro a tappable iPhone prototype
- FieldTest – Create mobile interactive prototypes
- Dotted Paper
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 operands
From these numbers, several measures can be calculated:
- Program vocabulary:
- Program length:
- Calculated program length:
- Difficulty :
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
- How customised is the user interface? Score from 0 for using the provided UI elements to 20 for a totally customised UI. Most game apps score a 20 for this, as everything from the buttons to the navigation bars need to be customised to suit the game theme. Utility apps are more likely to get a low score.
- How complicated is the underlying data model? This could vary from 0 for no persistent data to 20 for server based data. Using SQL or Core Data (for iOS) would be somewhere in the middle.
- How complex is the app? This relates to the app objective and may influence the other considerations. For example, an app with low complexity may simply display data. The other extreme would be an app that performs route mapping or language recognition. This dimension is a measure of what you are trying to do, the previous question on the data model is an element of how you are solving the problem. A lot of games can be surprisingly complex, an example of this would be if you were trying to build a decent AI for a 3D environment. Complexity will also influence how much code you will need to write which in itself will make life more difficult (have a look at the Halstead equations above).
- Who, what or how does the app have to communicate? You would score a 0 for this if the app was stand alone. The score would rise with the scale and type of networking required. You would also take into account how the networking was performed (e.g. Bluetooth, Wi Fi, etc) and how robust it needed to be (redundancy?).
- Does the app require 3rd party libraries or API’s? This could be ad servers, geo location, language recognition, translation services or anything similar. Score 0 for none and increase the score based on the number of interfaces. We also vary the score based on the maturity of the API and the API provider.
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:
- > 80: Insane:: You probably need to double the price you first thought of. Complexity increases exponentially (not linearly) with added elements because they all interact with each other.
- 60 – 80: Difficult:: In this range you would double check everything and ensure that you have a tight specification. This app will likely take you longer than you expect and throw up things that you don’t expect. Add an extra 25 – 50% contingency.
- 40 – 60: Average:: Most apps will fall into this range, no extra contingency should be required as long as the specification is solid and you have wire frames.
- 20 – 40: Easy:: Should be a walk in the park. A good place for beginner developers to start.
- 0 – 10: Simple:: There can never be too many fart apps.
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:
- Gradle-based build support.
- Android-specific refactoring and quick fixes.
- Lint tools to catch performance, usability, version compatibility and other problems.
- ProGuard and app-signing capabilities.
- Template-based wizards to create common Android designs and components.
- A rich layout editor that allows you to drag-and-drop UI components, preview layouts on multiple screen configurations, and much more.
- Built-in support for Google Cloud Platform, making it easy to integrate Google Cloud Messaging and App Engine as server-side components.
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.
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.
- Include Social Media Integration Within the app. Allow users to share via Facebook, Twitter etc
- Include Email Share features. Word of Mouth Marketing! Allow your users to email their friends about your app.
- Include direct feedback option. Allow users to submit feedback and comments within the app. Getting negative reviews hurts! Reduce the odds of negative comments by allowing your users to provide feedback directly to you with your app.
- Promote and entice ratings within your app. Ratings are a form of marketing for your app, a very important form. Getting positive ratings is critical. Ask user to rate and review your app, within your app. I posted about this here: How to Get More (& Positive) App Reviews and Ratings
- Online Marketing- create a dedicated website for your app. These days hosting is inexpensive. With most major hosts you can do a one click install of WordPress and using a free (and responsive, so it plays well on mobile) theme you can be up and running in little time. A website is key because you can link your Press Releases back to your website and App Review Requests. Your website will earn links and eventually rank in Google and other search engines for search queries related to your app. This form of online marketing will help your app get more installs by driving search traffic from the search engines.
- Social Media- create a Facebook page for your app. Create a Twitter account for your app. Publicize your social media accounts on your dedicated app website.
- Optimize Your App Description. Using keyword research (Google Keyword Planner) create a strategy for your app. Ensure your app title, description and keywords are optimized for a strategic keyword. Once your app page is optimized focus attention to optimizing your dedicated app website.
- Design an amazing app icon and screenshots. This is the most overlooked by app publishers. Your potential app users are very design focused… both app stores and centered mainly on app icon images. Remember someone looking for your app is really looking at your app icon first, along side dozens of your competitors icons. If your icon doesn’t stand out, they will simply click on your competitors icon. I have seen so many truly great apps that fail because the icon is poorly designed. Look at your app icon next to your competitors icon before you launch your app and see if it stands out well, ask yourself “would I click on my icon or one of the others?”
- Create a Press Release for your app. Post it on your dedicated app website.. and post it to press release sites.
- Create a short video demo of your app. Post it to YouTube. Share it in your Press Release.. share it when you request app reviews.
- Prepare for app review requests. There are hundreds of websites that review apps.. many for free. Once your app is live- submit it to these sites to get reviews and links to your app. Include your press release and video url with your request. Our team can do this work for you and submit your app to over 155 iPhone app Review Sites or over 115 Android App Review Sites.
- Research related blogs to your app. Every App has an audience and for every audience there are blogs. Research blogs that are on the same topic of your app. Find the related site, contact details, Facebook profiles. When your app is ready you can reach out and network with these sites to help market and promote your app. You can share your Press Release and YouTube Video and you can kindly request a review of your app. You can also offer to guest post on their blog in return for a link back. You can do this work yourself, or have our team assist by researching 100 related blogs to your app.