Skip to main content

Usage share of web browsers

Internet surfers using PCS and laptops are turning to Google’s chrome browser quickly, according to recent statistics by StatCounter and Net Market Share.






StatCounter, published data that put Chrome as the world’s third most used browser in December 2011, after a growth spurt of around 12 percent from the same time in 2010.


StatCounter ranked IE first, with 39 percent, and Firefox was the second most preferred browser, used by 25 percent of the people who came online. Safari and Opera followed at 6 and 2 percent respectively. Interestingly, all the browsers on the list except Chrome have seen a steady decline from December 2010. 


Although statistics from Net Market Share state vastly different figures, they point in the same direction for all browsers. IE ranks first with 52 percent in December 2011 down from 59 percent in February of the same year, Firefox ranks second with 22 percent after a slide from 23 percent, and Chrome is at 19 percent while it was at 11 percent in February.


In any case, Chrome still has to grow its user base if it is to topple IE as the most preferred browser. According to statistics from Net Market Share, IE 8 comes first as the most preferred version of browsers used (28 percent), followed by Firefox and IE 9 having the same size of market share(12 percent). Chrome 15 owns 9 percent of the market, while IE6 and Chrome 16 both occupy fourth place at 7 percent.




World-wide Usage:-

Comments

Post a Comment

Popular posts from this blog

  Mastering Per-App Language Preferences: From Android 10 to Android 13+ One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping. Today, thanks to AppCompat 1.6.0+ , we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching. The Architecture: How it Works On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle. Step 1: The Locale Helper Utility Instead of scattering logic across your app, use a clean LocaleHelper o...
Post a Comment
Read more

Beyond Scanning: Meet the All-in-One AI Document Assistant by Digitify Vision Technology

In an era where efficiency is the ultimate currency, information is scattered everywhere—on physical paper, within QR codes, and inside lengthy digital documents. The challenge isn't just capturing this data; it’s making it work for you. At Digitify Vision Technology , we believe your smartphone should be more than just a camera—it should be a high-performance engine for your daily workflow. Today, we are proud to unveil our most powerful update yet: a total evolution in AI-driven document management. 💡 Key Features of the New Update We’ve bridged the gap between physical information and digital action by integrating advanced vision and audio intelligence into a single, seamless experience. 🔍 Precision Scanning for Everything Our advanced vision engine is now more versatile than ever. Intelligent Document Scanning: Capture crisp, professional-grade scans of physical papers, contracts, or handwritten notes. QR Code Extraction: Instantly scan any QR code to extract text, read URL...
Post a Comment
Read more
  Optimising Android Launch: Mastering App Startup & The Modern Splash Screen The first few seconds of an app’s life determine a user's first impression. A slow start or a flickering white screen can lead to immediate uninstalls. In this guide, we’ll look at how to streamline your initialisation using the App Startup Library and ensure a seamless visual transition with the Android 12 Splash Screen API (with full backward compatibility for API 29). Part 1: The App Startup Library Traditionally, apps initialised multiple components using separate content providers. This adds overhead and slows down launch time. The Jetpack App Startup library allows all components to share a single content provider, significantly improving performance. Why use it? Performance: Shared content provider reduces overhead. Order: Explicitly set the initialisation sequence. Simplicity: Both library creators and app developers use a unified interface. Part 2: The Modern Splash Screen API Starting ...
Post a Comment
Read more