Ask HN: Which great products didn't succeed?
What are some examples of this?
If there are examples of truly great products that eventually died, I'd like to study them more in-depth.
What are some examples of this?
If there are examples of truly great products that eventually died, I'd like to study them more in-depth.
I'm not entirely sure what caused their death, but my personal view is that they tried to become too big, and I don't think the wearables market is really that valuable. They could have remained a small house which maintained a great product for a segment of the market that really appreciated it. I'm sure that's a simplistic view, and definitely ill-informed since I wasn't on the inside.
I still think they are far better than the Apple Watch or any of the Android Wear devices I've seen.
I think you're spot on here. They had a perfectly viable 20-30 person company going in a nice stable little niche, and then the smartwatch hype cycle reached its peak and VCs threw a ton of cash at them along with a mandate to become the Next Big Thing. And so they hired way too many new people, churned out too many new models, and collapsed when the market just wasn't there.
Venture capital might be the only way to fund a moonshot-style startup but it seems to be the kiss of death for already-established, already-profitable businesses.
Smartwatches are not "moonshots". They shouldn't be treated as such. They could be a component of one, though, and society would benefit from components being economically stable, instead of imploding after few years. Pebble was arguably the sanest smartwatch design out there - long battery life, power-efficient screens, hackable[0]. Because they suddenly wanted to get too big too fast, the world today does not have any smartwatch of comparable quality and utility.
--
[0] - not just in terms of writing watch faces; people did try to use them as medical devices[1], and they even had a protocol for attaching custom hardware that didn't go anywhere, but probably would if the company was still around
The thing that blows me away is no one has really swooped in to replace it. I got a Pebble because I wanted an always-on screen with high battery life (I charge mine roughly once every 5 days), and I have no idea where I'm going to find one when the time comes.
If I'm able to eke out another 2-3 years, I might get an Apple Watch, which would presumably have 3-4 day battery life by then.
Nothing has gotten to the size of my my pebble time round though
The only thing I wish it had was an alarm that would wake me up at a specific level of sleep, like rem sleep.
The OS on it is quite nice, the iOS app isn't bad either, but the inaccuracy just drove me nuts.
I moved on to a Garmin vivosmart instead. Not quite as pretty, but a lot more accurate.
Today there is a myriad of competitors; when pebble.com went down, I bought one with 45 day battery life and otherwise the same features as a Pebble HR+ at the same price, plus GPS. There's third party apps for a few bucks.
I do miss the always-on display and its clarity, but not dealing with the slow and buggy software and lack of sync or ability to export the data. And I have more confidence in Xiaomi being around in a few years, not that it matters with Google Fit, MyFitnessPal and local CSV backups.
For my purposes, it is a productivity boost to have calendar, slack etc. notifications and be able to mute everything by holding a button.
Why?
I realised a couple of things once I lost it:
1. very few notifications need my urgent attention. In fact, I frequently have my notifications turned to "calls only" on my phone, and frequently leave it in another room on purpose so I don't have the temptation to look at it. A smartwatch would be thus a negative aspect of my life in this regard.
2. I don't need to track every aspect of my life, in fact that just generated more anxiety for me. I'm pretty fit, sleep soundly not enough (but tracking that never helped), eat very healthily, etc.. Tracking didn't help, it just added to the mental noise / anxiety (disclaimer: I don't suffer strongly from anxiety).
3. While I loved the PTR form-factor, I can't stand bulky watches (and really dislike cuboid watches). There just isn't a smartwatch with an aesthetic I'd consider wearing.
I'm still looking for a smartwatch that hits all the beats of Pebble.
Hasn't the Apple Watch been outselling Rolex etc.?
https://www.businessinsider.com/apple-outsold-the-entire-swi...
The only people I see wearing watches are business people who wear suits to work or work outdoors (people in the military). That's only a small percentage of people with a ~$100 product.
I'd actually bet that phones will be supplanted by a combination of smartwatch + smartglasses in the future.
If you have ever detachedly watched a crowd of people holding out these slabs in their hands and craning their necks over them, you might agree that it looks rather archaic and is begging to be put out of fashion.
Nobody can tell you how many Rolexes there are in total, let alone the sales figures of a specific model of a Rolex. That's partially what makes them so valuable. People usually don't change Rolexes every year when the new model is out.
It's incredible how normal it has become to switch out $500-$1200 products at such a cycle. Wasteful, next to no functional gain (certified electro-cardiography being exempt in my books), supporting narcissism...
It's consumerism to the max. We should all take a step back and think about what we are doing.
But in the case of the Apple Watch, I think this replacement cycle is the same as most jewelry/fashion items.
The cultural impact is undoubtedly lower.
If they sold additional services that weren't necessary for the watch to perfom, then maybe they'd have survived without depending on Kickstarter for funding.
I'm sad they're gone. There is nothing quite like it on the market.
At work we use Slack, Email, Google Docs, etc. We’re never quite happy with how things work - what should be email vs Slack, at what point should a a Slack conversation become an email conversation to be visible to more people, when should that turn into a doc for a more formal review process, etc. We’re trialling Notion for some things and it’s good. What should be a Wiki?
Whenever we have any of these discussions, I always feel like we’re circling around what Wave once was, and potentially could have been. It wasn’t fully polished, but so many of the fundamental concepts were there. If it had stuck I think communication in companies would be much better than it is now.
It was sadly ahead of its time and was probably pitched to the wrong audience from the start. Rather than trying to explain why Wave is better than email and chat to the internet at large, they probably should have pitched it as a business productivity tool. Oh, well. Hindsight is 20/20.
I wonder why Google didn't put a Wave section into Gmail, or a "take your email conversation to Wave" button for inter-Gmail conversations.
Google only have failed engineers turned product manager. they live and die by some random metrics. the gmail PM would never accept anything there that reduced time spent (or some other random, disconnected from reality, success metric) by a second!
As great as wave was, it didn't work very well either.
It was open sourced as Apache Wave. Yes, it was gwt.
We began project specs in ‘instant messaging ‘ type mode, and then back and fleshed out that conversation, editing the original posts to become full fledged documents. It was seamless.
Browser performance was a dog, bug I’m sure that could have been worked on.
Loved the ecosystem of apps and bots that was developing
They were way too early to market. Supposedly their compensation is or was structured to reward shipping new products/features to an extreme degree. I wonder how things might have turned out if they "shipped" it internally first, and iterated on it a few more times before putting it in the hands of the public.
I think if it really was so great others would have copied it and made great clones. Given that that never happened it would seem that others were never motivated enough to build a clone, which tells me that it was never useful enough.
I would be happy to be proven wrong about what a great tool it was, but in the end it seemed like more of a cool tech-demo than anything great.
We are building a collaborative productivity tool at Taskade (https://taskade.com), in part inspired by Google Wave. Would love to get your thoughts!
https://en.m.wikipedia.org/wiki/Groove_Networks
Ray Ozzie’s Groove was remarkable for distributed teams in the mid-2000s; I’d argue not yet replicated.
That is on the off chance that the message is actually delivered.
Trying to get omemo up and running, but some clients (pidgin) have next to no support for it, while others only support it, and it seems it is only supported on ejabberd as of very recently, with documentation on how to enable it consisting of a comment line in a config file.
I am not inclined to positively review a chat protocol that frequently fails to deliver messages.
OMEMO only really needs XEP-0163, the thing which also gives you avatars and such, supported nearly anywhere. There is some problem that you can't access the key of someone who did not add you yet to the contact list on older implementations [1] but that does not make it unusable.
> I am not inclined to positively review a chat protocol that frequently fails to deliver messages.
XMPP delivers, if you encrypt them with the wrong key it can do nothing about.
What part of XMPP is doing that? I think you're talking about a bug in an implementation of XMPP not the protocol itself. Its like saying you go to an address and get the wrong website. Hard to blame an issue like that on HTTP rather than a server or a client that implements it.
Is a protocol worth anything without an implementation?
Is a protocol good even if it only has poor implementations?
XMPP relies on clients having the Carbon Copy plugin installed.
Some clients have it installed, some clients do not.
If I have 3 devices connected to XMPP, which one gets a message sent to me is rather hard to determine. Often times it is the one I have most recently sent a message from, but other times it is not, and I will not get messages delivered to any of my other devices until I physically go home and log out of my desktop.
- Pidgin: Just take a look at their bug tracker. You will not have any problems finding tickets requesting essential features which are 6 years and older (e.g. Message Archive Management). So unless the Pidgin devs get some done I would not use their client (Gajim is a much better alternative, especially since the 1.0 release last year).
- ejabberd OMEMO: Actually, I don't know what the ejabberd devs were thinking when they changed their default config to disable OMEMO. They told something about having a hard time tracking down issues with OMEMO enabled. Well, kinda makes sense from a developers perspective, but given the fact that OMEMO is end-to-end encryption, I wonder what they were expecting. Nevertheless, disabling OMEMO by default on the server is just a stupid idea.
- message delivery: I had problems with that too, but ultimately it was just a problem with some ejabberd setting (I think it was mod_stream_mgmt: resend_on_timeout: if_offline) [1].
[1] https://docs.ejabberd.im/admin/configuration/#mod-stream-mgm...
force_node_config:
## Change from "whitelist" to "open" to enable OMEMO support
## See https://github.com/processone/ejabberd/issues/2425
"eu.siacs.conversations.axolotl.*":
access_model: whitelist
[1] https://github.com/processone/ejabberd/blob/master/ejabberd....http://deb.debian.org/debian/pool/main/e/ejabberd/ejabberd_1... (debian/patches/ejabberd.yml.example.diff)
When I got a MacOS machine up and running, I installed Adium (top result still if you go around looking for a MacOS XMPP client), also a dead project.
On Android, the top XMPP client does not support OMEMO and the new hotness XMPP client does not support OTP!
I have a legacy client on Android and Pidgin half hacked together with random plugins on my Windows boxes and I forget what in the world MacOS is running because I have it turned off half the time because the more clients I have connected the more problems I have and holy crap this is why Slack is a great product.
XMPP has had 20 years to solve these problems, and part of their problems of course is that the base protocol wasn't designed to solve these issues out of the box.
But, from the end user's perspective, Telegram, Signal, What's App, Slack, Discord, and Teams, all "just work"!
Same.
Well, it's not the only reason I'm in contact with less people now, but it's a major component.
Google stopped XMPP compatibility before FB messenger did. I believe the latter still had an interface to the XMPP world up until 2015.
Yes, all-electric is the future, but right now being able to be on battery 95% of the time, but never having range anxiety because I can always get gas when needed, is wonderful. I can go on long trips and never worry about having to pre-plan where I will charge up. Also, I didn't have to do any special electrical work because I can get a full 40 mile charge overnight on 12 amps.
I think it's really a great car and due to the electric motor it's fun to drive for someone who doesn't generally like driving.
At $160/kWh for lithium batteries, it seems you could put a simple Atkinson cycle gas generator in the car for less than the extra 40kwh of batteries and yield better range and flexibility.
They also killed the CT6 plug-in hybrid after 1 year.
Seems they have too much brand debt to even bother putting out decent cars since nobody will bother trusting it.
Altogether not a truly great tablet, but I loved the idea of the Pixel Qi display. Normal colored LCD when being used indoors with backlight enabled. But outdoors in the bright sun, the colors faded away and it became some e-paper like reflective display. That way you could use it for watching movies in the dark and reading books on the beach ;-)
Sadly the tablet had a lot of other flaws and the colors of the LCD weren't as good as the AMOLEDs we are used to today, but every time I see one of those ebook readers with b/w display I wonder why the Pixel Qi displays didn't make it.
I guess one of the reasons headless/compact guitars don't go outside of the niche of progressive/fusion circles is that it just doesn't have the "cool" factor or traditional bodies. Imagine Duane Allman with a Streinberger, or Clapton, Page etc. Just seems out of place I guess.
I would snap this up in an instant, if I had $100K+ in discretionary money lying around: https://reverb.com/item/16339446-travis-bean-tb500-14-1976-w...
People really hated it because (IMHO) it had a really rocky launch. Ubuntu replaced a very usable GNOME 2.x desktop with an alpha-quality replacement. And Canonical was riding high from having "won" the Linux for desktop game and was pushing their weight around, giving the impression that they were ignoring the feedback from their users.
Unity wasn't without its missteps. But it matured quite nicely and I now prefer it to other desktop paradigms. Windows especially. It feels a bit stuck, like Microsoft thinks it reached peak desktop design in 1994. ;-)
Now that Ubuntu has ditched Unity, I really don't know what I'm going to do. I've been holding on running Ubuntu 16.04, but it's getting to be a burden. I don't like GNOME 3. I'm still not sure what to do. I might give Pop!_OS a decent kicking of the tires. I know that's still GNOME 3, but their take on it is the closest I've seen it get to tolerable.
the sooner you accept the gnome legacy is dead and move on to kde the better. I know it will be difficult, but it's inevitable.
Found Ubuntu Mate and am loving it! MATE Tweak gives you so many options to make the UI work like Unity, even better in some ways. The only thing I missed were application shortcuts, but now the fancy dock works just as well for me.
nowadays it's pretty polished, fast and stable.
Gnome 2 was perfect for people coming from windows moving over. Gnome 3 is like windows vista.
Me personally, I was really disappointed (of course you can install gnome 2 etc). But at the end of the day you just want something that works out of the box.
I am dumbfounded that people still see this happening at some point.
I do all my development on it: VSCode, Postgres, docker, node, python, all works great. Importantly, the Crostini project is progressing rapidly and I get new functionality with each new ChromeOS release (e.g. shared files between Linux and ChromeOS, one-button container backup, etc.)
My analogy would be xp -> vista. Alienating core & target users.
What’s wrong with GNOME 3 or Vista? I’ve never had problems with either.
[0] Please see https://unity8.io/ and https://forums.ubports.com/category/36/unity8
Trying it out in a VM for now.
For the first time of me using Ubuntu (ver 18.04), I was disappointed in the fact that I had to re-learn some things and then get used to the new workflow when everything in 16.04 and Unity in particular was muscle memory.
I was a long-time Inbox user and was dreading the day I'd have to switch back to Gmail. But now that I've done it, I've found that I don't really miss Inbox at all.
Stars can be made to work like pinned e-mails, sort of, but it not consistent across the mobile app and the website and the UX just feels unresponsive in comparison. Pinned emails were much better separated than starred emails are today.
I think a bonus aspect was just design. Inbox didn't have to support as much legacy as Gmail and its design ended up being really sleek. Inbox overall just felt faster than using Gmail.
Right before the shutdown I've booked a fight and hotel for a conference in June and it was showing as a big card in inbox. After the gmail switch there is nothing displayed, I have to go hunting for confirmation emails. So sad to see inbox go.
Using Spark for Android and it seems to be scratching the itch so far
Gmail seems slow and cluttered by comparison.
And other UX issues: seeing previews of images right in the email list, font/UI makes it harder to find things vs Inbox. Inbox was a much nicer UI/UX.
Ads are annoying but I would have been fine with ads if it was integrated in Inbox.
And look, I understand that it doesn’t make sense to invest in/maintain two heavily used email clients. But the most infuriating thing is the trip bundles. That was my most used feature and such a distinguishing aspect of Inbox that it’s almost insulting that Google would tell me I can “find my favorite features in Gmail” when it’s blatantly not there.
I would pay to still use Inbox.
Inbox: drag&drop a screenshot, then make it an attachment. Gmail: save it as an image in a folder, then select the attachments and browse to the file.
Back in Gmail I go to my flagged/starred emails and I know I’m supposed to do something about the email, but many times I’ve forgotten what what specific action was, so I open up the email, read through it and realize that I for some reason or other won’t take the action right now. Having to ”rediscover” actions in emails is such a waste of time. With Inbox there would be clear ToDos written, so I could easily scan a list of emails and pick the right one to take action on.
Also very useful with emails containing many actions within, but only one or a few are left unresolved, or an email with useful links for future reading, so easy to specify what in the email I should focus on and thus ignore the rest.
RIP Inbox. Miss you dearly.
The other option is to keep the next actions in a separate list (or app), with a link to the email. Then you face the problem of context switching between 2 apps, so yours is better.
I just with that I didn't have to open the email to see the note I'd written myself; Inbox was so clever that the reminder was right under the subject line.
When I used it, I saw it as a blend between Android and iOS.
It had the beauty, polish, and responsiveness that I loved on iPhones, but had the developer options and open community that Android had. It was a great product, and it's a shame that now we really only have two choices for smartphone operating system, WebOS being neither.
On my nexus player I was able to install Kodi, which I love for all the formats it supports. Roku doesn't support nearly as many formats.
No, this one isn't true. Performance was one of the biggest problems of webOS. WebOS user forums were full of posts complaining about that. UI built with HTML and JavaScript rendered by Webkit1 was way too much for 2000s hardware to handle.
The mobile OS I miss is the most is the last iteration of BlackBerry. Although Palm had the upper hand in developer/user relations, I think that BlackBerry really got the UX right.
it was the mobile browser I could access more sites' content with at the time. even flash content, for better or worse! also I could download anything and open any local file, not just what apple allowed me.
Not the top feature, but one of the most glaring. At the time I was working on a site that used TypeKit and the only platform I was using that TypeKit didn't support was webOS. The whole thing seemed quite odd as they essentially yanked out a working feature of WebKit when making the browser. Flash, OTOH, was something that didn't die soon enough. I'd've much rather seen support for actual standards than Flash, but HP made a bunch of odd decisions with webOS and the Touchpad. There's some pretty delicious irony in a platform with web in the name having a mediocre web browser.
I also had a bear of a time getting email and WiFi set up for whatever reason, I relegated my Touchpad to paperweight status pretty quickly though. Even basic UI things like scrolling and copy-and-paste just didn't work all that well. Here's a review I found that highlights the distinct lack of polish that webOS had.
https://shawnblanc.net/2011/07/hp-touchpad-review/
Overall I thought RIMM/BlackBerry did a much better job with BB10 than Palm/HP did with webOS.
OTOH, maybe it wasn't that great. There's a lot of kiosks, car head units, set top boxes, etc out there just running extremely stripped down versions of linux or android, just for webkit. It's extremely popular in embedded circles when it comes time to put a ui on a touch screen. (for commercial products, not hobbyists)
"I still think RSS is a better way", fixed that for you.
Gives you an option to curate the content or follow with rich query builder.
(No affiliation, just a big fan)
Comprehensive music catalogue, servers never went down, and UI was simplicity incarnate.
Totally illegal business model, so it's not surprising that it didn't survive.
But it was awesome while it lasted.
It was no different to YouTube’s...
It's a fair comparison, but I suppose YouTube had:
(a) the veneer of being a platform to "upload/share your own videos" (c.f. Grooveshark, which was solely for copyrighted music)
(b) savvier management (?) who knew how to play the media/copyright business.
It completely disappeared a year or two and was replaced by a crappy news feed that is so poorly displayed you often can't even read the entire headline. Please tell me Google just his this feature and it still exists.
And (again on same hardware) it was if not faster, much more pleasant to the eye than most Linux distros.
Surely it needed less memory and processor power than the competitors or however felt on limited resources very "snappy".
The UI was fluid, but their network performance would take a hit from how their API had been designed: every action on the app would trigger a large JSON payload download (and sometimes upload).
It definitely felt nicer than Spotify.
Rdio also had an amazing recommendation engine from Echo Nest. Even though that company got bought by Spotify it took them a long time after the acquisition before they had decent recommendations.
Pros: Snappier to use, faster to open, never see the "Updating spotify" interstitial.
Cons: Spotify quits when I cmd-q Chrome, completely different UI layout to the thick client, doesn't understand the OS-level media control keys.
Closed and recovered as OSS by the former dev of the company as « OpenWhyd », and still accessible for free on a server, but he’s getting tired.
https://en.wikipedia.org/wiki/Google_Glass
A pure ingenious effort to turn humans into cyborg by adding the 4th dimension of computing to their lives in a non intrusive and seamless way. I can never understand why google couldn't make it popular given that wearable tech like watches and fitness band is catching up so quickly.
That being said, like someone else mentioned, Glass and AR-type products are very successful as productivity boosters in people who assemble products. We use Pupil Labs' glasses at our business to do gaze tracking. There's a lot of good use cases for this technology, but it's not cheap and it's pretty specific at this time.
Having some of the smartphone info in a HUD is a killer feature in itself, much better than a smartwatch.
Mostly in industrial use they are used to identify parts quickly with AR overlays.
Nobody could make it popular after that infamous shower photo. Products need certain coolness to gain traction and Scoble made it go the other way (I live in non-English speaking country and I use that shot to explain the word "nerd").
I'm not really that bothered by people holding phones in a way that might be surreptitiously recording me, because I expect they're actually using them for something else.
Apparently it now has "joined" mix.com, where you can only join via Facebook, twitter or google authentication. Thanks but no thanks.
Google mod chips some time they had them for the Playstation and XBox to use CDRs.
An exploit was found due to the console support for CD's with multimedia support, called MIL CDs. Initially a bootdisc was needed which you swapped with a CD-R, later all dumps of games were done in such a way that the exploit was bundled.
You are correct though in that some games used the full 1GB+ capacity of the GD-ROM format and assets had to be removed/compressed in some cases.
Now botching the Saturn launch because of political infighting between the Japanese and American branches of the company? If you're going to call them complete dumbshits for anything, that's what I would pick.
What about the Nintendo Switch?
There's also rumors of a Switch Mini coming.
size of Vita is more comfortable for portable gaming, and it is way more comfortable to play than Switch(controller ergonomics aren't great in Switch).
It sold about half as many, but it still did very well. It's the 11th best selling video game system of all time https://en.wikipedia.org/wiki/List_of_best-selling_game_cons...
It also means far less opportunity to exfiltrate data. There would be no Snowden if he had a dumb terminal that refused to mount storage USB devices, for example. I'm kinda surprised the intelligence community didn't go all in on dumb displays for that reason alone.
[0] https://www.nvidia.com/en-gb/geforce/products/geforce-now/wa...
I don't see the advantage of thin clients over network booted thick clients anyway. It's way more performant and more economical to execute client software on the client CPU.
The segregation and amplification of the server/client roles is what makes me connect it to modern cloud computing. Your local device capabilities (speed and space) isn't nearly as important as long as it has a capable Presentation Layer and a network route.
I remember that when I switched to GTalk, I still kept MSN for some of my contacts that I still chatted with, but eventually those people switched too and there was nothing left in MSN for me other that contacts with long and overly decorated status messages.
The official GTalk client was simple and lightweight. But then it died and the only official client was within Gmail, which I eventually stopped using because I missed so many messages when I was “online” while it was sitting unnoticed in tab on my browser.
I know GTalk is still alive and there’s WhatsApp, Telegram and such but I guess I miss the synchronous conversations back then, when people would still say “You gonna be online tonight? Let’s talk about it there”
Second to that is probably the void that Sunrise, Carousel and Rdio have left out. I still haven't worthy replacements to all of them.
Currently I have a pixel 3, and technically there isn't much of a difference, meaning that its far larger price tag hangs heavily on it.
Not that I think Google's hardware is doing a bang up job. Pixel buds are the worst headphones I've ever owned.
I see Palm already mentioned. Neo Geo.
Obviously everything I have done was great--too advanced for its time to succeed.
Great product, competitive sector.
100% death rate.
And yes, I know there was a "fix" released last year. Didn't work for any of them.
Great cheap phones other than that. Really good cameras on them.
I wrote a post about the alarm clock[1] a while ago, which I feel is pretty indicative of the thought that went into each feature.
Too bad about the rare bug that never got fixed that could show a received SMS under the wrong contact. Or the bug (which did finally get fixed by the community) where if you received an SMS with emoji in it, it would silently just never show the whole message at all!
[1] http://nition.momentstudio.co.nz/2014/08/the-nokia-n9-alarm-...
(I might say one of the issues with lack of focus was relying too much on desktop linux components, as Android went down a different path, but that's a discussion for another time)
It didn't really matter in either case since IBM and its clones were destroying both of them with Macintosh stealing the non-IBM market share all the same.
The ST failed because the Tramiels didn't really understand software platforms. They got hardware, but when it came to developing an ecosystem that could support developers over a long period of time they just couldn't compete with the likes of Apple and Microsoft (the ST's software team was 10-12 people, and I don't care how good they were, doing a long-term successful platform just wasn't going to happen with a team that small). Coupled with some predatory business practices, the writing was on the wall.
The Magic Sac was more of a curiosity than it was a serious solution to anything. I have a great deal of respect for David Small, but the product was never going to work for the 68020 and up Macs.
When yahoo killed off pipes I found https://github.com/nerevu/riko and realised that the visual aspect of pipes was holding me back.
Having said that, the visual aspect of pipes was what made it easy for me to get into the whole idea of "stream processing". So I have a lot to thank the pipes team for.
And there is Xanadu, the ultimate hypermedia system. It’s a pity that no one (who could fund them) really understood the concept back then and it became vaporware...
1. The brilliant visionary wasn't also a skilled project manager, which is understandable enough, but unfortunately he didn't recognize the issue in time to take steps to either learn the relevant skills or delegate to someone who possessed them.
2. No viable intermediate steps. Version 1.0 insisted on being the whole shebang. They didn't manage to identify an MVP that would've been easier to build while still useful. Berners-Lee, by contrast, did identify such an MVP.
Then Sony pretty much messed it up with NetMD.
Wonderful video about the format: https://youtu.be/kU3BceoMuaA
I think the "it was only a success in Japan" meme is one of those things that people read on the internet and just assume is true because it sounds plausible. In reality they were very popular across Europe, wide parts of Asia, and Australia/NZ (to perhaps a slightly lesser extent) as well.
Anyway the YouTube video above covers all this better than I can.
In Japan, you can still buy blank minidiscs in any normal electronics store.
Wondering whether it was due to lack of demand or operational issues. If it was the latter, that implies the concept might in fact work under a stronger team (or one with deeper pockets).
I’d love to see a company like Spotify try to resurrect it. Or even (shudder) Apple. On the one hand, it’d be a drag to have such a lovely service owned by a corporate behemoth. On the other hand, any losses would basically be couch money for them, and I’d be kinda OK with them mining my music data in exchange.
I made ttdashboard.com which was a live statistics dashboard for turntable.
+1 XMPP - in still finding it puzzling that it's not deployed and used more often
The Supreme Court decision that killed the company is an excellent example of what happens when jurists don't understand technology... And don't want to, either.
Aereo actually had some good arguments, but they were so shady that there was no way anybody was going to believe them when the time came.
I mean, there is a new art form that let you paint in mid air. How are artists not all over this?
https://www.youtube.com/watch?v=HUW49IKs1kE
A technology doesn't have to be something you spend time with everyday to be successful.
I'm only seeing good things about VR gaming, though. It's definitely becoming more popular there. Lots of people seem excited for the Steam Index.
I would say Goro Fujita is a well-known artist for his illustration work and he's now doing almost only VR pieces. https://www.instagram.com/goro.fujita/
FWIW I was really skeptical about VR at the peak of the hype but now I'm waiting on a good opportunity to buy a headset myself.
Any recommendations for self hosted XMPP stuff?
[0] https://landing.google.com/sre/sre-book/chapters/managing-in...
A direct line from $random user to the on call is a recipe for disaster (ie your sres quitting) when you have many users. Engineers aren't first line tech support and those roles shouldn't be confused.
I fully understand what you're saying and mostly agree. Thoughts on having registered users of certain products having access (e.g. Domain purchasers, Google app admins [office? What is that product suite called these days?])?
It disappeared from my phone this week and I'm in shambles.
At least Google keyboard does it now!
But if it's an Android just use settings search?
I can't really describe, but it was better at capturing the words I swiped and also handled multiple languages better.
It was abandoned and later bought out by Pintrest.
http://www.wastedtalent.ca/comic/text-what-i-mean-not-what-i...
If it’s gone that’s one less reason to switch back to Android.
> By mid-2019, KaiOS will be running on over 150 million devices around the world.
If that's true then Firefox OS is quite successful
Although it didn't die yet, it certainly doesn't live up to its potential.
Then you could see tables of what you listened to most, see what your friends listened to, and get recommendations.
I think what happend is that last.fm failed to get deals with the recording companies, while Spotify succeeded (somehow?).
Nowadays I use Spotify like everyone else, but I feel like last.fm gave me much better recommendations. Probably because it had many many years or listening history.
Microsoft's WPF
The HTML based UI ecosystem is just so much richer and better supported than WPF that any theoretical advantages WPF might have are dwarfed by the practical considerations of just build it in Electron and be done with it.
You may be right :-)
OT: At one of my former employers we were building a PLC. The sister team was building the IDE to program the PLC, and the compiler.
All of us were behind schedule. But our colleagues from IDE world staged a presentation for the whole project including top management (owner, CEO etc.) where they showed how far they were.
They showed how they have multiple windows inside the main application window, minimizing and maximizing those. Syntax highlighting. Basically everything Eclipse is giving you for free. Actual business logic: none to be seen.
Now they are working on cross-platform and that's why it had a feature freeze ( + because of graphics). It's now being added in .net core though.
So it's not dead at all
Edit: I’ve used firebase a lot and found it to be a great experience, enabling some of the most rapid product development I’ve ever done. Real-time db, login, cloud functions, and integration with google cloud are all great. Just wondering if there’s something cool or different about parse/buddy worth looking into. Also curious if it was different than firebase and wonder if it died because it wasn’t.
I remember the delight I had when I started using VB4, the immediacy and productivity. WPF is the polar opposite to that.
Zune
- The default keyboard is great.
- Jump Lists: Alphabetical list navigation. (e.g. list of contacts, list of installed apps). For quickly getting to letter 'r', you tap one of the letters to bring up a grid with all the letters, then can easily tap which letter you want to get to. Whereas, iOS has a tiny list of letters on the side. Android sometimes has this tiny list of letters, too. I prefer "1 easy tap, 1 easy tap" is nicer to "1 fine/precise tap".
- Icon-buttons would have labelled text. To save space (I guess), the text was omitted but was still accessible by expanding the menu.
- IIRC, older WP models had a hardware camera button (on the side, for taking pictures or opening the camera app). Later on, the cheaper WP models dropped this.
That said, the lack of apps is what really kills it. :/ e.g. you might only need 2 or 3 apps which you can find on Android or iOS, but not on WP.
iPhone 4 was released before WP7.
It’s a shame, my WP8 phone is still my favorite smart phone ever.
No Google app suite, which Google is absolutely allowed not to make. So Microsoft made the apps for free for Google, google said no, then Microsoft released their own brand clients (e.g. Microsoft YouTube client, Maps, etc) and Google shut it down with lawyers.
Can any platform survive without Google ecosystem support? If Windows Phone was the case study then likely not.
You forget, or I forgive you if you never knew, that google made really good apps on the old Windows Mobile. Google Maps was especially good on WinCE. Then Microsoft declared all Win32 apps dead in favor of a very half baked Silverlight runtime that didn't have such luxury features as sockets or scrolling that actually works. So if I were calling the shots on Google's end at that time, no way I am going to advocate for a massive rewrite onto a runtime that doesn't work well for a very small number of users.
Microsoft's own boneheaded actions killed Google's goodwill for its mobile platform.
Microsoft made the apps for Google, then when that failed released them themselves with no expectation of Google taking over/paying for support. So your point isn't at all relevant to what happened in the Windows Phone situation.
As I said right at the start of my post: Google is fully entitled to refuse to produce apps for Windows Phone. That isn't the problem here, Google effectively blocked their API on that specific platform and their strong market position strangled the platform to death.
The apps that MS made for third parties were rush jobs and poorly maintained over time, and because the Silverlight runtime was not up to the job, performed poorly. They did not well represent their respective brands. They were nowhere near the quality of Google Maps for WinCE circa 2009, to say nothing of how they stood against their contemporary equivalents on iOS and Android.
Would you really want a bad app, that cannot do what your real offerings do, out there representing you, with your name and logo?
The Google apps Microsoft produced worked extremely well right up until the day they got pulled due to legal threats. I'm not sure what this is a reference to.
> because the Silverlight runtime was not up to the job, performed poorly.
XNA ("Silverlight") was only one of the platforms Windows Phone supported. It also had support for Windows Phone App Studio and the Windows Runtime. The Windows Runtime never had poor performing characteristics and was the most popular platform after WP8's release.
> Would you really want a bad app, that cannot do what your real offerings do, out there representing you, with your name and logo?
No, but since that wasn't the reality I don't see the relevance of the question. It is largely a strawman situation where the apps were bad (they weren't), had bad performance (they didn't), and were developed using "Silverlight" (they weren't).
You say you post this information a lot on this site. It is unfortunately you didn't research before the first time you posted it.
I guess the two API and forced hardware changes did most to cement its demise.
Store curation was also an issue with tons of garbage in there that shouldn’t have been allowed.
On the other hand, it would have gotten a -7 rating on the ifixit scale. The hard drive got jostled one too many times and stopped working properly. I've fixed a lot of phones, but the Zune turned out to be unopenable, if that's even a word.
Actually, that's a lie. It did ultimately open, but the casing cracked repeatedly.
The photos app was amazing. Live tiles are amazing. The music player and it's live tile was amazing. The performance was the same whether on a low end budget phone or the top of the line model.
So many good ui and ux decisions like the lack of hamburger menus and placement of all menu items along the bottom of the screen with the extra items being hidden away in a drop-down using ellipsis. System wide light and dark themes jazzed up using an accent color that all of your apps respected.
The People hub (contacts app) was the central point for all social media. Facebook and Twitter were integrated. I didn't need fb messenger. Skype and fb messenger were integrated with the messaging app.
Damn, I wish we made it.
Using geographical location to find digital items way before Ingress and Pokemon Go. The design was gorgeous too.
https://www.ibtimes.co.uk/4bn-mistake-yahoo-bought-precursor...
Amiga achieved quite a lot in terms of engineering for it's time.
Rewarded early participants in music discovery. Clever mechanic.
The hardware was too expensive and bulky, and the software tooling was never really there (I remember someone on the team comparing our dev tools with the newly released Visual Basic).
The first release of the Newton was plagued with bugs (it shipped maybe 4-6 months too early) and had a hardware issue -- noise in the digitizer -- that made its handwriting recognition system perform very badly. Early consumer experience with it wasn't great, and that painted the product with fail and derision; the Doonesbury cartoon was accurate at the time.
A better DOS than DOS
A better Windows than Windows
Microsoft used the OEM tax to force Windows preinstalled than OS/2. Then development dwindled and Microsoft made Visual Studio for Windows.
It is still a good OS and OSFree is trying to open source it.
Beautiful design, great natural light color, engineered to dissipate heat very well (and thus last a long time), they got on the cover of Wired.
However they overdid the packaging and had a hard times convincing people to buy $60 light bulbs and only sold in strange stores.
Last.fm, well. I really miss it.
Windows Phone and especially the Metro Design (although some of it carried into Modern UI).
They were done in by "planned obsolescence"; I haven't watched this video (https://www.youtube.com/watch?v=zdh7_PA8GZU) yet but it has a good ratio.
I can't stand the light from LED or fluorescent light bulbs, and GE can pour themselves a warm bath.
The problem with LEDs is simply that people buy based solely on price. A Yuji high-CRI LED lamp is genuinely indistinguishable from an incandescent lamp, but you'll never see one in a hardware store because they're slightly more expensive.
So far
Google Wave, Pepple Smart Watch, XMPP, Unity, WebOS, Zune, Windows Phone.
I don't see any of these as "great" at all. And they aren't better in any sense. Google Wave might have succeeded if it was aiming at business use case, but for average consumers I doubt anyone are interested, and that is why it was shutted down.
I have yet to see a single consumer who looked at the UX of Zune, Windows Phone, Unity and thought I wish my Android / iPhone has that.
It is the same thing again and again, Engineers, or Nerds are designing what they thought was good, trying to solve problems where consumers don't have or don't care. There are many case of SaaS successes because their market are filled with the people having the same problem in business or Engineering.
iOS does feel like a very dated os these days.
On top of that, the Windows Phone UX was so good in making you aware of everything at a glance. While Android makes you unlock the phone then swipe down to see your notifications, Windows Phone simply got all the info you needed on the home screen. Quicker, simpler, better.
Shame about the apps, yes. Google actively tried to kill Windows Phone by not making apps for it and cutting API access from lots of 3rd party apps. And while the Nokia apps were extremely good (Nokia Cinemagraph was so ahead of its time, seriously), that's not enough to sustain a whole mobile OS in this era of closed apps and walled sites.
I must admit, Angular 1 is productive to me. But its custom directive failed so much for a composition model.
It's a pity, though.
The "Metro" design language of the Zune devices, including the HD, influenced the Windows Phone and other Microsoft products. The Zune was the first device to have the tile layout many miss from the Windows Phone.
Zune Music Pass, an all-you-can-listen monthly music subscription service à la Spotify, was way before its time. I think it was the first such offering ever.
Unfortunately its "app store" had a total of 47 apps. On the plus side, you can install every Zune app ever at once :P
It also runs IE5, I think? Maybe IE6? It barely supported CSS at all.
Path had nice UI innovations that were later merged into other platforms. I guess people prefer a bigger audience over privacy.
https://www.cultofmac.com/144946/path-uploads-and-stores-you...
https://encyclopedia2.thefreedictionary.com/OS%2f2+NT
Also, Wikipedia "OS/2 NT" redirects to Windows NT.
The good news is that if you are feeling particularly nostalgic and have a 16 or 32 bit processor (or emulator), you can relive the OS/2 glory days with ArcaOS from https://www.arcanoae.com/arcaos/ It'll cost you about $130 for a personal license, but if you want it, it's still there, and still supported.
(Still waiting for the x86-64 VMS port to be completed... https://www.vmssoftware.com/products_roadmap.html)
As we all know, transposing each initial by 1 from VMS gets you WNT. Rather like the HAL/IBM Space Odyssey factoid.
Google Wave
The Amiga had true multitasking for a 68K Machine and even ran MS-DOS and MacOS with emulators. Problem is they could only get game makers to write software for the Amiga. The business software, video editing, etc came too late. They still make Amiga systems with PowerPC chips now.
AROS is an open source of AmigaOS 3.1: http://aros.sourceforge.net/
IMHO the final Apple product released before they turned intolerably smug.
I played with it as a sysadmin at work, on a Mac IIfx with thousands of dollars of RAM installed.
Did you ever get to play with the Apple Network Server? A rebadged IBM/6000 box.
Apple's approach to distributed network services was really great...
Alas. This era was like the Xerox Alto -- visionary, but required $10,000 to run.
It ran MacOS7's GUI, and it was as responsive as anything you run today.
Groove Networks [2] a serverless team app.
[1] https://en.wikipedia.org/wiki/FriendFeed
[2] http://www2.sys-con.com/ITSG/virtualcd/WebServices/archives/...
Its ironic since with Docker + Kubernetes, folks essentially are recreating their own PAAS from scratch, but wouldn't use a prebuilt one...
Google Inbox
SGI workstations
Sun NeWS
Tastekid
HaikuOS tries to open source BeOS: https://www.haiku-os.org/
When I first found it, I knew that's the photo backup I need. But when I was ready to pay for it, it was closing down. I thought it'd be a great fit at Amazon. But Alas, some great products don't succeed.
It was the most reliable, solid mobile phone I have ever had. Battery life is really long, talk quality is very good, screen does not crack when you drop it.
* http://blog.darknedgy.net/technology/2015/09/05/0/
I loved Amiga. I still wear Amiga shirts to work, and it was massively influential (I owned a modern-day Video Toaster for streaming, even!) - but IBM was gonna win, especially since they split the marketshare with Atari ST and then Macintosh.
Silverlight
Adobe AIR
I’m not informed enough to know, but it seems like I’ve only heard negative stuff about these.
Then there was the Moonlight knockoff based on Mono. And Mono itself, of course. Dead ends before the project ever started, but they finished and shipped them.
Let's not neglect .Net.
But we're supposed to be talking about good products, not misbegotten ones.
So: Apple Newton!
React Native and Electron carry the torch of this style of development now and both seem to be gaining traction in a way their predecessors couldn't. I like both, but can't help thinking that a UI framework designed as a UI framework would have served us better than CSS and the DOM in the long run.
Put simply: Silverlight/WPF and C# could have been a much better Electron and TypeScript if the runtime were implemented in a less myopic way.
Node is a mess compared to it.
(Someone else already said Google Wave.)
https://www.crowdsupply.com/aeroscope-labs/aeroscope-wireles...
ICQ
They claim to be working on a new version but, in the meantime, the leaked/released beta is a perfectly serviceable version of the software.
Microsoft Encarta
This was replaced by Wikipedia for me, but I really enjoyed reading about stuff without any distraction (read: Internet access at home)
They have been an almost literal life saver for me in 2012-2013.
As I understand it, The Breezy project is an active fork, and is also reportedly compatible with Git file storage:
Excuse me while I go reminisce....
VRML was far too ahead of human thinking, we ended up with a flat web of 2D rather than anything like what came with SGI demo discs back in the day. Frames as in frameset worked really well if you had a VRML world in one screen, the UX was immersive.
I helped my sister get a job with a VRML demo that fitted on a floppy disk. Disks, yeah. Application sent in the post with CV and disk - imagine that. Then imagine the person bothered enough to put disk in machine. Another world.
The VRML had some type of building with bits of my sister's CV in each room, you could click on things to hear stuff, see stuff or read stuff. The trips abroad for her degree were done in this interactive style, the view outside was the general scene of the countryside we grew up in, hobbies and interests were in there too.
She did get the job but never worked on anything as ambitious in this 'interactive media' job as what was on that 1.44Mb disk, even with vast teams. I really like it how VRML gave a glimpse to a future that was never to happen, not due to one's own helplessness but due to the lack of imagination and creativity going on when the rest of the web was flat table layouts. People preferred that to thinking in 'scene graphs'.
SIGH.
"Honeywell is having considerable — and surprising — success with the ultra-secure Multics operating system … Besides 3-5 systems within Honeywell, Multics has been installed or committed within Nippon Electric, Rome Air Development Center, USAF Data Services Center, and Ford" was widely reported in the mid-1970's industry press.
68040 at 33MHz
128MB RAM
4096 color, 1152x832 (or similar) display
that could do Display PostScript and had a relatively complete Unix subsystem under the covers.
The Turbo Cube (same CPU but with the 24/32 bit color NeXT display board) could do full color.
Current minimum specs to be happy on MacOS: dual core 2+ghz CPU, 8GB RAM, SSD drives
Failure or not of NeXT? Not sure.
but i'm afraid that the value of an intermediary-free internet isn't really perceptible enough to drive adoption, even if you made it completely painless.
I meet an awful lot of people, even in tech, that are surprised and shocked that you can use a computer thats not sitting right in front of you. or that two computers sitting next to each other can exchange data without using some third party service.
computing-as-television really won - just like how for the longest time quite a number of people thought that microsoft windows was the canonical definition of what a computer was.
You would get your mail instantly, and could effectively IM on it.
I'm still not even sure how often my iPhone polls or updates, that said it's been a while.
The 'absolute connectivity' of the BB I don't think has been repeated since.
I'm getting sick of features, and honestly I think that's what I want now - a black and white BlackBerry. Just smaller.