It appears we are using our Windows Phones and other cell phones more for data applications than voice calls. In a New York Times article, the wireless industry association CTIA reports that in 2009 the amount of data in text, e-mail, streaming video, music and other services surpassed the amount of voice data in calls.
CTIA has witnessed a decline in voice data over the past two years with the call duration following suit. The average length of a local call was 1.81 minutes in 2009 compared to 2.27 minutes in 2008.
Conversely, data usage has increased. Text messaging alone increased almost 50% since 2008. Phone design is also becoming more data friendly with more QWERTY keyboards popping up.
So, are you part of the data crowd who text's short messages to your spouse, friend or family member instead of making a short voice call to them? Do you rely more on email than voice calls?
George is the Reviews Editor at Windows Central, concentrating on Windows 10 PC and Mobile apps. He's been a supporter of the platform since the days of Windows CE and uses his current Windows 10 Mobile phone daily to keep up with life and enjoy a game during down time.
our phones make phone calls? who knew
i average around 10GB of data (once over 15GB), 1200 text messages, and at most 300 minutes of voice usage per month. Despite AT&T being loathed by many, i stick with them because they don't give me any hassles with using so much data... yet.
Data and text have cheap flat rate plans as compared to voice plans. voice plans are a rip off minuets aren't actual minutes and there not counted the same universally among all networks. u cant monitor ur actual minute usage in real time, the start of every second is counted as a minute. It better to jus get a data plan - send messages by email set it so it checks it every minute or so now u wont need a text plan and call people using skype
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.