1
00:00:00,000 --> 00:00:06,360
Show them what you did. I bought an iPhone 17 Pro Max.

2
00:00:03,600 --> 00:00:10,000
>> Yeah, and the worst part is the reason. For what? So Zoomer streamers wouldn't

3
00:00:08,440 --> 00:00:15,240
make fun of you when you go to exchange contact information? >> That is not the only reason. It was the

4
00:00:12,920 --> 00:00:19,440
biggest one. And [music] the worst part is he pulled the trigger on this thing

5
00:00:16,960 --> 00:00:23,120
just 2 weeks before Google announced that Pixel phones will be supporting

6
00:00:21,320 --> 00:00:27,240
AirDrop making it more convenient than ever to socialize cross-platform. Adding

7
00:00:25,280 --> 00:00:33,000
insult to injury, just weeks later the Samsung tri-fold

8
00:00:30,320 --> 00:00:36,025
that he waited 4 years for finally dropped. Dude, the look on your face was

9
00:00:34,920 --> 00:00:41,960
Yeah. >> [laughter] >> That one. But as crazy as it sounds, I actually

10
00:00:40,000 --> 00:00:45,720
don't regret my decision. [music] I know many of you out there may not love

11
00:00:43,800 --> 00:00:51,200
Apple's business practices and to be fair, yeah, neither do I. But I find

12
00:00:48,400 --> 00:00:55,800
myself really appreciating some of the quality of life features and I wanted to

13
00:00:53,240 --> 00:01:00,960
give you guys my personal perspective on why the social aspects of the iPhone go

14
00:00:57,960 --> 00:01:03,240
a lot deeper than bubble colors and why

15
00:01:00,960 --> 00:01:07,320
it's going to be really hard for Android to win me back again even if I did buy

16
00:01:05,320 --> 00:01:11,000
this like 1 month before my dream Android device was announced. Man, I

17
00:01:09,360 --> 00:01:15,080
really did buy this at the worst time, didn't I? Yeah. But it's the best time

18
00:01:13,800 --> 00:01:17,945
to segue Not quite. Oh. You could have done it in

19
00:01:17,360 --> 00:01:24,440
August. >> [laughter] >> Oh. That would have been slightly worse. >> That's true.

20
00:01:21,440 --> 00:01:26,200
But it's the best time to segue

21
00:01:24,440 --> 00:01:29,880
to our sponsor. Acuity Scheduling. It's a flexible

22
00:01:28,120 --> 00:01:33,840
scheduling software that offers calendar management, booking tools, client

23
00:01:31,600 --> 00:01:38,720
communication, secure payments, custom branding and much more. Save 20% today

24
00:01:36,720 --> 00:01:41,840
with our link below. No story is complete without the who, what, where,

25
00:01:40,040 --> 00:01:46,400
when and why though. Let's talk about all of that just not in that order. See

26
00:01:44,480 --> 00:01:50,440
you later. The TLDR is that I was looking for something fresher. My

27
00:01:47,840 --> 00:01:53,080
OnePlus 11 was fine, but I really did miss being on something cutting edge

28
00:01:51,960 --> 00:01:57,840
whether it was because of a better camera or even some fun gimmick like my

29
00:01:55,520 --> 00:02:02,280
Fold 4 had. But the biggest thing that actually pushed me to iPhone was the

30
00:01:59,360 --> 00:02:05,240
social experience. Last October, I got to go down to TwitchCon for the first

31
00:02:03,520 --> 00:02:09,759
time. And as dumb as this is going to sound to many of you, my Android device

32
00:02:07,720 --> 00:02:14,160
actually held back my networking efforts multiple times.

33
00:02:12,000 --> 00:02:17,440
Oh, hey. I'd spark up a conversation. We'd talk about a collaborative effort

34
00:02:15,720 --> 00:02:21,440
in the future. We'd hold out our phones to AirDrop, and I had to be the awkward,

35
00:02:20,000 --> 00:02:25,280
"Hey, can you just actually type your number into my phone?"

36
00:02:23,000 --> 00:02:29,240
Thanks. Well, no one refused to give me their number. I could immediately tell

37
00:02:27,360 --> 00:02:33,440
though that I was kind of coming across as a bit of a burden.

38
00:02:31,520 --> 00:02:37,959
Thanks. I did find some techy workarounds. I actually set my wallpaper

39
00:02:35,680 --> 00:02:41,640
to my Discord QR code, but sometimes people had issues with that, too. QR

40
00:02:39,800 --> 00:02:45,280
codes are a little less ubiquitous in North America. And let's face it, us

41
00:02:43,400 --> 00:02:49,920
Zoomers aren't exactly known right now for being super tech-savvy. Of course,

42
00:02:47,600 --> 00:02:55,160
that wasn't enough to convince me to join the herd. It was all of the other

43
00:02:52,480 --> 00:02:59,600
boxes that Apple also ticked. This generation of iPhone, even Linus

44
00:02:57,400 --> 00:03:04,440
admitted, is an incredibly complete package, pretty much top to bottom. So,

45
00:03:02,519 --> 00:03:08,560
after that trip, I did it. I went out and bought this phone. And I was

46
00:03:06,320 --> 00:03:13,920
actually so excited that I also picked up a Base 17 as a birthday present for

47
00:03:11,239 --> 00:03:17,959
my wife to replace her aging 12 mini. Then I got home, grabbed some dinner,

48
00:03:15,920 --> 00:03:25,800
and some hard-to-swallow pills. Cuz it took me, I kid you not, over 48 hours to

49
00:03:22,120 --> 00:03:27,600
finally get this device fully set up.

50
00:03:25,800 --> 00:03:32,440
And this is where the what comes in. Because I was constantly asking, "What

51
00:03:30,040 --> 00:03:36,760
the is Apple doing?" Just like Linus, I struggled to get the Move to

52
00:03:34,440 --> 00:03:40,880
iOS app to do anything. And it wasn't for a lack of trying. One time, my

53
00:03:38,640 --> 00:03:45,400
Android overheated, and it shut down. Other times, it took so long that both

54
00:03:43,320 --> 00:03:49,880
phones died mid-transfer. And then there was the time that it got stuck at the

55
00:03:47,600 --> 00:03:53,480
1-minute remaining mark for several hours. When I complained about this on

56
00:03:51,519 --> 00:03:57,800
Twitter, I had several people saying I was either fabricating this story for

57
00:03:54,960 --> 00:04:02,800
clicks or this was a skill issue. Well, excuse me. All I did was follow

58
00:04:00,680 --> 00:04:07,120
the app instructions and at the time, I had no intention on this being a video.

59
00:04:05,240 --> 00:04:11,560
So, why would I fake this for my own personal device? I did get some helpful

60
00:04:09,360 --> 00:04:15,240
comments saying, "It's just broken on certain flavors of Android." And

61
00:04:13,200 --> 00:04:19,760
honestly, if that's the case, I get it. The fragmentation of the

62
00:04:16,959 --> 00:04:24,240
Android ecosystem is one of the greatest weaknesses, which I'm going to get into

63
00:04:22,040 --> 00:04:28,360
a little bit later. But, Apple should be the one telling me. If I open the app

64
00:04:26,440 --> 00:04:32,600
and it knows that it might not work, Apple should pop up a little warning.

65
00:04:30,560 --> 00:04:37,360
Eventually, I had to give up and set everything up manually, which took about

66
00:04:34,800 --> 00:04:41,800
4 hours. But, it was kind of a blessing in disguise because during that time, I

67
00:04:39,919 --> 00:04:45,880
started to understand where people are coming from when they speak so highly

68
00:04:43,840 --> 00:04:50,400
about the iPhone. For starters, it's really easy on the eyes. And whether you

69
00:04:48,200 --> 00:04:54,120
like it or not, the smooth transitions and the fun little animations that come

70
00:04:52,040 --> 00:04:58,880
with liquid glass really do make the device feel luxurious, even if it can

71
00:04:56,480 --> 00:05:03,120
make things take a little bit longer. The display is also incredible,

72
00:05:01,320 --> 00:05:08,160
especially with how dim it can get for some bedtime doom scrolling. And the

73
00:05:04,720 --> 00:05:11,080
battery has lasted me multiple days

74
00:05:08,160 --> 00:05:14,200
multiple times. But, it charges so fast that I basically don't really think

75
00:05:12,760 --> 00:05:17,919
about my battery during the work week when I can charge it in my car. Also,

76
00:05:16,120 --> 00:05:22,360
despite what I have been told for years about Apple, the customization seems on

77
00:05:20,160 --> 00:05:26,320
par or even better than some Android devices that I've used, which doesn't

78
00:05:24,200 --> 00:05:31,600
mean it can do everything that Android can though. A big one is it can't side

79
00:05:29,080 --> 00:05:35,960
load. I often hear people talk about how terrible it is that you can't do this on

80
00:05:33,680 --> 00:05:40,160
Apple devices. But, then I realized I have never side loaded on Android.

81
00:05:38,560 --> 00:05:44,919
I just haven't needed to. And while there are tons of great reasons to side

82
00:05:42,600 --> 00:05:48,440
load something, not being able to has never held me back. And it probably

83
00:05:46,800 --> 00:05:52,480
won't hold me back in the future. And I found the same thing was true for most

84
00:05:50,600 --> 00:05:56,280
of the techy people in my life. So, I concede that it is a selling point for

85
00:05:54,480 --> 00:06:01,040
Android, but I don't buy the narrative that not having it is a limitation of

86
00:05:59,040 --> 00:06:05,280
Apple. The second big one is the keyboard. To put it simply, Apple has

87
00:06:03,200 --> 00:06:08,800
the worst default keyboard I have ever used on a mobile phone. The amount of

88
00:06:07,160 --> 00:06:13,800
wasted space that could have been used to have larger keys or more functions on

89
00:06:11,080 --> 00:06:17,720
the top layer drives me nuts, and my Canadian homie Justin Bieber nailed this

90
00:06:16,000 --> 00:06:24,960
one. The fact that they put the dictation key in the exact same spot as

91
00:06:22,360 --> 00:06:30,120
the send button in a text message is downright unacceptable. I know it's such

92
00:06:28,080 --> 00:06:34,520
a minor thing, but the amount of times that I have hit it by accident tells me

93
00:06:32,200 --> 00:06:39,240
for certain that if anyone at Apple actually uses this keyboard, they must

94
00:06:37,400 --> 00:06:42,520
know that this is a problem. And I know that I could probably download a

95
00:06:40,480 --> 00:06:47,080
third-party keyboard to get some of the functionality I'm missing, but I never

96
00:06:44,600 --> 00:06:50,800
felt like I needed to replace Gboard, so I think this is a fair criticism.

97
00:06:48,880 --> 00:06:55,520
Another thing that drives me nuts is having three separate actions for

98
00:06:53,480 --> 00:06:59,440
swiping down. The middle pulls down apps and search, top left handles

99
00:06:57,120 --> 00:07:03,000
notifications, and top right brings down the control center. Really, you couldn't

100
00:07:01,000 --> 00:07:06,640
have just like moved one of these to a swipe up function. And even more

101
00:07:04,600 --> 00:07:11,200
annoyingly, if I swipe down the control center, I either have to swipe back up

102
00:07:09,400 --> 00:07:15,560
in the top right, which is not ergonomic, or tap. And I'm sure I'm

103
00:07:13,800 --> 00:07:20,160
going to start a firestorm here, but it's the one place in iOS where tap is

104
00:07:17,880 --> 00:07:25,040
the gesture to go back instead of the other million back gestures that they

105
00:07:22,200 --> 00:07:30,919
have. It's so confusing. On a brighter note, though, the camera is incredible.

106
00:07:27,760 --> 00:07:33,360
This right here is why these phones

107
00:07:30,919 --> 00:07:36,720
dominate and will continue to dominate the social media addicted teen

108
00:07:34,720 --> 00:07:40,120
demographic. It's just easily the best camera I've ever used on a mobile

109
00:07:38,280 --> 00:07:44,800
device, no question. There are things I don't like. The default camera app feels

110
00:07:42,400 --> 00:07:48,800
too bare and not customizable and the camera button feels useless and I press

111
00:07:47,200 --> 00:07:52,560
it on accident more times than I'd like to admit, but the third-party camera

112
00:07:50,560 --> 00:07:56,680
apps unlock layers of compatibility for this thing that is just hard to compete

113
00:07:54,720 --> 00:08:01,320
with. A huge part as to why the camera can be so much better on an iPhone is

114
00:07:58,960 --> 00:08:05,720
simply down to how iOS interacts with the hardware and the very nature of

115
00:08:03,600 --> 00:08:09,080
Android makes this kind of hard to replicate. Android is incredibly

116
00:08:07,280 --> 00:08:14,200
versatile and works across thousands of devices. Maybe even tens of thousands of

117
00:08:12,200 --> 00:08:18,480
different devices. But that means developers of each flavor need to work

118
00:08:16,520 --> 00:08:22,000
on bridging the gap between the various physical camera integrations and

119
00:08:20,560 --> 00:08:26,520
Android. This can lead to extra overhead, poor image processing, and

120
00:08:24,240 --> 00:08:31,680
maybe most importantly, an extremely inconsistent look and feel across the

121
00:08:29,080 --> 00:08:36,440
ecosystem. You can say Apple phones have good cameras, but you can't say with

122
00:08:33,800 --> 00:08:40,520
certainty that Android phones have good cameras and I think that's a big

123
00:08:38,000 --> 00:08:45,720
problem, especially when we go a layer deeper and look at how third-party apps

124
00:08:43,280 --> 00:08:48,880
use the camera. A perfect example is this one. Compare these two Twitch

125
00:08:47,480 --> 00:08:53,000
streams that I did when I was down in San Diego. On the left, you can see

126
00:08:50,880 --> 00:08:58,080
Tubbo's POV where he is using his front-facing camera on his iPhone. It's

127
00:08:55,960 --> 00:09:03,480
pretty clean, right? And on the right, you can see my rear-facing camera, which

128
00:09:00,839 --> 00:09:07,440
in theory is a much better sensor than any selfie cam.

129
00:09:05,120 --> 00:09:12,520
It's okay, especially for a couple year old device.

130
00:09:08,680 --> 00:09:15,240
But my footage is the full quality file

131
00:09:12,520 --> 00:09:21,800
that I downloaded off my phone and Tubbo's is after Twitch compression and

132
00:09:18,839 --> 00:09:27,760
uploading it to YouTube. Somehow his still looks better even after passing

133
00:09:24,520 --> 00:09:29,640
through multiple dog encoding steps and

134
00:09:27,760 --> 00:09:33,520
this leads me to the biggest reason that I bought an iPhone. It's the social

135
00:09:31,560 --> 00:09:37,400
experiences. You can say what you want about Apple's walled garden, but when

136
00:09:35,280 --> 00:09:41,680
people have been fully converted to it, it truly feels like magic. Whether it's

137
00:09:39,680 --> 00:09:45,720
the tapping to add people as contacts, seamless transition from AirPods to

138
00:09:43,640 --> 00:09:50,480
speakerphone, sharing locations with friends in iMessage, going from phone

139
00:09:47,920 --> 00:09:55,000
call to FaceTime in one button press without having to start a new call. And

140
00:09:52,560 --> 00:10:00,120
of course, AirDrop. Stop, stop, stop right there. I know you are going to

141
00:09:56,840 --> 00:10:01,760
fire up your fancy, resizable, superior

142
00:10:00,120 --> 00:10:05,640
ducking keyboard and type, "But Android has Quick Share." Wait, wait, wait,

143
00:10:03,160 --> 00:10:09,840
wait. The difference is how Apple treats AirDrop versus how Android handles Quick

144
00:10:08,200 --> 00:10:13,360
Share. Quick Share is an afterthought, whereas Apple makes it a central part of

145
00:10:11,960 --> 00:10:18,120
their platform. And this kind of awareness matters. Even decade-long

146
00:10:15,840 --> 00:10:22,880
Android users will often struggle if I ask them to Quick Share a file with me.

147
00:10:20,000 --> 00:10:27,200
Almost all Apple people I know can immediately find AirDrop. Another key

148
00:10:25,520 --> 00:10:32,480
element of Apple's superior social experience is the apps. Brand new apps

149
00:10:30,040 --> 00:10:36,360
will often launch exclusively on iPhone. And even for well-established apps,

150
00:10:34,080 --> 00:10:40,240
iPhone users will often get new updates and features before the Android plebs. I

151
00:10:38,480 --> 00:10:45,120
found this to be especially true for content creator-focused features. Linus

152
00:10:42,760 --> 00:10:49,960
famously spent years calling out YouTube for supporting stories on iPhone, but

153
00:10:47,760 --> 00:10:54,120
not on many Android devices. And Instagram has a feature called Trial

154
00:10:51,760 --> 00:10:58,839
Reels, which allows you to post Reels to non-followers to get performance data

155
00:10:56,800 --> 00:11:03,720
before you share it with your followers. That's been out for a year, but on my

156
00:11:00,920 --> 00:11:07,480
OnePlus and even some Samsung devices still don't support that feature. I

157
00:11:05,920 --> 00:11:10,727
could go on, and I could probably even go on for a whole separate video with

158
00:11:09,320 --> 00:11:16,520
examples like that, but >> [music] >> I think what I've covered so far points

159
00:11:13,200 --> 00:11:18,680
to one big question. Who is this device

160
00:11:16,520 --> 00:11:22,520
for? And in my view, it's for two people. The first is the person who just

161
00:11:20,760 --> 00:11:26,280
wants a phone. They don't care about side loading. They don't care that Apple

162
00:11:24,720 --> 00:11:28,160
has them in a chokehold. They might even like it. I won't judge.

163
00:11:27,757 --> 00:11:33,080
>> [laughter] >> We're all into some weird stuff. But when you look at it from that

164
00:11:30,800 --> 00:11:37,520
perspective, it makes sense why Apple's keynotes focus on things like the

165
00:11:34,680 --> 00:11:41,880
camera, the body, the colors, or even liquid glass, and leave only 30 seconds

166
00:11:40,280 --> 00:11:46,400
to talk about real tech that matters, like how fast the USB-C port

167
00:11:44,200 --> 00:11:50,960
can transfer data. The second is for people like me, a content creator. And

168
00:11:49,040 --> 00:11:54,560
before you get mad, I'm not saying that content creators can't get their work

169
00:11:52,920 --> 00:11:58,320
done on other devices. It's just that between the apps getting new features

170
00:11:56,000 --> 00:12:02,520
first, sharing video files easily with AirDrop, tapping contacts quick meetup,

171
00:12:00,720 --> 00:12:07,840
the iPhone prioritizes the features that people like me need it for. So then,

172
00:12:05,800 --> 00:12:11,800
when am I going to be switching back to an Android?

173
00:12:09,200 --> 00:12:15,440
To be honest, I don't think I ever will be. If anything, I'm actually kind of

174
00:12:13,720 --> 00:12:19,520
upset that I put off on getting an iPhone for so long. The only thing that

175
00:12:17,600 --> 00:12:23,600
might win me back is the Samsung tri-fold, which I finally got hands-on

176
00:12:21,720 --> 00:12:27,200
with recently. And if Linus doesn't end up keeping it, maybe he'll let me do a

177
00:12:25,440 --> 00:12:30,480
30-day review of it, and I'll tell you guys my thoughts. That might win me

178
00:12:28,800 --> 00:12:34,520
back. But that's going to have to wait until I'm at least done telling you

179
00:12:31,960 --> 00:12:37,280
about our sponsor, Acuity Scheduling. Do you ever feel like you're running all

180
00:12:35,800 --> 00:12:41,120
over the place trying to keep up with scheduling things, and then having to do

181
00:12:39,200 --> 00:12:44,720
the things that you're scheduled to do? Well, Acuity Scheduling can help get

182
00:12:42,920 --> 00:12:49,880
your life organized by allowing clients to self-schedule, cancel, and rebook, so

183
00:12:47,680 --> 00:12:53,160
you can focus on doing your actual work. They make it straightforward to sync

184
00:12:51,240 --> 00:12:57,360
with multiple calendar apps, and you can set booking caps across all of them, so

185
00:12:55,280 --> 00:13:01,640
you'll never double-book a client call and Friday night gaming with the boys.

186
00:12:59,240 --> 00:13:05,720
And when you do go into those meetings, Acuity Scheduling will automatically get

187
00:13:03,640 --> 00:13:09,160
you up to speed with notifications and relevant client history. You can also

188
00:13:07,560 --> 00:13:13,200
integrate payment plans with services like Stripe, Square, or PayPal. You send

189
00:13:11,160 --> 00:13:16,760
a contactless request for payment, no need to remind them in person. Again,

190
00:13:14,960 --> 00:13:19,240
that means more time for gaming with the boys. Say goodbye to scheduling

191
00:13:18,520 --> 00:13:23,640
headaches, and go to acuityscheduling.com/LTT

192
00:13:21,839 --> 00:13:29,040
for a free trial, and use offer code ltt20 to save 20% off your first Acuity

193
00:13:26,880 --> 00:13:33,080
Scheduling subscription. If you guys enjoyed this video, go watch Linus'

194
00:13:30,600 --> 00:13:36,920
review of the iPhone 17 to see where we agree and where we disagree. All you

195
00:13:35,360 --> 00:13:40,720
need to know is that I'm right, he's wrong. So, like the video.
