In this guide you’ll learn how to destroy 2/3 of your user base in Chrome Web Store with a single update. Take a look on the chart:
This is the history of real chrome app and as you see, at the time when the “killer-update” came it was installed by almost 32,000 Chrome users. Then I made new version of the app and that single update caused a lose of almost 2/3 of the users. (They are 13,400 right now, but still dropping). Nice update, isn’t it 😉 And the problem was not in the updated code — it was just a simple new feature added. Still, some features may kill your app. Are you curious how I managed to achieve that? Then just read the rest of this post. That could save you from doing the same mistake…
Continue reading Chrome Web Store: How to Destroy your App’s User Base with Just One Update
Content is King. Google made this clear over the years.
But any king needs an army. And obviously — we are the army. Bloggers, web-masters, SEO specialists… We are all in the never-ending battle to get our sites popular. And since we have a king, a a holy goal and an army… what more we need?
Weapons (software and tools). Maps (any attack starts with a map). Data (because there is no other way to decide how we’ll fight our battle than relying on experience, analytics and …data). And this little piece of data is here to answer one single question:
Does Community News Submission work?
Well… It seems obvious that we need to submit our great articles to community-news sections of related sites. But is it that obvious? Yes, we all know any form of popularization is welcome (I don’t mean “black-hat things here), but when you have to decide where to put your time, it does matter what exactly one could expect. I couldn’t find a proof that it is a must to spend time to submit my blog posts to community-news sites, so about 6 weeks ago I started one small experiment to see does that really affect blog popularity. Continue reading Community News Submission: To Do or Not?
Back in November, after few weeks of curiosity, I decided to give jQueryMobile a try. In my world that means: get the framework, create a real-life example and put it into the wild. It was “a must” especially in this case, because I couldn’t find any real-life example of using jQueryMobile back then (everything I managed to find was just these simple nice how-to tutorials, but I was interested in web apps, not mobile sites with few pages) It is always the same: everything looks fine with any framework when you read the documentation, but is it suitable (and where is it suitable) can be found only with real-life tests… Continue reading jQueryMobile: does it work?
Are you a webmaster? Do you publish on the web? There is one big question any webmaster or site owner must answer: do my site looks as expected in different browsers and operating systems?
If you already know how to test the integrity of your design on different platforms and browsers, you may skip reading this post right now. For anyone new in website publishing: the testing services listed below are “a must”. Every browser (and even the same browser in different operating system) will render your html in a different way, and (unfortunately) often the end user can see something ugly instead of the beautiful page you designed. But (fortunately), there are very good and free cross-browser test services online and you don’t have any excuse to avoid them. These below are my favorites:
This is one of the best and most used cross-browser testing services that works as standalone online service (https://browserlab.adobe.com/) and also from within Dreamweaver. I would advice, however, to use the online version with testing on real, remote server (not from your development machine). In fact, when I am building sites, I am always testing this way — local files tend to lead to problems. The way I am doing it: create a testt site online (some subdomain or a domain I am using for tests only), then uploading the site as on the final (real) server and testing this online demo. This is the closest thing to the real site I am building and gives me the exact result on how the final site will perform. But for quick tests while you are designing the Dreamweaver integration is fine. The browser lab service is still free — just go oand create your account with Adobe (they will ask for confirmation of your email in the usual “confirmation link” way).
Continue reading Multiple Browser Testing: Beginner’s Guide