In contrast, I started investing in Alexa mid/late-2018 and while it was great to start, it has become increasingly useful. It makes phone calls to businesses, and gets it right very consistently; it knows business hours; the automation has become more powerful over time (a category Cortana never even began to touch); and the integration ecosystem is superb.
Alexa keep improving, too. Yesterday I invoked a routine that included playing music, while the invoked service was busy playing on another device. While in the past the music just wouldn't have played, now she says, 'Amazon Music is already in use on another device. Did you want to play Thunderstorm Sounds on Bedroom Sonos?' That's just one example, but they are numerous and regular enough that I was able to pick one from just yesterday.
I remain flabbergasted that today, in 2020, phones don't blend into desktop and laptop computers in any significant manner. I can't browse files on my iPhone X from my Windows 10 desktop through Bluetooth. There are band-aids and work arounds through apps and services. My point is that this should be a natural integration by now, not a pile of band-aids. To be sure, companies like Apple are at fault as well.
Think about everything you can do when you plug in a second, third or fourth monitor into your computer. You should be able to do that and more with your multi-core, multi-gigabyte, hyper-connected, high display resolution smart device.
I should be able to start a Zoom meeting on my phone, swipe the call onto my computer screen and back. I should be able to drop PDF and other files onto my phone by dragging them into the aforementioned native interface.
I still think MS have an opportunity to come out (again) with a phone that is a such a good extension of Windows that it would feel like you ripped the phone right off the Windows desktop and file system. The problem with this is it requires leadership and commitment they might not have.
On Android+Linux, KDE Connect is a single solution to do all of this. Files, clipboards, bidirectional music/volume control, pausing computer music during phone calls, notifications, SMS (desktop app), type from computer onto phone, and more. I've heard there's some work going on to make it work on Windows+Android, and for Linux there's already a KDE Connect applet to make it work on desktop environments other than KDE.
Microsoft did something like that in 2015. The high end Lumia's could plug into a dock with a keyboard, mouse and display and show a windows desktop with a start menu and apps.
It was called Windows 10 Continuum and it never caught on.
e.g. Win10 has automatic tablet mode. Perfect.
Apple have gotten pretty far along that road with Airdrop, it works great.
As for the rest, MS tried some of that stuff and it landed with a thud. The mass market doesn’t actually care for the stuff (how often are you actually taking a Zoom call on your phone and wanting to transfer it? I like the idea but I can’t think of many times it would actually apply).
I’m sceptical it would ever be a thing now. There’s a reason why so many companies make Electron apps: desktop apps just aren’t all that important, and they’re not likely to dedicate dev resources to one.
I absolutely loved my Windows phones. I had a couple of different Lumia phones, including the flagship Lumia 920 which had a pretty decent camera for the time, but my favorite was the Lumia 520. The Lumia 520 was only $60, and didn't need a case or screen protector or anything fancy like that. When it was dropped, the back popped off and the battery flew out which reduced the impact on the screen. It had offline maps, a web browser, and the battery easily lasted for 3 days. And if it was lost, it was just $60 to replace! I went through 3 of them before my bank removed their Windows Phone app, which meant that I couldn't do mobile check deposit. I "upgraded" to an android phone, which cost much more and was so much more complicated to use.
But... no apps. And then they pissed everyone off by announcing that Windows Phone 7 devices wouldn’t get an upgrade to 8. That was the point at which I realised MS didn’t really understand what they were doing and switched to iPhone. I still think there was potential there, but alas...
For example WP7s emphasis on big long lists made it very hard for me as a dyslexic to quickly scan for the one app I wanted in that list. My eyes would constantly jump about and the lack of other visual clues made it hard to anchor to the item I wanted. I don’t even have this problem menu bars because those have more visual clues that WP7 did.
Another issue was how the flat design made it impossible to distinguish between a button and a highlighted block. Also between a hyperlink and normal emphasised text (frankly, hyperlinks do not belong on UIs outside of document markups. There was one time my mum changed her WP7 language to Polish (she has Polish heritage) to see if she could read it. She couldn’t and that mistake was totally user error on her part. But she could read enough to get us to the language settings and it literally took both her and I more than 10 minutes to realise that there was a button that needed pressing after the language selection because the button blended in with all the text on that dialogue. If your only distinguishing feature of interactive elements is their caption then that’s simply bad UI design.
To give balance, I’ve used nearly every Windows device on phones or PDAs. While Windows Mobile (and CE before it) had its own issues they were still enjoyable devices in their own ways. But I hated WP7 because the UI constantly left me guessing. My mum hated it for the same reason so switched to Android. One of my friends, who is a reasonably technical Windows fanboy but doesn’t work in the IT industry, he hated it too and then switch to Android. It was not a well design UI at all. And while I’m sure there are pockets of engineers who will miss WP7, I’ve never met a single end user who liked it.
I was one over also by the UI, found it super easy to use.
The overall flat design was a big pain in the ass when you couldn’t tell what was clickable / editable.
The accessibility of putting the data first was awesome. Apps being tiles or a simple list of names was great. They started that with the Zune and it’s still a winning play on the Xbox. It worked great on the phone.
I want to try light phone and hope it doesn’t suck.
Note that people are much more likely to talk to their phone in private than in public. It’s rude/weird to talk to one with people around. I use mine at home or when away from people.
I use mine for the following:
* turn on/off the lights
* play some music
* what’s the weather
* call people
* add X to my grocery list
* start a timer
* occasionally, open an app. Usually on apple watch where this is faster
* Remind me tomorrow to do X
* Get me directions home
* Show me pictures of X
* Start/stop time tracking timers
The common thing is they’re all simple functions, quick to say, and faster by voice than going 3-4 steps into a UI and typing stuff out.
This is on iPhone. I imagine all of the above use cases work well on android, and I think others would be effective too, as google assistant is reputed to be more powerful.
Note that siri used to be garbage at understanding me. After using it a while it seems much better. Either she learned or I learned to speak differently.
Maybe voice search will be a big thing, maybe not. But if it proves to be one, Google needs to have an established product in that space before it takes off and they're left playing catch-up.
Believe it or not a lot of use is out of the public eye, though. Lots of usage is in cars (where there has been a sharp shift to phone powered interfaces), and as an assistive tech. They are great for breastfeeding moms as an example.
I do have smart speakers and I use them every day to run my lights, music, set alarms, etc. It is wonderful to be able to say 'Alexa, next song' while in the shower and have it just work (with a Sonos speaker, btw).
My own experience, having given Siri and Googles alternatives are fair chance on my phone, went “Hey Siri/Google. Do this thing... OK why did I even bother? It would have been faster to just do it myself”
Do Android users who are part of the Google Home or Alexa ecosystems not use their phones for `OK Google` or `Alexa`? Or do such people only use dedicated Google/Amazon hardware?
I couldn't name a single thing that has improved my usage of Google Assistant since launch. In fact, Assistant isn't any better for my usage than the previous thing, Google Voice Search, available years before. Whatever all the people working on these assistants are doing, it isn't the right thing.
I wish MS didnt think shiny when thinking about these two apps. Outlook and Teams (at my workplace) log me out from laptop and mobile without warning and send me an SMS OTP I have to use within 5 minutes. They don't even have a resend OTP so I have to restart the apps and hope the SMS arrives on time. Outlook web is slow as molasses on Firefox and of course years behind Gmail.
Ideal corporation according to HN commenters:
1) Moderately successful, but not too successful (my Foo can't compete with Bar)
2) Run by at most 20 people (why do they need so many people, me and my buddy could do it in a week!)
3) Maintains all products/features indefinitely even if less then 1% of the users use it (Google killed RSS Reader)
4) Directs all earnings back into the product (they have so much money, surely they can afford to all maintain all products/features indefinitely)
5) Pays below market rates (engineers make too much money)
6) Grows organically with no VC/investor money
7) Makes no mistakes. All experiments end up being total hits / cash cows forever.
1% of all Google users is what, a gazillion people?
Actual issue: They use their success to bludgeon competitors to death. E.g. what Microsoft used to do to Linux, which is why we still don't have a viable Linux on desktop even though nearly everyone agrees that they only use Windows 10 because they have to and not because they want to. Plus, now that Microsoft has apparently "done a 180 on open source" (read: we used the bludgeoning time to figure out how to profit from OSS), their success is the equivalent of breaking a sleeping man's knee and handing him a stick to walk, and then patting yourself for your generosity.
Actual issue: They don't provide support commensurate to the number of people building it once the project's hype factor goes down. A good example is nearly every not-very-cool-anymore OSS library which was announced with great hype 4 years ago, is not used a lot today, and the employees of the BigCo treat everyone who raises GitHub issues with general disdain and disinterest. Although, to be fair, I think this is the fault of the suckers who go and use this OSS library. As they say "Fool me once..."
Actual issue: Unlike BigCo, which can kill whatever product they want and not face the smallest problem, the user base of these products in terms of actual usage is so big, it can support a company or two or twenty. People who are investing the time to build on your bloody platform are regularly treated in the same way Mark Z thinks of his user base ("dumb fucks").
Actual issue: Not actually committing resources to product support.
Here is something which should make you laugh, if it didn't also make you cry in case you are a Google Cloud developer (you cannot remove yourself from a Google Cloud project that someone else added you into):
The issue is marked as priority: P2, severity: S2. Really? And Mr Thomas Kurian wants developers to evangelize Google Cloud when they wouldn't even take care of these kinds of things for over 5 years?
Actual issue: Hard to say, because on the one hand, they are definitely overpaid with respect to the difference between their actual performance and their own perception of it (for e.g. even the biggest supporters of the tech that comes from BigCo, when pressed, will point out a laundry list of bugs). Not to mention the perennially lousy support on the projects deemed by the engineers as not-sexy-anymore. On the other hand, if some of these folks end up going to jail for things such as trying to manipulate elections (which I firmly believe is a question of when and not if), then you want them to be compensated for that risk.
Actual issue: Taking investor money is just a neon warning sign today: "expect user hostile behavior in our product very soon". If the vast majority of VC backed companies didn't become user hostile, this wouldn't have been a big issue.
Actual issue: these experiments are often accompanied by extreme hype and overpromising. To be fair, once again, I say "Fool me once..."
Did you notice I finally put most of the blame on the people who trust BigCo, because they repeatedly act like suckers? There is indeed a sucker born every minute, and the surest sign of that is the fact that people are actually signing up for something like Facebook Shops. So the HN crowd is the voice of the skeptic. I actually hope it is never pleased about anything.
I'm assuming that "July 31st" means 2019? Otherwise, that's a few-hours window.
Should manufacturers be forced to support devices for a set amount of time (5 years?) or should the customer start demanding it?