[新聞] 為何Lumia 1020依然不會成功
原文網址:http://ppt.cc/aSDt
Why The Amazing New Flagship Windows Phone Will Fail
Nokia's new Lumia smartphone has amazing hardware (especially its
unprecedented 41-megapixel camera). And it doesn't matter at all, because its
software lags so far behind its hardware.
By Dan Nosowitz Posted 07.12.2013 at 11:28 am 25 Comments
When HTC released a gorgeous, powerful, innovative, distinctive Android phone
a few weeks ago, we realized Android was suddenly an option for everyone,
even the very rich. But yesterday, Nokia unveiled its newest flagship
smartphone, a gorgeous, powerful, innovative, distinctive Windows Phone, and
I suspect it won't sell any better than the Lumia 920, the last flagship
Nokia Windows Phone (which in its first quarter sold 4.4 million units,
compared to the iPhone 5's 27.4 million). Or the Lumia before that. Or the
one before that. That's because Windows Phone has a serious problem: its
hardware is improving rapidly, but its operating software is not.
Two years ago, we reviewed Windows Phone 7.5, the first major update to the
then-new Windows Phone operating system, and said we were still "waiting for
it to really live up to its promise." One year ago, we reviewed the Nokia
Lumia 920, with the Windows Phone 8 update, and said "Windows Phone has huge
problems. That doesn't mean it's bad, but we're two years into this operating
system, and it still has basic issues that impact daily use."
The new Lumia looks great--I was very impressed with the camera technology
when I saw it last year, and the aesthetics of the Lumia line have always
been stylish and playful in a way that's totally different from anything else
on the market. But that doesn't matter at all, because Microsoft is not
improving the Windows Phone operating system at anywhere near the pace it
needs to.
Here's a brief list of major problems Microsoft has yet to address.
1. Multitasking is sometimes inscrutable, in that you never know which apps
will show up in the "currently running" list of apps.
2. Email threading often doesn't work, especially with Gmail accounts.
3. Lots of features, including Rooms (sort of a mobile, multimedia chat
room) are Windows Phone exclusives, meaning they can only be accessed with
Windows Phones--cool, but it's pretty unlikely all your friends have Windows
Phones too.
4. Speech recognition is lousy, nowhere near as good as Google's Android
voice control or even Apple's Siri.
5. There's no place to see notifications at all; if you get an alert on an
app that you haven't pinned to your homescreen, you'd never know.
6. Bing Maps doesn't have public transit directions, let alone bike directions.
7. It's not easy to share photos to services like Twitter and Facebook;
Android and iOS let you do that in one touch, but not Windows Phone.
Microsoft can fix all that stuff. Microsoft needs to fix all that stuff. But
the biggest problem might be the hardest to fix: there aren't nearly enough
good apps available for Windows Phone.
App developers are often low-budget and understaffed, even wildly successful
ones, and it's expensive and time-consuming to assign people to port apps to
another platform, like Windows Phone. They'll do it, sure, if they have the
resources and it seems like the userbase is big enough to make them some
money... and therein lies the problem.
It's a cyclical issue. Developers won't make apps for a platform nobody uses,
and nobody will buy a phone with no apps. No customers leads to no apps leads
to no customers.
Microsoft can break the cycle, though. All it has to do is take advantage of
the fact that it's one of the biggest and most powerful companies in the
world: take a cannon, fill it up with money and talented developers, and aim
it south from the Microsoft campus in Redmond, Washington straight at Silicon
Valley. (Or wherever else the developers call home.) Aim the cash cannon
east, at London, and give King.com, the makers of massive hit Candy Crush, a
couple hundred thousand dollars and a team of developers to port the game
over to Windows Phone. Do the same for Instagram (which is still not
available on Windows Phone), Snapchat, Dots, or whatever else people are
using on other platforms.
Microsoft has the clout and capital to fix its own problems--it just needs to
actually spend the time and money it'll take to do it.
===================
懶人包:WP8太廢啦,跟不上Nokia硬體創新的速度
--
Ghostcrawler: Kalgan's always been NICE to paladins,
there must be something mistaken.
--
※ 發信站: 批踢踢實業坊(ptt.cc)
◆ From: 114.34.52.100
→
07/14 10:18, , 1F
07/14 10:18, 1F
推
07/14 10:37, , 2F
07/14 10:37, 2F
推
07/14 10:46, , 3F
07/14 10:46, 3F
推
07/14 10:55, , 4F
07/14 10:55, 4F
推
07/14 10:55, , 5F
07/14 10:55, 5F
→
07/14 10:57, , 6F
07/14 10:57, 6F
→
07/14 10:57, , 7F
07/14 10:57, 7F
推
07/14 11:00, , 8F
07/14 11:00, 8F
推
07/14 11:00, , 9F
07/14 11:00, 9F
推
07/14 11:03, , 10F
07/14 11:03, 10F
推
07/14 11:09, , 11F
07/14 11:09, 11F
推
07/14 11:17, , 12F
07/14 11:17, 12F
推
07/14 11:24, , 13F
07/14 11:24, 13F
推
07/14 11:27, , 14F
07/14 11:27, 14F
推
07/14 11:34, , 15F
07/14 11:34, 15F
→
07/14 11:36, , 16F
07/14 11:36, 16F
推
07/14 11:38, , 17F
07/14 11:38, 17F
→
07/14 11:39, , 18F
07/14 11:39, 18F
→
07/14 11:40, , 19F
07/14 11:40, 19F
→
07/14 11:40, , 20F
07/14 11:40, 20F
推
07/14 11:42, , 21F
07/14 11:42, 21F
噓
07/14 11:46, , 22F
07/14 11:46, 22F
→
07/14 11:47, , 23F
07/14 11:47, 23F
→
07/14 11:48, , 24F
07/14 11:48, 24F
→
07/14 11:48, , 25F
07/14 11:48, 25F
→
07/14 11:49, , 26F
07/14 11:49, 26F
→
07/14 11:49, , 27F
07/14 11:49, 27F
→
07/14 11:50, , 28F
07/14 11:50, 28F
推
07/14 11:50, , 29F
07/14 11:50, 29F
→
07/14 11:51, , 30F
07/14 11:51, 30F
→
07/14 11:52, , 31F
07/14 11:52, 31F
→
07/14 11:54, , 32F
07/14 11:54, 32F
→
07/14 11:54, , 33F
07/14 11:54, 33F
→
07/14 11:54, , 34F
07/14 11:54, 34F
→
07/14 11:55, , 35F
07/14 11:55, 35F
推
07/14 12:01, , 36F
07/14 12:01, 36F
→
07/14 12:03, , 37F
07/14 12:03, 37F
→
07/14 12:04, , 38F
07/14 12:04, 38F
推
07/14 12:07, , 39F
07/14 12:07, 39F
→
07/14 12:08, , 40F
07/14 12:08, 40F
推
07/14 12:31, , 41F
07/14 12:31, 41F
→
07/14 12:34, , 42F
07/14 12:34, 42F
→
07/14 12:46, , 43F
07/14 12:46, 43F
→
07/14 12:50, , 44F
07/14 12:50, 44F
→
07/14 12:55, , 45F
07/14 12:55, 45F
→
07/14 12:56, , 46F
07/14 12:56, 46F
→
07/14 15:05, , 47F
07/14 15:05, 47F
推
07/14 15:08, , 48F
07/14 15:08, 48F
→
07/14 15:08, , 49F
07/14 15:08, 49F
推
07/14 20:22, , 50F
07/14 20:22, 50F
→
07/14 20:39, , 51F
07/14 20:39, 51F
→
07/14 20:39, , 52F
07/14 20:39, 52F
推
07/14 20:44, , 53F
07/14 20:44, 53F
推
07/14 20:44, , 54F
07/14 20:44, 54F
→
07/14 20:45, , 55F
07/14 20:45, 55F
→
07/14 20:45, , 56F
07/14 20:45, 56F
→
07/14 20:46, , 57F
07/14 20:46, 57F
推
07/14 20:49, , 58F
07/14 20:49, 58F
推
07/14 20:49, , 59F
07/14 20:49, 59F
→
07/14 20:50, , 60F
07/14 20:50, 60F
→
07/14 20:51, , 61F
07/14 20:51, 61F
→
07/14 20:51, , 62F
07/14 20:51, 62F
→
07/14 20:51, , 63F
07/14 20:51, 63F
→
07/14 20:51, , 64F
07/14 20:51, 64F
→
07/14 20:52, , 65F
07/14 20:52, 65F
→
07/14 20:52, , 66F
07/14 20:52, 66F
→
07/14 20:52, , 67F
07/14 20:52, 67F
→
07/14 20:53, , 68F
07/14 20:53, 68F
→
07/14 20:53, , 69F
07/14 20:53, 69F
→
07/14 20:54, , 70F
07/14 20:54, 70F
→
07/14 20:54, , 71F
07/14 20:54, 71F
→
07/14 20:54, , 72F
07/14 20:54, 72F
→
07/14 20:54, , 73F
07/14 20:54, 73F
→
07/14 20:54, , 74F
07/14 20:54, 74F
→
07/14 20:55, , 75F
07/14 20:55, 75F
→
07/14 20:55, , 76F
07/14 20:55, 76F
→
07/14 20:55, , 77F
07/14 20:55, 77F
→
07/14 20:55, , 78F
07/14 20:55, 78F
→
07/14 20:55, , 79F
07/14 20:55, 79F
→
07/14 20:56, , 80F
07/14 20:56, 80F
推
07/14 20:56, , 81F
07/14 20:56, 81F
→
07/14 20:57, , 82F
07/14 20:57, 82F
→
07/14 20:57, , 83F
07/14 20:57, 83F
→
07/14 20:57, , 84F
07/14 20:57, 84F
→
07/14 20:57, , 85F
07/14 20:57, 85F
→
07/14 20:57, , 86F
07/14 20:57, 86F
→
07/14 20:58, , 87F
07/14 20:58, 87F
→
07/14 20:58, , 88F
07/14 20:58, 88F
→
07/14 20:58, , 89F
07/14 20:58, 89F
→
07/14 20:59, , 90F
07/14 20:59, 90F
→
07/14 20:59, , 91F
07/14 20:59, 91F
推
07/15 11:53, , 92F
07/15 11:53, 92F
推
07/15 15:29, , 93F
07/15 15:29, 93F
推
07/15 15:40, , 94F
07/15 15:40, 94F
→
07/15 16:42, , 95F
07/15 16:42, 95F
討論串 (同標題文章)
以下文章回應了本文:
完整討論串 (本文為第 1 之 2 篇):