WEBVTT - Big Apps that Flopped

0:00:04.440 --> 0:00:12.280
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.320 --> 0:00:15.240
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:15.240 --> 0:00:18.360
<v Speaker 1>I'm an executive producer with iHeart Podcasts and how the

0:00:18.480 --> 0:00:22.040
<v Speaker 1>tech are yet. So, once upon a time, we used

0:00:22.079 --> 0:00:24.880
<v Speaker 1>to have these things called programs. And I say that

0:00:25.000 --> 0:00:28.160
<v Speaker 1>because now we don't call programs programs anymore. We typically

0:00:28.200 --> 0:00:31.760
<v Speaker 1>call programs apps. I think that really started to become

0:00:31.760 --> 0:00:35.680
<v Speaker 1>a thing upon the ascent of the consumer smartphone, which

0:00:35.760 --> 0:00:39.360
<v Speaker 1>was sparked by Apple, which was then cranked up by Android,

0:00:39.840 --> 0:00:42.800
<v Speaker 1>and that we really had the era of the app.

0:00:42.840 --> 0:00:45.239
<v Speaker 1>At that point. We used to, like I said, call

0:00:45.280 --> 0:00:48.839
<v Speaker 1>them programs. Now they are applications, whether it's for a

0:00:48.880 --> 0:00:52.600
<v Speaker 1>phone or a computer. I guess app stores sounds better

0:00:52.680 --> 0:00:57.800
<v Speaker 1>than program emporium anyway. For thousands of entrepreneurs, the dream

0:00:58.080 --> 0:01:00.680
<v Speaker 1>is to build an app and to be come rich

0:01:00.760 --> 0:01:05.800
<v Speaker 1>beyond your wildest dreams. Right, You design an app and

0:01:05.840 --> 0:01:09.040
<v Speaker 1>then the money rolls in. Maybe it's because some bigger

0:01:09.080 --> 0:01:12.920
<v Speaker 1>fish out there, like some Google or Apple or Meta,

0:01:12.959 --> 0:01:16.000
<v Speaker 1>decides that you're just too good to be left unacquired,

0:01:16.319 --> 0:01:19.440
<v Speaker 1>and then they spend a bucket load of cash on you.

0:01:19.840 --> 0:01:23.800
<v Speaker 1>Hopefully ten times more than what you're actually worth. Or

0:01:25.040 --> 0:01:27.720
<v Speaker 1>maybe you actually figure out how to be profitable all

0:01:27.760 --> 0:01:30.399
<v Speaker 1>on your own, you actually have a business plan and

0:01:30.440 --> 0:01:32.840
<v Speaker 1>you have a way of generating revenue. You would be

0:01:32.880 --> 0:01:36.760
<v Speaker 1>the rare Silicon Valley project that actually works as a

0:01:36.880 --> 0:01:42.080
<v Speaker 1>business on its own. That again is the dream. But

0:01:42.200 --> 0:01:45.440
<v Speaker 1>dreams don't always come true, and sometimes even apps that

0:01:45.520 --> 0:01:49.000
<v Speaker 1>seem to be strapped to a rocket for success end

0:01:49.080 --> 0:01:52.080
<v Speaker 1>up blowing up and going up in flames. So this

0:01:52.200 --> 0:01:55.480
<v Speaker 1>episode is about apps that fall into that category, apps

0:01:55.480 --> 0:01:58.440
<v Speaker 1>that at one time seem like they were a sure thing,

0:01:59.000 --> 0:02:01.680
<v Speaker 1>only they flamed out down the line. One of the

0:02:01.720 --> 0:02:04.480
<v Speaker 1>apps I originally planned to put on this list was

0:02:04.640 --> 0:02:08.000
<v Speaker 1>four square, but as it turns out, that app and

0:02:08.040 --> 0:02:12.000
<v Speaker 1>the company behind it is still chugging along, just in

0:02:12.040 --> 0:02:15.000
<v Speaker 1>a slightly different role than it was before. See I

0:02:15.040 --> 0:02:19.080
<v Speaker 1>remember when four square launched and folks would use it

0:02:19.120 --> 0:02:21.960
<v Speaker 1>to check in to locations that they were visiting in

0:02:22.000 --> 0:02:24.680
<v Speaker 1>the real world. So some places would even start to

0:02:24.760 --> 0:02:28.799
<v Speaker 1>offer special discountsl right like twenty percent off your first

0:02:28.880 --> 0:02:32.080
<v Speaker 1>drink if you check into the bar via four square.

0:02:32.360 --> 0:02:35.480
<v Speaker 1>Because it was seen as a kind of viral marketing.

0:02:36.280 --> 0:02:39.560
<v Speaker 1>Other folks worried about the privacy issues of this kind

0:02:39.560 --> 0:02:43.400
<v Speaker 1>of behavior. In fact, some folks created a website called

0:02:43.600 --> 0:02:48.440
<v Speaker 1>Please rob Me, and this site satirically would scrape data

0:02:48.800 --> 0:02:52.519
<v Speaker 1>off Twitter for four square check in notifications, so please

0:02:52.600 --> 0:02:55.040
<v Speaker 1>rob Me would then list people who were saying they

0:02:55.040 --> 0:02:58.360
<v Speaker 1>were not currently at home. Now, the whole point wasn't

0:02:58.400 --> 0:03:02.880
<v Speaker 1>to actually inspire a way of burglaries, but rather show

0:03:03.440 --> 0:03:07.160
<v Speaker 1>why it's dangerous to broadcast your location to the world

0:03:07.200 --> 0:03:09.720
<v Speaker 1>in general, and it might not be a good idea,

0:03:09.800 --> 0:03:14.840
<v Speaker 1>and maybe people should think harder about their personal privacy.

0:03:15.320 --> 0:03:19.760
<v Speaker 1>In twenty fourteen, for Square actually changed dramatically. The company

0:03:19.800 --> 0:03:24.840
<v Speaker 1>launched a companion app called Swarm Now. This app contained

0:03:25.000 --> 0:03:29.000
<v Speaker 1>all the social networking features that for Square used to have,

0:03:29.720 --> 0:03:33.240
<v Speaker 1>so all the check in stuff, all the geolocation stuff

0:03:33.600 --> 0:03:37.520
<v Speaker 1>that was kind of seen as the critical element of

0:03:37.560 --> 0:03:39.440
<v Speaker 1>force Square and the one that you should be worried

0:03:39.480 --> 0:03:42.720
<v Speaker 1>about that went to Swarm. For Square meanwhile became four

0:03:42.800 --> 0:03:46.600
<v Speaker 1>Square City Guide, which became a discovery and recommendation app,

0:03:46.960 --> 0:03:49.080
<v Speaker 1>and it would help you figure out places that maybe

0:03:49.120 --> 0:03:52.160
<v Speaker 1>you should visit based upon your past experiences. Right. It

0:03:52.200 --> 0:03:56.120
<v Speaker 1>would say, Okay, I see that you're in downtown New

0:03:56.240 --> 0:03:59.320
<v Speaker 1>York and because of the places that you used to

0:03:59.360 --> 0:04:02.560
<v Speaker 1>go to in your hometown, here are some places we

0:04:02.640 --> 0:04:05.600
<v Speaker 1>think you should probably check out because you'll really like them.

0:04:06.000 --> 0:04:08.360
<v Speaker 1>You didn't have to use both of the apps if

0:04:08.360 --> 0:04:10.920
<v Speaker 1>you didn't want to, but they did compliment one another,

0:04:11.040 --> 0:04:15.000
<v Speaker 1>so if you used Swarm, four Square would tap into

0:04:15.080 --> 0:04:19.640
<v Speaker 1>that check in data to help inform what recommendations it

0:04:19.680 --> 0:04:23.160
<v Speaker 1>should give you. Those apps are still available today. Like

0:04:23.520 --> 0:04:25.600
<v Speaker 1>I just thought that four Square had come and gone

0:04:25.720 --> 0:04:29.599
<v Speaker 1>because I haven't personally used it in a decade, But

0:04:30.080 --> 0:04:33.600
<v Speaker 1>the fact is it's still a thing. One really interesting

0:04:33.600 --> 0:04:36.880
<v Speaker 1>thing to me is that, forour Square's business largely involves

0:04:37.360 --> 0:04:44.320
<v Speaker 1>licensing its technology to other companies, which include Uber, Airbnb, Snapchat,

0:04:44.440 --> 0:04:47.119
<v Speaker 1>and lots more. The check in feature that four Square

0:04:47.200 --> 0:04:52.039
<v Speaker 1>developed powers numerous other apps. So while our perception was

0:04:52.040 --> 0:04:54.640
<v Speaker 1>that four Square was a relic of the past, that's

0:04:54.720 --> 0:04:59.320
<v Speaker 1>just not true. That's totally my misconception there, and again

0:04:59.360 --> 0:05:01.560
<v Speaker 1>it's because I have really paid at digital four Square

0:05:01.600 --> 0:05:04.120
<v Speaker 1>in a decade. But it is interesting to me that,

0:05:04.440 --> 0:05:08.039
<v Speaker 1>you know, they found success in a different way than

0:05:08.080 --> 0:05:10.479
<v Speaker 1>what they set out to do. I still don't have

0:05:10.520 --> 0:05:14.679
<v Speaker 1>any real desire to read download either four square or Swarm. However,

0:05:15.240 --> 0:05:17.760
<v Speaker 1>on a related note, there is also the story of

0:05:17.880 --> 0:05:21.640
<v Speaker 1>yik yak. Now, this app actually did flame out, but

0:05:21.880 --> 0:05:24.480
<v Speaker 1>then it was resurrected again just a few years ago,

0:05:24.600 --> 0:05:27.279
<v Speaker 1>so for those of y'all who do not know the story,

0:05:27.720 --> 0:05:31.720
<v Speaker 1>a couple of guys launched an anonymous location based messaging

0:05:31.760 --> 0:05:35.279
<v Speaker 1>platform back in twenty thirteen, and the way it worked

0:05:35.640 --> 0:05:38.000
<v Speaker 1>was that you would open the app and you would

0:05:38.080 --> 0:05:41.200
<v Speaker 1>connect via putting in your phone number. This would end

0:05:41.279 --> 0:05:45.200
<v Speaker 1>up allowing you to post to the platform, but you

0:05:45.240 --> 0:05:48.240
<v Speaker 1>would only be able to read messages that had been

0:05:48.240 --> 0:05:51.320
<v Speaker 1>posted by people within a certain distance of your physical location,

0:05:51.440 --> 0:05:54.479
<v Speaker 1>such as within a five mile radius, and you could

0:05:54.520 --> 0:05:57.640
<v Speaker 1>post a message anonymously, and again, only people who are

0:05:57.800 --> 0:06:01.120
<v Speaker 1>in a five mile radius of your lowtion would be

0:06:01.160 --> 0:06:04.120
<v Speaker 1>able to read your message. So as you would travel around,

0:06:04.160 --> 0:06:06.760
<v Speaker 1>you would see new messages, while ones that were now

0:06:06.800 --> 0:06:10.160
<v Speaker 1>out of physical range would disappear from view. The focus

0:06:10.200 --> 0:06:14.760
<v Speaker 1>on geolocation, coupled with anonymity, made the app extremely popular

0:06:14.800 --> 0:06:18.720
<v Speaker 1>with school campuses, and yakyak largely catered to that audience.

0:06:19.360 --> 0:06:23.360
<v Speaker 1>This also meant there was a lot of abuse. There

0:06:23.360 --> 0:06:26.640
<v Speaker 1>was no accountability right there was no connection to a

0:06:26.680 --> 0:06:29.560
<v Speaker 1>specific person, so people could post to the platform and

0:06:29.640 --> 0:06:33.520
<v Speaker 1>they could bully other folks or worse. So there were

0:06:33.560 --> 0:06:36.680
<v Speaker 1>these stories popping up all around the United States about

0:06:36.839 --> 0:06:39.120
<v Speaker 1>how the app was bringing out the absolute worst in

0:06:39.200 --> 0:06:43.640
<v Speaker 1>people and endangering folks. Right Like, let's say that you

0:06:44.279 --> 0:06:49.440
<v Speaker 1>belonged to a minority population in a particular campus university

0:06:49.440 --> 0:06:52.320
<v Speaker 1>of Even if someone's not specifically calling you out, it

0:06:52.400 --> 0:06:54.839
<v Speaker 1>might be easy to figure out who people are talking about,

0:06:54.920 --> 0:06:57.640
<v Speaker 1>which could definitely hurt your mental health, or they could

0:06:57.680 --> 0:07:02.080
<v Speaker 1>even be calling for more extremes that could endanger your

0:07:02.120 --> 0:07:06.760
<v Speaker 1>physical health. So pressure built against the company, and eventually

0:07:06.839 --> 0:07:10.240
<v Speaker 1>yakyak cave to it. So in twenty fifteen, yakyk made

0:07:10.280 --> 0:07:13.440
<v Speaker 1>a massive change and required users to register a handle

0:07:13.800 --> 0:07:17.000
<v Speaker 1>with the site, So all messages now would be attributed

0:07:17.160 --> 0:07:20.400
<v Speaker 1>to a handle. They wouldn't be fully anonymous. Now, it

0:07:20.440 --> 0:07:23.040
<v Speaker 1>was still a handle, not your name, so it wasn't

0:07:23.080 --> 0:07:25.840
<v Speaker 1>exactly the same thing as signing your name to your

0:07:25.880 --> 0:07:28.200
<v Speaker 1>own words, but it was a lot closer than what

0:07:28.320 --> 0:07:33.280
<v Speaker 1>had come before. Hardcore users hated this change, and eventually

0:07:33.320 --> 0:07:35.320
<v Speaker 1>yak yak kind of backed off a bit and made

0:07:35.320 --> 0:07:38.040
<v Speaker 1>it an optional feature, but by then the user base

0:07:38.400 --> 0:07:42.760
<v Speaker 1>had been alienated and had dwindled, and in twenty seventeen,

0:07:42.800 --> 0:07:45.360
<v Speaker 1>the company announced that the app was shutting down due

0:07:45.440 --> 0:07:48.600
<v Speaker 1>to that dwindling user base. They actually did a sell

0:07:48.600 --> 0:07:53.440
<v Speaker 1>off Square, the company that is behind online payment systems.

0:07:53.760 --> 0:07:57.680
<v Speaker 1>They purchased essentially the IP but really more like they

0:07:57.680 --> 0:08:01.320
<v Speaker 1>purchased the engineering talent of Yaka and brought them on board.

0:08:01.680 --> 0:08:04.880
<v Speaker 1>And it was for reportedly like just a million dollars,

0:08:04.920 --> 0:08:06.840
<v Speaker 1>which is still a lot of money. Don't get me wrong.

0:08:06.880 --> 0:08:09.880
<v Speaker 1>A million dollars is a lot, but it's nothing compared

0:08:09.920 --> 0:08:12.920
<v Speaker 1>to what yik yak was valued at a few years earlier.

0:08:13.440 --> 0:08:18.040
<v Speaker 1>And so yik yak effectively stopped being a thing in

0:08:18.040 --> 0:08:22.080
<v Speaker 1>twenty seventeen, and it stayed in the grave for four years.

0:08:22.440 --> 0:08:24.920
<v Speaker 1>But then in February twenty twenty one, a group of

0:08:25.000 --> 0:08:29.520
<v Speaker 1>new owners who remained mysterious and unnamed. Like everywhere I

0:08:29.560 --> 0:08:32.320
<v Speaker 1>look to find out who the heck owned yak yak

0:08:32.640 --> 0:08:35.600
<v Speaker 1>between twenty twenty one and twenty twenty three, didn't have

0:08:35.720 --> 0:08:39.400
<v Speaker 1>information about that anyway, They purchased yik yak and announced

0:08:39.400 --> 0:08:42.040
<v Speaker 1>plans to relaunch, and sure enough, late in the summer

0:08:42.040 --> 0:08:45.280
<v Speaker 1>of twenty twenty one, the app came back. Now two

0:08:45.360 --> 0:08:48.440
<v Speaker 1>years later, in twenty twenty three, another company called side

0:08:48.520 --> 0:08:52.400
<v Speaker 1>Chat scooped up yik yak. Now side chats. Shtick was

0:08:52.480 --> 0:08:54.960
<v Speaker 1>essentially the same as yik yak. Side Chat had an

0:08:55.000 --> 0:09:01.000
<v Speaker 1>anonymous posting platform that largely was targeting college campus side

0:09:01.080 --> 0:09:04.079
<v Speaker 1>Chat was not as popular as yak yak. A lot

0:09:04.120 --> 0:09:07.599
<v Speaker 1>of yak yak users felt that side Chat's user interface

0:09:08.200 --> 0:09:13.199
<v Speaker 1>was inferior, and initially yakyak users were getting messages where

0:09:13.280 --> 0:09:16.560
<v Speaker 1>they were being urged to migrate to side chat and

0:09:16.600 --> 0:09:19.600
<v Speaker 1>they hated it. Eventually that would change, where yak yak

0:09:19.960 --> 0:09:25.280
<v Speaker 1>would remain a thing, but effectively transformed into side chat.

0:09:25.360 --> 0:09:28.000
<v Speaker 1>You know, its interface became more of side Chat's interface.

0:09:28.200 --> 0:09:31.240
<v Speaker 1>By the way, I based this all off of blog

0:09:31.320 --> 0:09:34.679
<v Speaker 1>posts and articles and message boards because I wasn't on

0:09:34.840 --> 0:09:37.280
<v Speaker 1>yik yak at the time, so I had no idea

0:09:37.640 --> 0:09:40.680
<v Speaker 1>what was going on. But while the initial yak yak

0:09:40.760 --> 0:09:44.960
<v Speaker 1>was popular with campuses, this new version specifically focused on

0:09:45.080 --> 0:09:48.360
<v Speaker 1>university students, like almost like exclusively. As opposed to it

0:09:48.400 --> 0:09:50.880
<v Speaker 1>being a community based thing or a regional base thing.

0:09:51.200 --> 0:09:55.640
<v Speaker 1>It was specifically a campus based thing, and occasionally it

0:09:55.800 --> 0:09:58.400
<v Speaker 1>sounds like it would even make mistakes and accidentally assign

0:09:58.480 --> 0:10:01.520
<v Speaker 1>someone to a university that was not the one they

0:10:01.559 --> 0:10:04.720
<v Speaker 1>actually went to, which could be really hairy, right because

0:10:05.080 --> 0:10:07.120
<v Speaker 1>if I were to join yik yak and it suggested

0:10:07.160 --> 0:10:10.040
<v Speaker 1>I was a student at Georgia Tech, that's fighting words

0:10:10.520 --> 0:10:13.600
<v Speaker 1>because I attended the University of Georgia. Now that probably

0:10:13.679 --> 0:10:15.440
<v Speaker 1>means nothing to most of you, but just know those

0:10:15.440 --> 0:10:19.040
<v Speaker 1>two schools have had a long standing rivalry that goes

0:10:19.120 --> 0:10:23.160
<v Speaker 1>between being you know, good natured ribbing and genuine, deep

0:10:23.240 --> 0:10:27.600
<v Speaker 1>seated loathing. So if you had one student misidentified as

0:10:27.640 --> 0:10:30.439
<v Speaker 1>going to the other school, that could be fighting words.

0:10:30.760 --> 0:10:34.480
<v Speaker 1>Now I should say that yaikyak currently is only back

0:10:34.520 --> 0:10:38.679
<v Speaker 1>for iOS users as I record this podcast. Now, the

0:10:38.840 --> 0:10:44.040
<v Speaker 1>relaunch did at one point include Android, and apparently it

0:10:44.080 --> 0:10:47.480
<v Speaker 1>was only active for a very short while before in

0:10:47.520 --> 0:10:50.320
<v Speaker 1>the spring of twenty twenty three, the company said that

0:10:50.360 --> 0:10:53.480
<v Speaker 1>they were shutting down Android support in order to focus

0:10:53.520 --> 0:10:57.439
<v Speaker 1>on building out features for the iOS version. Now, again,

0:10:57.480 --> 0:10:59.680
<v Speaker 1>I can't check this app out. I'm an Android user.

0:10:59.720 --> 0:11:02.000
<v Speaker 1>Plus I'm not a college student, so I have to

0:11:02.040 --> 0:11:04.800
<v Speaker 1>rely on articles and Reddit posts to read up on it.

0:11:04.840 --> 0:11:07.000
<v Speaker 1>And it sounds to me that in the past you

0:11:07.080 --> 0:11:09.720
<v Speaker 1>could register for yik yak just with your phone number,

0:11:10.000 --> 0:11:12.800
<v Speaker 1>but now since the side chat acquisition, you have to

0:11:12.840 --> 0:11:17.320
<v Speaker 1>supply a university email address to create an account university

0:11:17.360 --> 0:11:19.959
<v Speaker 1>or college email address, and if you don't have one

0:11:20.000 --> 0:11:22.160
<v Speaker 1>of those, you can't have an account, and that has

0:11:22.240 --> 0:11:24.720
<v Speaker 1>upset a lot of users because it meant that they're one.

0:11:25.080 --> 0:11:27.120
<v Speaker 1>If they're not in college, they can't be part of

0:11:27.160 --> 0:11:30.760
<v Speaker 1>this anymore. Though honestly, I don't see why you would

0:11:30.840 --> 0:11:33.640
<v Speaker 1>necessarily want to be, But then that's probably because I

0:11:33.640 --> 0:11:36.280
<v Speaker 1>feel a lot of empathy for the folks who were bullied,

0:11:36.600 --> 0:11:39.559
<v Speaker 1>but it also is a reason. One reason they don't

0:11:39.600 --> 0:11:41.800
<v Speaker 1>want to do it anymore is because their actual identity

0:11:41.840 --> 0:11:45.360
<v Speaker 1>would be associated with their account, maybe not directly, like

0:11:45.400 --> 0:11:49.640
<v Speaker 1>the actual posts would be anonymous, but the site would

0:11:49.679 --> 0:11:52.600
<v Speaker 1>know who you were because you would have an email

0:11:52.640 --> 0:11:57.520
<v Speaker 1>address tied to your identity to register for the site. Arguably,

0:11:57.600 --> 0:12:00.360
<v Speaker 1>you could say the same thing is true because for

0:12:00.440 --> 0:12:02.840
<v Speaker 1>the old version, because you had to supply a phone number,

0:12:03.320 --> 0:12:06.599
<v Speaker 1>so unless you're buying burner numbers just for yaekiyak, it

0:12:06.600 --> 0:12:09.600
<v Speaker 1>would be pretty easy to figure out who you were.

0:12:09.920 --> 0:12:11.920
<v Speaker 1>But it also means that if you're not a college student,

0:12:12.040 --> 0:12:14.520
<v Speaker 1>or you're not on faculty or staff, then you're completely

0:12:14.600 --> 0:12:17.200
<v Speaker 1>out of the loop. There's a lot of competition in

0:12:17.240 --> 0:12:20.160
<v Speaker 1>the anonymous message board space these days. Seems to me

0:12:20.240 --> 0:12:22.880
<v Speaker 1>that a lot of the companies behind these apps typically

0:12:22.960 --> 0:12:26.000
<v Speaker 1>will reach a level of success that brings more attention

0:12:26.720 --> 0:12:32.000
<v Speaker 1>to their activities and perhaps their flaws, let's say, and

0:12:32.040 --> 0:12:35.040
<v Speaker 1>then they feel pressure to change things in order to

0:12:35.040 --> 0:12:37.880
<v Speaker 1>make their apps less prone to abuse, because now people

0:12:37.920 --> 0:12:40.680
<v Speaker 1>are paying attention to them and calling them out. And

0:12:40.720 --> 0:12:44.800
<v Speaker 1>then subsequently, after making these changes, the apps decline in

0:12:44.840 --> 0:12:48.240
<v Speaker 1>popularity because it turns out the user base the stuff

0:12:48.280 --> 0:12:50.640
<v Speaker 1>that they really liked happened to be the same stuff

0:12:50.640 --> 0:12:54.920
<v Speaker 1>that also facilitated abuse. Not to say that users all

0:12:55.200 --> 0:12:59.000
<v Speaker 1>enjoyed and piling on folks and abusing people, but that

0:12:59.120 --> 0:13:03.480
<v Speaker 1>the same features that made it easy to abuse folks

0:13:03.480 --> 0:13:07.160
<v Speaker 1>were also the features that people just really liked. That

0:13:07.240 --> 0:13:08.880
<v Speaker 1>kind of seems to be the life cycle for these

0:13:08.960 --> 0:13:12.360
<v Speaker 1>kinds of applications. They launch, they go viral, they get

0:13:12.400 --> 0:13:16.720
<v Speaker 1>really big, folks notice that sometimes really awful people are

0:13:16.840 --> 0:13:19.880
<v Speaker 1>using that app to do really awful things. The app

0:13:20.040 --> 0:13:23.440
<v Speaker 1>then ends up making changes in an effort to not

0:13:23.880 --> 0:13:26.920
<v Speaker 1>be held accountable for these things, and then it alienates

0:13:26.960 --> 0:13:29.400
<v Speaker 1>the user base, both the good and the bad users.

0:13:29.640 --> 0:13:32.720
<v Speaker 1>It then declines in popularity, then it fades into memory,

0:13:32.840 --> 0:13:35.160
<v Speaker 1>your rentse and you repeat. Now, I can't say for

0:13:35.200 --> 0:13:37.319
<v Speaker 1>certain that's what's happening with Yak Yak. There are a

0:13:37.360 --> 0:13:39.160
<v Speaker 1>lot of users who say that it's not as good

0:13:39.160 --> 0:13:42.360
<v Speaker 1>as it used to be, that they don't see the appeal.

0:13:42.480 --> 0:13:45.280
<v Speaker 1>The fact that it doesn't it's not available for Android

0:13:45.360 --> 0:13:47.680
<v Speaker 1>users is a huge thing. It means that a large

0:13:47.880 --> 0:13:50.720
<v Speaker 1>amount of the population can't even access it. Maybe the

0:13:50.760 --> 0:13:54.520
<v Speaker 1>company will manage to relaunch for Android and regain some momentum,

0:13:54.640 --> 0:13:58.240
<v Speaker 1>or maybe it's on the path back toward obsolescence. Okay,

0:13:58.440 --> 0:14:01.040
<v Speaker 1>we've got more failed app to talk about. Before we

0:14:01.080 --> 0:14:14.040
<v Speaker 1>do that, let's stop for a moment and thank our sponsors. Okay,

0:14:14.040 --> 0:14:17.880
<v Speaker 1>we're back. So no list of failed apps would be

0:14:17.920 --> 0:14:25.040
<v Speaker 1>complete without Quibi. Holy cats. This was a massive whiff

0:14:25.400 --> 0:14:28.560
<v Speaker 1>with a whole lot of money and some really heavy

0:14:28.600 --> 0:14:32.400
<v Speaker 1>hitters in both the entertainment and tech industries at the wheel,

0:14:32.520 --> 0:14:36.760
<v Speaker 1>and it still crashed and burned. It was the brainchild

0:14:36.880 --> 0:14:41.280
<v Speaker 1>of Jeffrey Katzenberg, who had forged a legendary career in Hollywood.

0:14:41.680 --> 0:14:44.880
<v Speaker 1>You know, he became really well known at Disney and

0:14:44.920 --> 0:14:48.520
<v Speaker 1>then created dream Works, and Quibi was hoping to tap

0:14:48.600 --> 0:14:53.680
<v Speaker 1>into that same magic that Hollywood success and also the

0:14:53.720 --> 0:14:57.840
<v Speaker 1>same magic that TikTok boasts. That was the key was

0:14:58.320 --> 0:15:02.440
<v Speaker 1>can we make something inspired by the success of TikTok,

0:15:02.920 --> 0:15:06.120
<v Speaker 1>and that was namely short form content, And in the

0:15:06.160 --> 0:15:08.760
<v Speaker 1>case of Quibi, the short form would be videos that

0:15:08.800 --> 0:15:13.520
<v Speaker 1>would last ten minutes or less. However, unlike TikTok, Quibi

0:15:13.560 --> 0:15:17.160
<v Speaker 1>productions would have some serious money behind them. We're talking

0:15:17.240 --> 0:15:20.960
<v Speaker 1>about really high production values, stuff that you would see

0:15:21.280 --> 0:15:24.680
<v Speaker 1>that would be akin to a television or film studio.

0:15:25.240 --> 0:15:28.640
<v Speaker 1>And if TikTok can knock them dead with DIY shorts

0:15:28.680 --> 0:15:32.240
<v Speaker 1>created by just any Yahoo out there, surely an entertainment

0:15:32.280 --> 0:15:37.760
<v Speaker 1>app with serious Hollywood credentials could make a killing right now.

0:15:37.800 --> 0:15:42.120
<v Speaker 1>On the tech side, former HP CEO Meg Whitman was

0:15:42.120 --> 0:15:46.000
<v Speaker 1>on board, and Whitman and Katzenberg brainstormed the structure and

0:15:46.080 --> 0:15:50.640
<v Speaker 1>execution of Quibi. They also are argued a lot. Witman

0:15:50.680 --> 0:15:54.720
<v Speaker 1>would later essentially say that Katzenberg would undermine her decisions

0:15:54.720 --> 0:15:56.920
<v Speaker 1>and was micromanaging, and there seem to be a lot

0:15:56.920 --> 0:16:00.240
<v Speaker 1>of bad blood at the top levels at Quibi, which

0:16:00.280 --> 0:16:03.640
<v Speaker 1>was just one of many problems. But the company signed

0:16:03.640 --> 0:16:09.600
<v Speaker 1>on various actors, directors, writers, and associated people to create

0:16:09.800 --> 0:16:15.120
<v Speaker 1>content for the site. They poured approximately a billion dollars

0:16:15.600 --> 0:16:19.400
<v Speaker 1>to that effect. Some of the content created consisted of

0:16:19.480 --> 0:16:22.200
<v Speaker 1>standalone short videos right like it was just a one

0:16:22.240 --> 0:16:25.880
<v Speaker 1>and done ten minutes or less video, but some were

0:16:25.920 --> 0:16:29.680
<v Speaker 1>actually serialized. They were longer pieces and divided up into

0:16:29.720 --> 0:16:32.520
<v Speaker 1>ten minute long chapters. This, in turn was a really

0:16:32.600 --> 0:16:35.720
<v Speaker 1>tricky because, like, if you're gonna divide a movie into

0:16:35.720 --> 0:16:38.640
<v Speaker 1>ten minute long chapters, you need a way to entice

0:16:38.680 --> 0:16:42.160
<v Speaker 1>people to continue after a chapter is over, and in

0:16:42.200 --> 0:16:45.120
<v Speaker 1>my opinion, it becomes like a Dan Brown novel where

0:16:45.200 --> 0:16:49.560
<v Speaker 1>every chapter ends in a cliffhanger to try and incentivize

0:16:49.560 --> 0:16:52.920
<v Speaker 1>people to go to the next chapter. And personally, I

0:16:53.040 --> 0:16:57.960
<v Speaker 1>find that kind of narrative exhausting and not very satisfying.

0:16:58.560 --> 0:17:01.920
<v Speaker 1>I am not a Dan Brown fan, nothing against him,

0:17:02.200 --> 0:17:05.080
<v Speaker 1>I just it doesn't appeal to me to end every

0:17:05.400 --> 0:17:09.320
<v Speaker 1>few pages with another cliffhanger. Anyway, they also made a

0:17:09.359 --> 0:17:13.639
<v Speaker 1>really odd decision when it came to framing, because the

0:17:13.680 --> 0:17:16.720
<v Speaker 1>whole point of Quibi was that it was intended to

0:17:16.760 --> 0:17:20.320
<v Speaker 1>be consumed on smartphones, and as I'm sure you're aware,

0:17:20.480 --> 0:17:24.520
<v Speaker 1>we're used to watching television programs in landscape format, that is,

0:17:25.000 --> 0:17:28.919
<v Speaker 1>the picture is wider than it is tall, right, But

0:17:29.000 --> 0:17:33.200
<v Speaker 1>for phones, we often hold phones in portrait mode, where

0:17:33.240 --> 0:17:36.560
<v Speaker 1>it's taller than it is wide. Otherwise you have to

0:17:36.640 --> 0:17:40.199
<v Speaker 1>turn the dang phone on its side, and there's a

0:17:40.280 --> 0:17:42.880
<v Speaker 1>chance you'll end up watching a tiny video with huge

0:17:42.880 --> 0:17:46.200
<v Speaker 1>black bars above and below it. So one choice Quibi's

0:17:46.240 --> 0:17:50.119
<v Speaker 1>founders made is that all content should be viewable in

0:17:50.240 --> 0:17:53.359
<v Speaker 1>full screen, whether the user was holding their phone in

0:17:53.440 --> 0:17:55.960
<v Speaker 1>portrait or landscape mode, and that you could switch back

0:17:56.000 --> 0:17:58.720
<v Speaker 1>and forth. So you could hold it in portrait mode

0:17:58.920 --> 0:18:00.240
<v Speaker 1>and then say you know what, I want to see

0:18:00.280 --> 0:18:03.760
<v Speaker 1>this in wide screen, turn your phone landscape. It would switch,

0:18:03.800 --> 0:18:07.760
<v Speaker 1>and in both versions the image would completely fill the

0:18:07.800 --> 0:18:10.640
<v Speaker 1>screen of your phone. That's a big deal, even though

0:18:10.680 --> 0:18:12.760
<v Speaker 1>it might not sound like it, because if you're a

0:18:12.800 --> 0:18:16.760
<v Speaker 1>director or cinematographer, part of your job is making sure

0:18:16.920 --> 0:18:21.200
<v Speaker 1>all the important information for the viewer is available within

0:18:21.280 --> 0:18:24.440
<v Speaker 1>the frame. Obviously that's going to be different if the

0:18:24.480 --> 0:18:27.560
<v Speaker 1>finished product is to be viewed in portrait mode rather

0:18:27.640 --> 0:18:30.040
<v Speaker 1>than landscape you need to figure out how are you

0:18:30.080 --> 0:18:32.400
<v Speaker 1>going to frame the image so that it works in

0:18:32.480 --> 0:18:35.080
<v Speaker 1>both formats, or you might have to use things like

0:18:35.240 --> 0:18:38.879
<v Speaker 1>pan and scan or switching views to get the information across. Right, Like,

0:18:38.920 --> 0:18:41.520
<v Speaker 1>you might have a scene where you have two characters,

0:18:41.560 --> 0:18:44.280
<v Speaker 1>one far left and one far right on the screen.

0:18:44.640 --> 0:18:48.200
<v Speaker 1>They're talking to each other, and in landscape mode, that's fine,

0:18:48.480 --> 0:18:50.439
<v Speaker 1>you can see it, but you switch it to portrait

0:18:50.480 --> 0:18:52.960
<v Speaker 1>mode and now there's not enough room on the screen

0:18:53.160 --> 0:18:56.160
<v Speaker 1>to get both characters in frame. What do you do?

0:18:56.160 --> 0:18:59.600
<v Speaker 1>Do you have an empty frame where both characters are

0:18:59.600 --> 0:19:02.360
<v Speaker 1>off screen, one off screen left and one off screen right.

0:19:02.600 --> 0:19:04.560
<v Speaker 1>Do you just focus on one character and then you

0:19:04.640 --> 0:19:08.639
<v Speaker 1>switch whenever the dialogue changes so that you get a

0:19:08.680 --> 0:19:12.359
<v Speaker 1>different view when character one speaks versus character two? Do

0:19:12.440 --> 0:19:15.719
<v Speaker 1>you pan back and forth? Which is that swimmy effect

0:19:15.760 --> 0:19:19.200
<v Speaker 1>you often get if you watch like old old home video,

0:19:19.760 --> 0:19:21.800
<v Speaker 1>not home video, but you know videos that were made

0:19:21.800 --> 0:19:25.959
<v Speaker 1>for home video use. You will often get that scanning feature.

0:19:26.000 --> 0:19:28.640
<v Speaker 1>Because televisions were in the old four to three aspect

0:19:28.720 --> 0:19:33.119
<v Speaker 1>ratio and they couldn't incorporate a wide screen picture unless

0:19:33.160 --> 0:19:35.560
<v Speaker 1>they did the bars at the top or bottom or both,

0:19:35.920 --> 0:19:37.679
<v Speaker 1>and a lot of people hated those. They wanted to

0:19:37.720 --> 0:19:39.720
<v Speaker 1>have the image take up the whole screen, So you

0:19:39.800 --> 0:19:45.280
<v Speaker 1>end up having this digital panning, which I absolutely detested. Well,

0:19:45.280 --> 0:19:47.919
<v Speaker 1>you have to make those decisions, or do you end

0:19:48.040 --> 0:19:51.600
<v Speaker 1>up blocking all of your shots so that all the

0:19:52.119 --> 0:19:55.600
<v Speaker 1>relevant information can be seen in one view, even if

0:19:55.600 --> 0:19:57.679
<v Speaker 1>it's portrait, in which case you might just have a

0:19:57.680 --> 0:20:01.119
<v Speaker 1>lot of unused space, like negative space in the frame

0:20:01.160 --> 0:20:03.680
<v Speaker 1>if you're watching it widescreen, or maybe you shoot with

0:20:03.760 --> 0:20:07.119
<v Speaker 1>multiple cameras so that way, one camera is taking the

0:20:07.200 --> 0:20:11.200
<v Speaker 1>landscape version of the shot, one camera's taking the portrait

0:20:11.280 --> 0:20:14.120
<v Speaker 1>version of the shot. Like, there's a lot of complex

0:20:14.400 --> 0:20:16.320
<v Speaker 1>things you have to think of behind the scenes from

0:20:16.359 --> 0:20:21.160
<v Speaker 1>a content creator standpoint, beyond just the technology of if

0:20:21.200 --> 0:20:23.800
<v Speaker 1>you turn your phone, you want the frame to be

0:20:23.880 --> 0:20:28.000
<v Speaker 1>completely full. So this was a real issue that goes

0:20:28.040 --> 0:20:31.000
<v Speaker 1>a technical challenge, and they did not have enough time

0:20:31.400 --> 0:20:32.960
<v Speaker 1>to figure out how to deal with that in a

0:20:33.000 --> 0:20:36.800
<v Speaker 1>way that was satisfying anyway. That whole design decision became

0:20:36.880 --> 0:20:39.600
<v Speaker 1>a big hurdle. But another hurdle was that Quibi was

0:20:39.640 --> 0:20:42.159
<v Speaker 1>meant to be mobile only by design. It was not

0:20:42.280 --> 0:20:45.399
<v Speaker 1>intended to be an app that you would access on

0:20:45.480 --> 0:20:49.199
<v Speaker 1>a computer or smart television or streaming box or anything

0:20:49.280 --> 0:20:53.239
<v Speaker 1>like that, and something that was outside the control and

0:20:53.320 --> 0:20:55.679
<v Speaker 1>not predicted by the folks at Quibi when they were

0:20:55.720 --> 0:20:59.560
<v Speaker 1>putting together their business plan was the COVID nineteen pandemic,

0:20:59.600 --> 0:21:02.679
<v Speaker 1>which took a lot of us totally by surprise. So

0:21:02.800 --> 0:21:06.720
<v Speaker 1>Quibi was really intended to be used for a world

0:21:06.760 --> 0:21:09.320
<v Speaker 1>that was on the go, right. The use case was

0:21:09.359 --> 0:21:11.879
<v Speaker 1>that you would be out in the real world and

0:21:11.920 --> 0:21:14.600
<v Speaker 1>you would have time to kill. Maybe you're waiting in

0:21:14.600 --> 0:21:16.879
<v Speaker 1>line of the bank, or maybe you're sitting on a

0:21:16.920 --> 0:21:18.840
<v Speaker 1>subway and you're on your way to work and you

0:21:18.960 --> 0:21:22.240
<v Speaker 1>just need something to distract you from the tedium of life.

0:21:22.800 --> 0:21:26.160
<v Speaker 1>Boom Quib is there to save the day. High production

0:21:26.320 --> 0:21:30.840
<v Speaker 1>value scripted entertainment or you know, like game shows or whatever,

0:21:30.920 --> 0:21:33.520
<v Speaker 1>but still high production value, not the type of stuff

0:21:33.560 --> 0:21:37.639
<v Speaker 1>you would see typically on a site like TikTok. Except

0:21:37.640 --> 0:21:39.840
<v Speaker 1>the app launched just as the world was shutting down

0:21:39.920 --> 0:21:42.480
<v Speaker 1>and going into quarantine in twenty twenty, so the use

0:21:42.520 --> 0:21:45.400
<v Speaker 1>case for the app was no longer relevant, at least

0:21:45.440 --> 0:21:48.840
<v Speaker 1>not for the several first months of the app's existence.

0:21:49.320 --> 0:21:52.320
<v Speaker 1>Plenty of critics said that even without the pandemic, Quibi

0:21:52.359 --> 0:21:55.320
<v Speaker 1>would have just totally failed, But certainly the lockdown was

0:21:55.400 --> 0:21:58.160
<v Speaker 1>a massive blow to the service when there were plenty

0:21:58.240 --> 0:22:01.080
<v Speaker 1>of other options folks could act when they were at home.

0:22:01.440 --> 0:22:05.560
<v Speaker 1>Why use Quibi if you have access to Netflix or

0:22:05.680 --> 0:22:08.800
<v Speaker 1>one of the billion other streaming services that are out

0:22:08.840 --> 0:22:12.240
<v Speaker 1>there now. The Verge has an article going through other

0:22:12.320 --> 0:22:16.919
<v Speaker 1>reasons why Quibi flopped. The writer Julia Alexander argues in

0:22:16.960 --> 0:22:19.760
<v Speaker 1>that piece that one big reason is that none of

0:22:19.760 --> 0:22:23.280
<v Speaker 1>the shows on Quibbi were particularly good, and that is

0:22:23.280 --> 0:22:25.879
<v Speaker 1>a really tough problem. It is hard to convince folks

0:22:25.920 --> 0:22:29.640
<v Speaker 1>to flock to your streaming service if the stuff you're

0:22:29.680 --> 0:22:35.000
<v Speaker 1>streaming isn't very entertaining or compelling. Alexander actually says, quote

0:22:35.400 --> 0:22:39.280
<v Speaker 1>most titles felt like jokes straight out of thirty Rock

0:22:39.680 --> 0:22:42.200
<v Speaker 1>end quoteff if you don't know what that means. Thirty

0:22:42.280 --> 0:22:47.399
<v Speaker 1>Rock was this sitcom, a satirical sitcom about creating a

0:22:48.160 --> 0:22:51.920
<v Speaker 1>late night comedy variety show a kin to Saturday Night Live.

0:22:52.400 --> 0:22:57.000
<v Speaker 1>And often the show was joking about different shows that

0:22:57.080 --> 0:23:00.600
<v Speaker 1>the network was launching, and they were always ridiculous, and

0:23:01.200 --> 0:23:03.200
<v Speaker 1>you know, you would never really expect to see such

0:23:03.200 --> 0:23:06.200
<v Speaker 1>a show in the real world well, Quibi apparently brought

0:23:06.200 --> 0:23:10.200
<v Speaker 1>those kinds of shows to the real world. Initially, Quibi

0:23:10.320 --> 0:23:13.240
<v Speaker 1>offered a free subscription for a few months to early users,

0:23:13.320 --> 0:23:16.199
<v Speaker 1>kind of a trial period, but once that trial period

0:23:16.280 --> 0:23:19.200
<v Speaker 1>ran out, users were then given the option to subscribe

0:23:19.240 --> 0:23:21.680
<v Speaker 1>to the service either for five dollars a month, which

0:23:21.760 --> 0:23:25.359
<v Speaker 1>was an ad supported experience, or eight dollars a month

0:23:25.560 --> 0:23:27.960
<v Speaker 1>if you wanted to be free of ads. But since,

0:23:28.119 --> 0:23:32.280
<v Speaker 1>as Alexander points out, there really wasn't much compelling content

0:23:32.480 --> 0:23:36.160
<v Speaker 1>on the streaming service, most folks declined the offer once

0:23:36.200 --> 0:23:38.600
<v Speaker 1>it stopped being free. They're like, that's it, I'm out,

0:23:38.640 --> 0:23:41.840
<v Speaker 1>there's nothing here to keep me here. Julia Alexander also

0:23:41.960 --> 0:23:45.040
<v Speaker 1>argues that Quibi was doomed even if there had never

0:23:45.080 --> 0:23:49.600
<v Speaker 1>been a pandemic, and it's quite possible that she was right, because,

0:23:49.600 --> 0:23:53.120
<v Speaker 1>as we do know, Katzenberg and Whitman were at odds

0:23:53.160 --> 0:23:56.600
<v Speaker 1>with each other. There was a lack of good content

0:23:56.760 --> 0:24:00.680
<v Speaker 1>on Quibi. There were a lot of other competing services

0:24:00.760 --> 0:24:03.240
<v Speaker 1>already out there, and there weren't a lot of good

0:24:03.320 --> 0:24:07.040
<v Speaker 1>arguments to say, why use Quibi when there are these

0:24:07.080 --> 0:24:11.879
<v Speaker 1>other alternatives? Right, And to Alexander's point, the people at

0:24:11.920 --> 0:24:15.800
<v Speaker 1>Quibi never really settled on what Quibi actually was, or

0:24:15.800 --> 0:24:18.919
<v Speaker 1>what it was for, or what its mission was. And

0:24:18.960 --> 0:24:22.080
<v Speaker 1>because there was this lack of clarity, there was really

0:24:22.240 --> 0:24:26.600
<v Speaker 1>little chance of success. Now we'll never know if Quibi

0:24:26.640 --> 0:24:29.359
<v Speaker 1>would have succeeded had there not been a pandemic, or

0:24:29.400 --> 0:24:31.760
<v Speaker 1>if it would have survived, but we do know that

0:24:31.840 --> 0:24:34.720
<v Speaker 1>Quibi launched on April sixth, twenty twenty, and it was

0:24:34.760 --> 0:24:37.960
<v Speaker 1>shut down by December of twenty twenty. It didn't even

0:24:38.000 --> 0:24:40.760
<v Speaker 1>make it a full year. And considering how much money

0:24:40.920 --> 0:24:44.000
<v Speaker 1>was behind that app, like, remember, this is an app

0:24:44.280 --> 0:24:48.000
<v Speaker 1>that spent a billion dollars just on the content, that's

0:24:48.000 --> 0:24:51.080
<v Speaker 1>not even on the engineering or anything else. Well, that's

0:24:51.119 --> 0:24:55.760
<v Speaker 1>a massive flop, like big time flop in the tech world.

0:24:56.160 --> 0:24:58.640
<v Speaker 1>And while we're on the subject of short form entertainment,

0:24:58.760 --> 0:25:02.520
<v Speaker 1>let's talk about a pre sir to TikTok, something that

0:25:02.720 --> 0:25:08.679
<v Speaker 1>kind of was forging the path that other services like

0:25:08.760 --> 0:25:12.359
<v Speaker 1>TikTok or Instagram reels would follow. And I'm talking about

0:25:12.440 --> 0:25:16.480
<v Speaker 1>the venerable and missed app Vine, at least it's missed

0:25:16.520 --> 0:25:21.000
<v Speaker 1>by some people, including me. So in twenty twelve, Don Hoffman,

0:25:21.359 --> 0:25:27.880
<v Speaker 1>Colin Kroll, and Russ Yusopov developed and launched the app Vine. Now,

0:25:27.920 --> 0:25:30.600
<v Speaker 1>for those of y'all who have never experienced Vine, it

0:25:30.760 --> 0:25:36.800
<v Speaker 1>was a short form video app where you could record

0:25:36.960 --> 0:25:40.040
<v Speaker 1>and then post a six second video clip and it

0:25:40.080 --> 0:25:43.520
<v Speaker 1>would automatically loop once it reached the end, so it

0:25:43.520 --> 0:25:46.439
<v Speaker 1>would play out the six seconds or however long it was.

0:25:46.480 --> 0:25:48.880
<v Speaker 1>It could be less than six seconds, and then once

0:25:48.880 --> 0:25:50.440
<v Speaker 1>it was at the end, it would start over again

0:25:50.560 --> 0:25:53.680
<v Speaker 1>until you scrolled to the next you know, Vine. And

0:25:53.720 --> 0:25:58.240
<v Speaker 1>this made the app ideal for meme worthy content, so

0:25:58.280 --> 0:26:01.800
<v Speaker 1>it was great for stuff like pranks or funny visual gags,

0:26:02.240 --> 0:26:05.680
<v Speaker 1>or amazing feats of skill, like if someone was, you know,

0:26:06.040 --> 0:26:11.480
<v Speaker 1>shooting a basketball from half court and sinking it perfectly

0:26:11.520 --> 0:26:16.000
<v Speaker 1>nothing but net perfect Vine, right. And it also meant

0:26:16.040 --> 0:26:18.840
<v Speaker 1>that folks started to get really creative. They started to

0:26:18.880 --> 0:26:21.720
<v Speaker 1>look at Vine as sort of a challenging platform and

0:26:21.760 --> 0:26:24.679
<v Speaker 1>they wanted to create content specifically for it, and they

0:26:24.680 --> 0:26:29.920
<v Speaker 1>would create six second long stories, typically comedic. Right. You'd

0:26:29.960 --> 0:26:32.760
<v Speaker 1>have a setup and then a punchline and it would

0:26:32.760 --> 0:26:35.920
<v Speaker 1>all take place in six seconds, but sometimes it would

0:26:35.960 --> 0:26:39.520
<v Speaker 1>include things like scene changes. This was not easy to

0:26:39.560 --> 0:26:42.760
<v Speaker 1>do in Vine because there were no real editing tools

0:26:42.920 --> 0:26:46.119
<v Speaker 1>to speak of. Within the app, you could record, then

0:26:46.160 --> 0:26:49.320
<v Speaker 1>you could pause recording, and then you could start recording again.

0:26:49.640 --> 0:26:52.600
<v Speaker 1>But you had just that six seconds to do everything,

0:26:52.960 --> 0:26:56.000
<v Speaker 1>and you couldn't cut and edit clips together. So if

0:26:56.000 --> 0:26:58.320
<v Speaker 1>you had like a really good take in the first

0:26:58.320 --> 0:27:01.800
<v Speaker 1>three seconds of one verse and a really good conclusion

0:27:02.160 --> 0:27:04.479
<v Speaker 1>in the last three seconds of another version, you couldn't

0:27:04.480 --> 0:27:07.040
<v Speaker 1>pair those together. You had to get it all done

0:27:07.280 --> 0:27:09.639
<v Speaker 1>in one go, which meant if you made a mistake,

0:27:09.680 --> 0:27:13.480
<v Speaker 1>your options were either post the imperfect version or keep

0:27:13.520 --> 0:27:17.360
<v Speaker 1>trying till you got it right. Even so, with these restrictions,

0:27:17.480 --> 0:27:21.080
<v Speaker 1>folks flocked to Vine to make some pretty amazing short videos,

0:27:21.480 --> 0:27:23.960
<v Speaker 1>and they ranged all over the place. I mostly think

0:27:23.960 --> 0:27:26.200
<v Speaker 1>of the comedic ones, but there were other ones too.

0:27:26.240 --> 0:27:28.320
<v Speaker 1>There were some that weren't, you know, comedic. They were

0:27:28.320 --> 0:27:31.640
<v Speaker 1>like heartwarming or you know, they might make you weepy,

0:27:31.840 --> 0:27:35.920
<v Speaker 1>depending upon the content. Vine was a phenomenon shortly after

0:27:36.000 --> 0:27:39.080
<v Speaker 1>launching in June of twenty twelve, and it was enough

0:27:39.080 --> 0:27:42.320
<v Speaker 1>to convince Twitter to acquire the company in October of

0:27:42.440 --> 0:27:46.800
<v Speaker 1>twenty twelve for thirty million smackaroos, which is not bad

0:27:46.920 --> 0:27:50.800
<v Speaker 1>for a newly launched app. A couple of years later,

0:27:50.880 --> 0:27:54.840
<v Speaker 1>in twenty fourteen, some successful Vine creators all banded together

0:27:54.920 --> 0:27:57.639
<v Speaker 1>to move into an apartment complex which became kind of

0:27:57.680 --> 0:28:02.280
<v Speaker 1>a ragtag collaborative studio in a sense, and they found

0:28:02.280 --> 0:28:06.080
<v Speaker 1>further exposure on mainstream media. Like their success on Vine

0:28:06.280 --> 0:28:11.119
<v Speaker 1>translated to larger platforms like classic ones on television. But

0:28:11.240 --> 0:28:14.280
<v Speaker 1>even by twenty fourteen, things were starting to get rocky

0:28:14.560 --> 0:28:17.719
<v Speaker 1>for Vine. One major reason is that Vine was in

0:28:17.800 --> 0:28:22.520
<v Speaker 1>trouble due to hefty competition. You see, the same year

0:28:23.080 --> 0:28:26.600
<v Speaker 1>that Vine launched, back in twenty twelve, Meta which at

0:28:26.600 --> 0:28:30.639
<v Speaker 1>that point was just known as Facebook, acquired Instagram for

0:28:30.800 --> 0:28:35.080
<v Speaker 1>a billion smack a roos. That's really a princely sum.

0:28:35.400 --> 0:28:38.760
<v Speaker 1>And then in twenty thirteen, Instagram introduced the ability to

0:28:38.760 --> 0:28:41.720
<v Speaker 1>post video clips of up to fifteen seconds in length,

0:28:41.920 --> 0:28:45.880
<v Speaker 1>so already more than twice as long as a Vine.

0:28:46.360 --> 0:28:49.840
<v Speaker 1>Instagram also already had a huge user base, which was

0:28:49.840 --> 0:28:53.400
<v Speaker 1>made even larger by Facebook's integration, and it took a

0:28:53.440 --> 0:28:56.920
<v Speaker 1>big old gulp of Vine's milkshake as a result. Now,

0:28:57.040 --> 0:29:00.440
<v Speaker 1>this move should not have surprised anyone, because even back then,

0:29:00.560 --> 0:29:04.760
<v Speaker 1>Facebook already had a reputation for scooping up companies that

0:29:04.960 --> 0:29:09.000
<v Speaker 1>could otherwise distract Facebook users. Instagram was actually a great

0:29:09.040 --> 0:29:12.480
<v Speaker 1>example of this. Instagram was one of those acquisitions where

0:29:12.600 --> 0:29:15.680
<v Speaker 1>Facebook says, Oh, this other app is starting to get

0:29:15.680 --> 0:29:19.200
<v Speaker 1>people's attention, which means their attention isn't on our website,

0:29:19.200 --> 0:29:21.800
<v Speaker 1>which means we're not making money from them. I don't

0:29:21.880 --> 0:29:25.200
<v Speaker 1>like that. Let's fix it. And Facebook typically had one

0:29:25.200 --> 0:29:27.560
<v Speaker 1>of two ways that they would fix this problem. They

0:29:27.640 --> 0:29:33.880
<v Speaker 1>would buy the company and incorporate it into Facebook's corporate structure,

0:29:34.000 --> 0:29:37.320
<v Speaker 1>and thus it became a bonus. It was adding to

0:29:37.360 --> 0:29:41.040
<v Speaker 1>Facebook's value. It was no longer taking away. Or they

0:29:41.080 --> 0:29:46.880
<v Speaker 1>could copy it, and if they copied it, then they

0:29:46.920 --> 0:29:52.680
<v Speaker 1>get undermine their competitor, and in the case of Vine,

0:29:52.840 --> 0:29:59.080
<v Speaker 1>Facebook shows that option. They would just mimic the defining

0:29:59.120 --> 0:30:02.080
<v Speaker 1>features of the co competitor, either in Facebook or in

0:30:02.120 --> 0:30:04.880
<v Speaker 1>one of their other properties, and they would try to

0:30:05.120 --> 0:30:09.560
<v Speaker 1>sap the user base back over to Facebook without having

0:30:09.600 --> 0:30:12.440
<v Speaker 1>to buy the competition. That's kind of what was going

0:30:12.440 --> 0:30:15.560
<v Speaker 1>on with Vine, and it worked. The money began to

0:30:15.600 --> 0:30:18.800
<v Speaker 1>shift from Vine to Instagram, and that money was largely

0:30:18.840 --> 0:30:23.200
<v Speaker 1>coming out of marketing departments. So brands were partnering with

0:30:23.320 --> 0:30:27.800
<v Speaker 1>popular creators in an effort to manufacture some viral marketing campaigns,

0:30:27.960 --> 0:30:30.719
<v Speaker 1>and these could be really cost effective, right, Like, if

0:30:30.760 --> 0:30:33.880
<v Speaker 1>you're a creator, a deal might land you a ton

0:30:34.120 --> 0:30:36.760
<v Speaker 1>of money, but that ton of money would still be

0:30:36.840 --> 0:30:40.960
<v Speaker 1>tiny compared to what a traditional mainstream marketing campaign would

0:30:41.000 --> 0:30:45.040
<v Speaker 1>cost a company. So then there you go. That's where

0:30:45.040 --> 0:30:47.760
<v Speaker 1>the money was for Vine. But then Instagram was offering

0:30:47.800 --> 0:30:50.640
<v Speaker 1>a longer form factor, right, more than twice as long

0:30:50.680 --> 0:30:53.000
<v Speaker 1>as what a vine was, and that was far more

0:30:53.080 --> 0:30:55.680
<v Speaker 1>attractive to a lot of marketers out there. Like when

0:30:55.720 --> 0:30:58.400
<v Speaker 1>you're talking fifteen seconds, you're talking half of a traditional

0:30:58.400 --> 0:31:01.800
<v Speaker 1>television commercial. So the shift of money and influence meant

0:31:01.800 --> 0:31:05.520
<v Speaker 1>that creators would also jump ship from Vine to Instagram

0:31:05.640 --> 0:31:08.800
<v Speaker 1>or in some cases to other platforms like YouTube. Now,

0:31:08.840 --> 0:31:12.160
<v Speaker 1>not everyone did it, but it was really challenging to

0:31:12.200 --> 0:31:14.920
<v Speaker 1>go in for that small pool of money that was

0:31:14.960 --> 0:31:18.680
<v Speaker 1>still available for Vine creators. And it was also scary

0:31:19.000 --> 0:31:22.200
<v Speaker 1>to port your work from one platform to another because

0:31:22.240 --> 0:31:24.960
<v Speaker 1>there was no guarantee the audience would follow. Right, just

0:31:24.960 --> 0:31:27.640
<v Speaker 1>because you were popular on Vine doesn't mean you're going

0:31:27.680 --> 0:31:29.680
<v Speaker 1>to find the same success if you move over to

0:31:29.800 --> 0:31:33.560
<v Speaker 1>Instagram or to YouTube. Some folks could do that, and

0:31:33.600 --> 0:31:36.120
<v Speaker 1>maybe they would lose some of their audience, but they

0:31:36.120 --> 0:31:38.800
<v Speaker 1>would have enough to be able to not lose too

0:31:38.880 --> 0:31:41.680
<v Speaker 1>much momentum. For others, it would mean having to start

0:31:41.720 --> 0:31:44.880
<v Speaker 1>from scratch, and there's no guarantee that you'll strike gold twice.

0:31:45.040 --> 0:31:47.440
<v Speaker 1>But since that pool of money was getting smaller and

0:31:47.480 --> 0:31:50.800
<v Speaker 1>smaller over at Vine, most creators didn't need a lot

0:31:50.880 --> 0:31:53.800
<v Speaker 1>of convincing. They had to switch or else they weren't

0:31:53.800 --> 0:31:56.560
<v Speaker 1>going to make any money anyway. So Vine went into

0:31:56.560 --> 0:31:59.400
<v Speaker 1>further decline, and in twenty sixteen, Twitter announced it was

0:31:59.400 --> 0:32:02.960
<v Speaker 1>going to shut down Vine, which happened in early twenty seventeen.

0:32:03.240 --> 0:32:05.600
<v Speaker 1>And we can still feel the influence of Vine today

0:32:05.640 --> 0:32:08.760
<v Speaker 1>in the form of Instagram reels and TikTok videos, and

0:32:09.000 --> 0:32:11.520
<v Speaker 1>it's possible that neither of those things would have happened

0:32:11.520 --> 0:32:13.680
<v Speaker 1>without Vine. And I know lots of folks who to

0:32:13.720 --> 0:32:17.520
<v Speaker 1>this day limit the loss of Vine. So farewell Vine.

0:32:17.520 --> 0:32:20.840
<v Speaker 1>We hardly knew. Yee, Okay, we're gonna take another quick break.

0:32:20.880 --> 0:32:24.040
<v Speaker 1>When we come back. We've got a couple more examples

0:32:24.120 --> 0:32:36.480
<v Speaker 1>I really want to talk about. Okay, let's talk about

0:32:36.520 --> 0:32:39.920
<v Speaker 1>some more failures. And this next one is one that

0:32:40.240 --> 0:32:43.920
<v Speaker 1>I absolutely loved, even as I recognized that it was

0:32:43.960 --> 0:32:47.440
<v Speaker 1>a hot mess from the get go, and it probably

0:32:47.600 --> 0:32:50.720
<v Speaker 1>wasn't a practical solution for ninety nine percent of the

0:32:50.760 --> 0:32:55.960
<v Speaker 1>population out there. So I'm talking about Google Wave, And honestly,

0:32:56.040 --> 0:32:58.720
<v Speaker 1>I could do a full episode just about Google apps

0:32:58.760 --> 0:33:00.760
<v Speaker 1>that have come and gone, and in fact, I actually

0:33:00.800 --> 0:33:03.120
<v Speaker 1>have done that at least once or twice in the past.

0:33:03.280 --> 0:33:05.920
<v Speaker 1>But Google Wave has a special place in my heart.

0:33:06.440 --> 0:33:10.200
<v Speaker 1>So Google launched this bizarre app back in two thousand

0:33:10.200 --> 0:33:13.760
<v Speaker 1>and nine, and it was a real time online collaborative

0:33:13.840 --> 0:33:17.160
<v Speaker 1>tool and it was kind of like a Frankenstein's Monster

0:33:17.320 --> 0:33:20.840
<v Speaker 1>of features. There were elements of email worked in there,

0:33:21.600 --> 0:33:25.480
<v Speaker 1>Instant messaging was worked in there, online word processing, and

0:33:25.600 --> 0:33:29.720
<v Speaker 1>lots more. So you could create a document in Google Wave,

0:33:30.040 --> 0:33:33.200
<v Speaker 1>you could invite online collaborators and all of you could

0:33:33.200 --> 0:33:35.440
<v Speaker 1>work within that document at the same time, and you

0:33:35.480 --> 0:33:38.040
<v Speaker 1>would be able to see what others were doing in

0:33:38.080 --> 0:33:40.640
<v Speaker 1>the document, like word by word. You could watch as

0:33:40.640 --> 0:33:43.520
<v Speaker 1>they made typos and corrected and stuff. It was all

0:33:43.560 --> 0:33:46.760
<v Speaker 1>going at the same time, and the app would also

0:33:46.880 --> 0:33:49.640
<v Speaker 1>keep a history of all the changes made to the document.

0:33:49.800 --> 0:33:53.680
<v Speaker 1>So maybe someone's going off the rails right and you're like, no, wait,

0:33:54.000 --> 0:33:56.760
<v Speaker 1>we can't none of this is working for this document.

0:33:56.760 --> 0:33:59.240
<v Speaker 1>You could actually wind things back to an earlier version.

0:33:59.840 --> 0:34:03.160
<v Speaker 1>I only used Google Wave with one other person, who

0:34:03.240 --> 0:34:06.480
<v Speaker 1>was my former co host, Chris Pillette. We used Google

0:34:06.520 --> 0:34:10.120
<v Speaker 1>Wave to build out a run of show for a

0:34:10.160 --> 0:34:13.960
<v Speaker 1>streaming video series we used to do way back in

0:34:14.000 --> 0:34:16.520
<v Speaker 1>the day. So once a week we would do a

0:34:16.520 --> 0:34:18.720
<v Speaker 1>streaming video that was kind of like a tech news

0:34:18.760 --> 0:34:21.919
<v Speaker 1>program live on TV in the middle of the day

0:34:22.040 --> 0:34:25.160
<v Speaker 1>Eastern time, and we would use Google Wave to organize

0:34:25.160 --> 0:34:27.359
<v Speaker 1>our show and even to make changes on the fly

0:34:27.480 --> 0:34:30.200
<v Speaker 1>while streaming our video content. And it was an ideal

0:34:30.400 --> 0:34:34.600
<v Speaker 1>tool for that situation. The trouble was, I couldn't figure

0:34:34.640 --> 0:34:37.759
<v Speaker 1>out any other use case where it would really make

0:34:37.880 --> 0:34:41.120
<v Speaker 1>sense for me, just this one thing I would do

0:34:41.320 --> 0:34:43.480
<v Speaker 1>once a week for my job, and for a lot

0:34:43.560 --> 0:34:46.319
<v Speaker 1>of folks out there, they never found a good use

0:34:46.480 --> 0:34:48.960
<v Speaker 1>for Google Wave. By the way, I really miss that

0:34:49.000 --> 0:34:52.319
<v Speaker 1>streaming video show. One of the fun things that we

0:34:52.440 --> 0:34:55.080
<v Speaker 1>used to have in that show is that occasionally either

0:34:55.200 --> 0:34:57.440
<v Speaker 1>Matt Frederick, one of the hosts of Stuff they Don't

0:34:57.480 --> 0:35:00.040
<v Speaker 1>Want You to Know, would do this, or some some

0:35:00.080 --> 0:35:02.279
<v Speaker 1>times Tyler Klaig, who's now like the head of our

0:35:02.360 --> 0:35:05.200
<v Speaker 1>podcast production. Both of them are still with the company.

0:35:05.280 --> 0:35:07.799
<v Speaker 1>I would do a tweet of the week segment and

0:35:07.880 --> 0:35:11.400
<v Speaker 1>they would hold up a little bird on a stick.

0:35:11.480 --> 0:35:13.000
<v Speaker 1>They would be out of frame and they would poke

0:35:13.040 --> 0:35:15.520
<v Speaker 1>a bird of stick to be in front of my

0:35:15.600 --> 0:35:18.840
<v Speaker 1>face and they would make a tweet sound, which just

0:35:18.880 --> 0:35:22.160
<v Speaker 1>shows how far those guys have come since we were

0:35:22.160 --> 0:35:25.600
<v Speaker 1>doing the streaming news show. Anyway, features in Google Wave

0:35:25.960 --> 0:35:29.280
<v Speaker 1>would eventually find their way into lots of other Google applications,

0:35:29.640 --> 0:35:32.200
<v Speaker 1>but Google Wave itself was just not very long for

0:35:32.280 --> 0:35:36.480
<v Speaker 1>this world. Google supported it for about a year. Then

0:35:36.719 --> 0:35:39.279
<v Speaker 1>they essentially said, you know what, this isn't working for us,

0:35:39.280 --> 0:35:42.680
<v Speaker 1>and they shifted it off to the Apache Software Foundation

0:35:42.880 --> 0:35:46.040
<v Speaker 1>in twenty ten. Folks suggested that Google's decision was due

0:35:46.080 --> 0:35:50.760
<v Speaker 1>to lots of converging reasons, ranging from just a confusing

0:35:50.800 --> 0:35:54.880
<v Speaker 1>interface that was turning away new users to internal conflicts

0:35:54.920 --> 0:35:57.440
<v Speaker 1>that were happening within the development team, especially at the

0:35:57.520 --> 0:36:01.080
<v Speaker 1>leadership level. There were stories that there were leaders who

0:36:01.120 --> 0:36:03.960
<v Speaker 1>were disagreeing on what Google Wave was even supposed to be,

0:36:04.200 --> 0:36:06.239
<v Speaker 1>which meant that the development team was put in this

0:36:06.280 --> 0:36:08.760
<v Speaker 1>really difficult position in the middle to try and create

0:36:08.840 --> 0:36:11.120
<v Speaker 1>all things for all people, which was impossible, so they

0:36:11.160 --> 0:36:13.759
<v Speaker 1>ended up creating something that was for nobody. But even

0:36:13.760 --> 0:36:17.840
<v Speaker 1>the Apache Wave version is no more. The nonprofit group

0:36:17.880 --> 0:36:21.600
<v Speaker 1>had Wave in an incubator status for almost a decade,

0:36:21.719 --> 0:36:25.840
<v Speaker 1>but in twenty eighteen the Wave became still Waters because

0:36:25.880 --> 0:36:29.040
<v Speaker 1>development ceased and Wave just never graduated out of that

0:36:29.200 --> 0:36:32.160
<v Speaker 1>incubator status. Now I can't say that I would still

0:36:32.160 --> 0:36:35.280
<v Speaker 1>be using Wave to this day if it were still around,

0:36:35.360 --> 0:36:38.400
<v Speaker 1>but that's mostly because tech stuff is a pretty simple project.

0:36:38.520 --> 0:36:41.520
<v Speaker 1>I research, write, and record all the episodes, and then

0:36:41.640 --> 0:36:46.319
<v Speaker 1>super producer Tari she edits and publishes the episodes, so

0:36:46.360 --> 0:36:49.279
<v Speaker 1>there is collaboration there. Tari and I do collaborate, but

0:36:49.320 --> 0:36:53.920
<v Speaker 1>it's divided really neatly into a production phase and a

0:36:53.960 --> 0:36:58.479
<v Speaker 1>post production phase. Perhaps if I were more actively working

0:36:58.560 --> 0:37:01.720
<v Speaker 1>on shows that had multiple collaborate I would feel Waves

0:37:01.800 --> 0:37:05.240
<v Speaker 1>loss more keenly. But I really liked using it, even

0:37:05.360 --> 0:37:09.000
<v Speaker 1>while I recognized how weird and janky it was. Now

0:37:09.040 --> 0:37:12.080
<v Speaker 1>this list could go on much much longer, but I

0:37:12.120 --> 0:37:15.600
<v Speaker 1>figure I'll conclude with a rock Star like story, and

0:37:15.680 --> 0:37:19.040
<v Speaker 1>that story involves a company called pay by Touch Will.

0:37:19.280 --> 0:37:21.399
<v Speaker 1>Most of the apps I've talked about so far were

0:37:21.520 --> 0:37:24.200
<v Speaker 1>ones that you would either use on your phone or

0:37:24.200 --> 0:37:27.600
<v Speaker 1>on your computer. Pay by Touch was different, okay, it

0:37:27.680 --> 0:37:30.320
<v Speaker 1>was an app that was a service, and this service

0:37:30.320 --> 0:37:33.200
<v Speaker 1>would let you pay for purchases at a point of sale,

0:37:33.320 --> 0:37:36.360
<v Speaker 1>primarily in places like supermarkets here in the United States,

0:37:36.680 --> 0:37:39.760
<v Speaker 1>and all you had to do was swipe your finger

0:37:39.840 --> 0:37:42.879
<v Speaker 1>on a fingerprint sensor at the cash register, and your

0:37:42.880 --> 0:37:46.800
<v Speaker 1>biometric data would correspond to your pay by Touch account

0:37:47.120 --> 0:37:49.960
<v Speaker 1>and an electronic transaction would take care of your grocery

0:37:50.000 --> 0:37:53.319
<v Speaker 1>bill by deducting it from your checking account or from

0:37:53.320 --> 0:37:55.480
<v Speaker 1>a credit card, and you could go on your merry

0:37:55.520 --> 0:37:58.680
<v Speaker 1>way without ever having to hand over cash or write

0:37:58.680 --> 0:38:01.640
<v Speaker 1>a check or use a cra card physically. Just swipe

0:38:01.680 --> 0:38:04.640
<v Speaker 1>your finger, good to go. This was the future, and

0:38:04.680 --> 0:38:06.960
<v Speaker 1>it was all in two thousand and two. The idea

0:38:06.960 --> 0:38:10.080
<v Speaker 1>of having your financials directly tied to your own identity

0:38:10.480 --> 0:38:12.880
<v Speaker 1>was one that had been around for a while but

0:38:12.960 --> 0:38:17.480
<v Speaker 1>not really accomplished. So again, it was really considered to

0:38:17.520 --> 0:38:21.840
<v Speaker 1>be convenient, and you could even tie your biometrics to

0:38:22.040 --> 0:38:26.520
<v Speaker 1>things like a store loyalty account, so by using your fingerprint,

0:38:26.560 --> 0:38:30.799
<v Speaker 1>you could then apply discounts or coupons to whatever it

0:38:30.840 --> 0:38:33.239
<v Speaker 1>was you were buying, and this was coming out in

0:38:33.239 --> 0:38:35.200
<v Speaker 1>two thousand and two, you know, like five years before

0:38:35.239 --> 0:38:37.799
<v Speaker 1>we would get the first iPhone. So these days, you know,

0:38:37.840 --> 0:38:41.640
<v Speaker 1>obviously we have lots of contactless payment solutions, mostly tied

0:38:41.680 --> 0:38:43.759
<v Speaker 1>to mobile phones, But back in two thousand and two,

0:38:43.800 --> 0:38:47.719
<v Speaker 1>this was really revolutionary. Now, the services did face challenges.

0:38:47.760 --> 0:38:49.920
<v Speaker 1>One big one was that folks were a little anxious

0:38:49.920 --> 0:38:52.800
<v Speaker 1>about having their money tied to their fingerprints. There seemed

0:38:52.800 --> 0:38:55.640
<v Speaker 1>to be something invasive about that. Heck, if you're the

0:38:55.719 --> 0:38:58.319
<v Speaker 1>type of person who prefers to use cash for your transactions,

0:38:58.360 --> 0:39:01.480
<v Speaker 1>it absolutely goes against your references. Also, the thought of

0:39:01.480 --> 0:39:05.160
<v Speaker 1>a third party company potentially having insight into your purchase

0:39:05.200 --> 0:39:08.319
<v Speaker 1>history seemed creepy. But despite the slow going and low

0:39:08.320 --> 0:39:11.399
<v Speaker 1>adoption rate, pay by Touch did grow and got lots

0:39:11.440 --> 0:39:15.000
<v Speaker 1>of investors. It expanded its business into various supermarket chains.

0:39:15.200 --> 0:39:17.879
<v Speaker 1>But then the company would ultimately declare bankruptcy in two

0:39:17.920 --> 0:39:21.120
<v Speaker 1>thousand and eight. So what happened, Well, part of what

0:39:21.360 --> 0:39:24.360
<v Speaker 1>happened was a failure to communicate to the public the

0:39:24.400 --> 0:39:28.240
<v Speaker 1>benefits of this system. Just really bad marketing and education.

0:39:28.600 --> 0:39:32.560
<v Speaker 1>The concept again, including things like tying biometrics to loyalty

0:39:32.600 --> 0:39:36.319
<v Speaker 1>programs and stuff that just didn't really get communicated effectively

0:39:36.600 --> 0:39:40.719
<v Speaker 1>in most locations, and some stores were just using the

0:39:40.760 --> 0:39:43.880
<v Speaker 1>system for loyalty programs and customers would still pay for

0:39:43.960 --> 0:39:46.840
<v Speaker 1>their purchases using more traditional means. So there was this

0:39:46.920 --> 0:39:49.640
<v Speaker 1>element of distrust that the company was never able to overcome,

0:39:49.960 --> 0:39:52.759
<v Speaker 1>possibly for good reason, because another big reason for the

0:39:52.800 --> 0:39:56.200
<v Speaker 1>company's failure was in its leadership. The CEO of the

0:39:56.200 --> 0:39:59.239
<v Speaker 1>company was a guy named John P. Rogers, and he

0:39:59.320 --> 0:40:02.879
<v Speaker 1>had had some trouble with the law that largely went

0:40:03.000 --> 0:40:06.719
<v Speaker 1>unnoticed when he was getting investments for his company. At

0:40:06.800 --> 0:40:09.880
<v Speaker 1>least a couple of women had accused him of violent behavior,

0:40:10.000 --> 0:40:13.440
<v Speaker 1>one saying that he had abused her, the other saying

0:40:13.480 --> 0:40:16.279
<v Speaker 1>he had trashed her home. Both of them had been

0:40:16.280 --> 0:40:19.879
<v Speaker 1>connected romantically with him. He had also been pulled over

0:40:19.920 --> 0:40:22.480
<v Speaker 1>by police and arrested on suspicion of driving under the

0:40:22.520 --> 0:40:27.520
<v Speaker 1>influence of cocaine, and apparently he was known to have

0:40:27.640 --> 0:40:32.359
<v Speaker 1>had issues with drug addiction. Investigation suggested that Rogers had

0:40:32.400 --> 0:40:37.120
<v Speaker 1>been rather extravagant with corporate funds, that he had spearheaded

0:40:37.280 --> 0:40:40.360
<v Speaker 1>efforts to convince those with really deep pockets to invest

0:40:40.400 --> 0:40:43.359
<v Speaker 1>in pay by touch that paid off in dividends. He

0:40:43.480 --> 0:40:47.080
<v Speaker 1>raised around three hundred and forty million dollars, but by

0:40:47.280 --> 0:40:49.640
<v Speaker 1>two thousand and eight the coffers were empty, and the

0:40:49.640 --> 0:40:52.960
<v Speaker 1>investigation suggested that one reason for this was that Rogers

0:40:53.000 --> 0:40:55.840
<v Speaker 1>appeared to have been dipping into corporate funds to pay

0:40:55.880 --> 0:40:59.879
<v Speaker 1>for an extravagant lifestyle, complete with drug use. And when

0:40:59.880 --> 0:41:03.160
<v Speaker 1>I say extravagant, I mean that the investigation suggested he

0:41:03.320 --> 0:41:07.239
<v Speaker 1>was burning around eight million dollars a month, which is

0:41:07.800 --> 0:41:09.840
<v Speaker 1>a lot of money. And it would turn out that

0:41:09.920 --> 0:41:13.360
<v Speaker 1>Rogers had a history of failed businesses, something that no

0:41:13.400 --> 0:41:15.560
<v Speaker 1>one had really noticed when Pay by Touch was just

0:41:15.640 --> 0:41:18.279
<v Speaker 1>getting off the ground. He had managed to keep his

0:41:18.280 --> 0:41:21.200
<v Speaker 1>history kind of out of the spotlight, and investors didn't

0:41:21.239 --> 0:41:24.000
<v Speaker 1>ask any tough questions. They just were excited about this

0:41:24.160 --> 0:41:28.279
<v Speaker 1>potential opportunity to completely revolutionize the way we pay for

0:41:28.400 --> 0:41:32.680
<v Speaker 1>stuff at retail locations. Obviously that was key to him

0:41:32.680 --> 0:41:37.920
<v Speaker 1>securing investments. Ultimately, Pay by Touch went couput. Some investors

0:41:37.960 --> 0:41:42.000
<v Speaker 1>pursued civil litigation against the company and against Rogers, but

0:41:42.160 --> 0:41:44.959
<v Speaker 1>he never faced criminal charges for how things went down,

0:41:45.080 --> 0:41:47.719
<v Speaker 1>which is kind of wild. I wasn't there, so I

0:41:47.719 --> 0:41:51.040
<v Speaker 1>don't know. Maybe the evidence was all circumstantial. Maybe there

0:41:51.080 --> 0:41:53.480
<v Speaker 1>was not a solid case against him, but it does

0:41:53.760 --> 0:41:56.319
<v Speaker 1>seem to fall in line with the perception that the

0:41:56.400 --> 0:41:59.480
<v Speaker 1>rules are different depending upon who you are and your

0:41:59.520 --> 0:42:02.360
<v Speaker 1>station in life. I don't know if that's actually the

0:42:02.440 --> 0:42:05.400
<v Speaker 1>case in this particular instance, but on the surface it

0:42:05.400 --> 0:42:10.000
<v Speaker 1>seems to reinforce that idea anyway. That is just a

0:42:10.120 --> 0:42:15.160
<v Speaker 1>quick list of some major apps that received a lot

0:42:15.160 --> 0:42:19.279
<v Speaker 1>of attention but ultimately flamed out. As I said, we

0:42:19.320 --> 0:42:22.279
<v Speaker 1>could go on much much longer with this list. There

0:42:22.280 --> 0:42:24.879
<v Speaker 1>are tons of other examples, and I'll probably do more

0:42:24.920 --> 0:42:28.120
<v Speaker 1>episodes about them in the future. And you should expect

0:42:28.120 --> 0:42:31.440
<v Speaker 1>these kind of things, right because again, creating an app

0:42:31.920 --> 0:42:37.480
<v Speaker 1>is seen as one of those gateways toward insane success

0:42:37.560 --> 0:42:41.600
<v Speaker 1>in Silicon Valley. Like it seems like everyone in Silicon

0:42:41.719 --> 0:42:45.600
<v Speaker 1>Valley is behind some sort of app, and we might

0:42:45.640 --> 0:42:48.640
<v Speaker 1>only hear about a small percentage of them. Some of

0:42:48.640 --> 0:42:50.920
<v Speaker 1>those cases are because the app is just so incredible

0:42:50.960 --> 0:42:55.080
<v Speaker 1>and useful that it's undeniable how valuable it is. In

0:42:55.160 --> 0:42:58.719
<v Speaker 1>other cases, it might be that it's a peculiarity and

0:42:58.840 --> 0:43:02.880
<v Speaker 1>it gets some momentary notice and then ultimately that doesn't

0:43:03.000 --> 0:43:05.000
<v Speaker 1>stand the test of time. And in a few cases

0:43:05.000 --> 0:43:08.799
<v Speaker 1>it may just be notorious and infamous, as I would

0:43:08.880 --> 0:43:13.279
<v Speaker 1>argue the pay by touch story ultimately became once the

0:43:13.520 --> 0:43:18.600
<v Speaker 1>history of Rogers became more public knowledge. Anyway, I hope

0:43:18.600 --> 0:43:21.840
<v Speaker 1>you enjoyed this episode. I hope you are all well,

0:43:22.520 --> 0:43:31.399
<v Speaker 1>and I will talk to you again really soon. Tech

0:43:31.480 --> 0:43:35.880
<v Speaker 1>Stuff is an iHeartRadio production. For more podcasts from iHeartRadio,

0:43:36.200 --> 0:43:39.920
<v Speaker 1>visit the iHeartRadio app, Apple Podcasts, or wherever you listen

0:43:39.960 --> 0:43:44.719
<v Speaker 1>to your favorite shows.