Archive for the ‘Google’ Category
My previous article was dedicated to promotion of the applications on the AppStore but in this one I would like to focus on the Android application promotion. So you are welcome to read my article and to find some useful tips in these regards.:)
It is known fact that nowadays Android becomes more and more popular and there are a lot of individual apps uploaded to the Google Play every day. Thank is why it is also crucially important to take all the possible variants to promote your application and make it worth to be downloaded. Below I’m sharing some of the working tips which you can utilize and create a buzz about your latest app developed by you.
- First of all you before you submit your Android app to the market, you should not to forget that the application has to be fully complete and should have a good interface. It is not a good idea of submitting a partial app. Submitting a partial app will lower your users ratings and will blow your plan permanently. Also it is known that google’s play market algorithm will take your app higher if the users rate well in the initial stage. That’s one of the tricks to improve your download count.
- App stores: Submitting your app to several app stores is an easy free way to make the application more visible. The first stop should be made on Google Play. You could submit it to GetJar and Amazon Android Market places as well. But I would like to note that Google Market + Amazon take a revenue share of money you make from either selling your app or from any in app purchases (IAP) that are made through their billing solutions which is the trade-off for exposure. Getjar only accepts free apps and allows you to implement your own billing solutions if you use IAP.
- Get an eye-catching icon: Make sure that you have an attractive and eye-catching app icon that best represents and sells your application to the user. Poor icons blows you app to the bottom and will indicate an unfinished or poorly made app. Optimize and beautify your icons.
- Launch the free “Lite” version of the application. The free apps gets the user base and then it will tend the user in buying add-ons or the full version if he likes it. Or you can simply launch a free app with ad and promote an add free with some advance feature in your premium version. You can also consider launching your app for free for first 2 weeks to increase the user base and later on you can upgrade the price.
- Promoting through reviews: before someone would like to download your application you should take care of its promotion. So the best method to market your app from my experience is through content and reviews. You can have reviews in the form of small description about your app, ratings of the apps, review date. This will help people to know about your android app.
- Video marketing: The video marketing is important tool for internet advertising. We can explain the features of our apps by creating videos. The videos can be placed on various websites to attract the audience. This can serve as great tool for promotion of android apps. So you can make a couple of YouTube videos showing how the app would look like and how people can use it. Also try to make the video using a better clarity and understanding which is also worth sharing.
-Use of Social media, Forums & Blog posting: We can use various social websites such as FaceBook, twitter, linked-In, You-tube for promotion of android apps. We can participate in the forums & blog posting for the marketing of the android apps. It will help to share the information about your apps. You may also sent emails to any bloggers for review of your app, make sure that you also send them your video link. This will help a blogger to understand your product better and will help them to write better app reviews.
These are some ways to promote an Android application that just came to my mindJ. Please feel free to add any variants you’ve had a chance to try and they worked well for you and what is more important that they were effective.
Google is pregnant again?
Perhaps you have heard this statement. Also you could hear that the “baby” has been created to substitute Java… and number of similar statements… But What is NOOP?!
Some people are reporting it to be Google new language, which is not quite technically correct. Noop is being developed by a group of independent developers as a side project, a few of which happen to work at Google.
Noop is built on the Java Virtual Machine and is syntactically similar to Java. What it adds, though, is dependency injection and testability functionality built directly into the language…
What is the status of NOOP?
Development on the language is still at an early phase, but many hope that they release something to the public in the near future. There is no binary to download, although, the source code is available from their online repository.
Why this language?
The experience shows that developers often create code that’s hard to test and maintain, without realizing this. On a large software project, this can create problems later on for the whole team. While analyzing this problem, it was found that the root cause in many cases was language features – like globally visible state, misused subclassing, obligatory and redundant boilerplate, and API’s that are easily misused. The language seeks to apply the wealth of lessons of language development over the past 20 years and optimize on cleanliness, testability, ease-of-modification, and readability.
Also we should consider the following factors why to choose/try this language:
1) Dependency Injection changed the way we write software. Spring overtook EJB’s in thoughtful enterprises, and Guice and PicoContainer are an important part of many well-written applications today.
2) Automated testing, especially Unit Testing, is also a crucial part of building reliable software that you can feel confident about supporting and changing over its lifetime. Any decent software shop should be writing some tests, the best ones are test-driven and have good code coverage.
3) Immutability and minimal variable scope are encouraged by making final/const behavior the default and providing easy access to a functional style. Testability is encouraged by providing Dependency Injection at the language level and a compact constructor injection syntax.
In conclusion I would like to notice that this language experiment attempts to blend the best lessons of languages old and new and syntactically encourages what we believe to be good coding practices. However only time will tell whether it will last or merely be another fad language which the programming world is littered with. In any case this language might be worth taking a look at… ;-)
Thank you for your attention and you are welcome with your comments!
This last option — which is currently the only one available to those who truly object to Google’s new policy — could be very difficult, especially for Android users. And most especially for those who have recently invested in Samsung’s Galaxy Nexus Smartphone, which is pretty much useless outside of the Google net verse.
I must admit, the idea of being completely unable to opt out of specific privacy issues has me very troubled. My immediate reaction is to read Google’s policies, check out some of the more knowledgeable commentators on the subject, and if I find that I do agree with those privacy activists who believe that Google has stepped too far over the line, to join those hoping to pressure the company to alter its new policy.
Google’s applications and products have become an important resource for a large number of people. Their new policy has just been announced, and has over a month to be put into effect. Things can go several ways at this point: Google could simply stick to its guns and hope that the resulting fallout will only be a bit of bad publicity and a relatively few lost users. But if enough Google users become uneasy, Google could back off (the way Facebook has several times over the last few years), at least in it’s “all or nothing” opt-out policy. It will be interesting to watch.
Microsoft might have sold hundreds of millions of Windows 7 licenses, and Apple might be managing to persuade tens of millions of people to buy iOS-powered devices every quarter, but the real winner when it comes to operating systems in 2011 as been Android, Google’s mobile operating system.
Based on the Linux kernel, Android is a wildly successful platform. By November of this year some 200 million Android powered devices were in use. If that sounds impressive, consider that this number is growing by some 550,000 daily (or 3.85 million a week, 16.5 million a month). Also, last quarter Apple sold 17 million iPhones and 11 million iPads over the three month period.
Despite Google not charging handset makers a dime for Android, the mobile platform is a huge money spinner for the company. Android pulled in some $2.5 billion for Google during its last financial year (all from ads), and this number is set to double during this financial year. As the number of Android devices out in the wild increase (and the number of eyeballs looking at the ads increase), then this figure will keep on growing.
Then there are the 10 billion app downloads. That’s a staggering number, and at the equivalent point in the Apple App Store’s life cycle, it had only managed around half this number of download. What’s more impressive is realizing that Google only broke the 3 billion mark back in March of this year, so that’s 7 billion in around 8 months (it took Google 20 months to hit the billion download mark in July 2010).
There may be issues that Google need to address when it comes to Android, but we can’t allow this to take away from the successes achieved by the mobile platform. Apple might be grabbing the limelight with iOS and the iDevices it is installed on, but Android is the platform for the masses.
Android is, without a doubt, the most successful Linux distro out there. And it’s only going to go from strength to strength come 2012.
Definitely, there are certain benefits of using cloud services, but the cost of these benefits may be too high if you can’t rely on the cloud. So do you trust the cloud?
It’s not so much to the cloud itself – you really have to consider the number of dependencies between you and the cloud provider – this is something people seldom ever calculate into their equation. Sure we can trust the Cloud provider to have redundant Power Backups & Generators, but there are a number of components between you and the provider that are UN-accounted networks and outside of either party’s control.
I have to quote this:
“It is never okay to allow someone you don’t know to see or hold your confidential information, whether professional or personal.”
I think people always forget to compare local downtimes to cloud ones. How often does Google suffer an outage vs. how much business do you lose vs. how much accountability exists?
We work with cloud providers that start losing money if they go below a minimum level of uptime. Can your locally hosted infrastructure guarantee that – not really.
You can’t 100% trust anyone/thing. Neither the cloud, nor your local infrastructure, nor your own cell phone where you store all your data. The advantage that the cloud offsets though is multiple copies of data and better redundancies. This means that if you notice, even when Google suffers outages (small or big), you don’t lose email that was sent to you. 6 months ago Google suffered an outage where a percentage of users lost all their mails in their inboxes. In 48-72 hours, Google restored all of these from their backup infrastructure and continued delivering new mail.
I bring this up to you since most people never factor in the reliability of all related networks between you and the Cloud – it is a critical mistake to leave this out. I trust the cloud, but have less trust in what connects us and won’t keep applications that are critical to local operations on a cloud service utilizing networks that is harbor much less reliability which is out of our control. While cloud computing is great, it’s still a gamble to rely too much on it at this time. That is the dark secret.