Thoughts on how High Density Housing is Destroying Silicon Valley

If you're on the road these days, you can't help but notice one inescapable fact -- traffic in the Bay Area just keeps getting worse and worse. Increasingly, we're seeing gridlock on our roads. During rush hour, there are times and places where you have to wait through a green light because you can't make it through the intersection -- there isn't any room for your vehicle on the other side. All of these vehicles and increased traffic density means longer drive times, lost productivity, and increased stresses from time pressures, bad drivers, and road rage.

Commuting home the other day, I took a route that was similar to my commute a couple of years ago and I was shocked by where I experienced traffic back-ups, and by how much traffic there was. My rough estimate, based on where I was seeing the back-ups, is that we may have double the number of cars on the road compared to just two or three years ago.

But where did all of these cars come from? Why are there more cars here?

I have one simple answer -- high-density housing. Over the past five years or so, there has been a trend to transform areas of land that once held one and two-story buildings into high-density residential and multi-use/residential structures. In the photo above (that I happened to take about three years ago), what was once a Santa Clara technology campus with about three 2-story buildings was being transformed into a multi-story, high-density multi-use housing facility. The same transformation is also taking place in a couple of blocks in every direction from here.

The big joke with these places is that they make the claim that these high-density residences won't significantly increase traffic because they're close to the train station and public transit. The reality is that, with most of these places, you need to estimate an additional 1.5 cars on the road.

It's surprising to me that so many of these developments have been approved (and continue to be approved) by local city councils. While there are always calls for more affordable housing (and claims that a lack of housing is the problem), these developments are simply eroding any semblance of quality of life in the area. Here's my latest analogy for the problem:

Imagine the Bay Area like an awesome Internet Cafe, good food, nice environment, good Internet connectivity. Then, people start having meetings there and more people keep coming in. Soon, there is no space to sit, all of the tables are occupied and all of the chairs are full. 

Troubled by this, the patrons call for more chairs, more places to sit. Comfy chairs are changed to benches and counters are added to walls, so more people can fit in, but soon there is no place for coffee cups and few places for computers. 

But the worst is that, while the number of patrons has grown significantly, the cafe's Internet connection is still running on the same DSL line that provided reasonable broadband 15 years ago. The Internet Cafe has no Internet.

The Bay Area is collapsing under the weight of too many users while the roads, our broadband connectivity.

It would be one thing if we had the infrastructure to support the human density that they are building for, but we don't. We have no subways, no metro train system. And if you look at San Francisco as an example, we're going on 10 years and they still haven't completed the Muni line from Union Square to the Caltrain station.

And just when you thought they couldn't pack any more in, there's more high-density housing on the way...

San Diego Bike Share - What Happened to the Bikes?

I just spent the week in San Diego for a conference and it made for an interesting comparison to last year's San Diego event.

In San Diego last year, everywhere you went, there were bicycles -- GPS-enabled bike share had taken over the downtown convention center area. There were probably three or four different companies with bikes all around. What was surprising was that  I'd seen a few ride share bikes in the time, but in nowhere near the number that there were there in San Diego. Still, the bikes didn't seem out of place -- between the climate, the beach culture of San Diego and the transportation around the downtown area, the bikes seemed like a great complement to the transportation infrastructure there.

Last year there were only two options for electric scooters, Bird and Lime, and the actual number of scooters you saw was rather limited. While I used the bike share bikes for all of my around-town trips last year, I didn't rent a single scooter. In part, it was because the scooters were kind of hard to find, but some of it had to do with the whole scooter experience itself. For example, if I went for a late night run to the store for water and snacks, the idea of a nighttime ride back to the hotel on a scooter with an imbalanced load of groceries seemed like a good recipe for hitting the pavement. In contrast, most of the bike share bikes have baskets so that you could load a small amount of groceries in them.

This year, I saw only one GPS enabled bike company here, and bikes were few and far between. Instead, there are electric scooters everywhere. Everywhere. I saw scooters from three or four companies, including Lyft (something I hadn't seen before). There are also these little electric things that looks sort of like a mash-up between a bike and a mini-bike -- you sit on a bike seat to ride them, but they have something like 16" tires with bicycle disk brakes. There are no pedals, just foot-pegs. These things seemed to be a bit faster than scooters too.

The wholesale invasion of the electric scooters is kind a mixed bag. When I was getting ready to go to San Diego, I was actually looking forward to getting some bicycle time in, turning the pedals and burning some calories. Instead, there's not much for calorie burn on the electric scooters.

The scooters were okay for making the short trip from the hotel to the convention center faster. If you had your stuff in a backpack, you didn't really notice the load, but I don't know that someone with a briefcase style bag would say the same thing. That being said, the couple of times that I took a scooter out to restaurants in the Little Italy area, it was a ride that bordered on madness. Between the small wheels and the overall condition of the roads, each and every ride had moments when I thought that there was a better than even chance that I was going to crash -- and I would consider myself someone with better skills with my cycling background and decent sense of balance.

When I got off the scooter at the end of a scooter ride between Little Italy and the hotel, not once did I think, "man, that was fun. I can't wait to do that again."

Even more surprising for me were the times when I saw adults taking kids for a ride one of the scooters.

Ultimately, while I understand that the scooter model offers a lower cost element that enables these businesses to scale more easily and that the individual vehicles take up less physical space, I'm not optimistic about any sort of grand scale growth for this transportation alternative. I think it's only a matter of time before something like reports of serious injuries put a damper on the enthusiasm surrounding the whole electric scooter thing. I just wish that they would bring back the bikes.

Apple Ragnarøkkr

It's a new year and, following a warning from Apple on earnings, Apple's stock price has dropped significantly. In the warning, Apple blamed China's economy and consumer delays in upgrading their iPhones as key factors. Beyond problems with the economy and the monkey at the wheel flinging tariffs around, Apple's product problems have been a continuing trend, so it's hardly surprise that we're seeing that play out in their sales results. In terms of their product offering, the last time that Apple was this far off the rails, Steve Jobs came in for the turnaround rescue, reshaping not just the company, but the core product line. Something like that happening at this point seems rather unlikely, but rather than staring off into the distance looking for the rescue ship, let's drill down into some of the places where the current boat is taking on water.

In the earnings call, Tim Cook attributed part of Apple's revenue issue to people not upgrading their iPhones as quickly as they did in the past. For many in the media, this is directly related to the high price of the newest iPhones. Apparently, there has even been talk of price cuts across the iPhone line.

While I don't disagree with an assessment that the cost of the device is a big negative on the current line of iPhones, I don't think that that is the only answer. After all, I bought a new iPhone XS; however, in using it, I found the device to be so functionaly frustrating, I switched my phone back to my old iPhone SE. I carry the iPhone XS -- the camera is really good -- but I don't use it as a phone.

With the current state of the iPhone product line and the implied strategic direction, I expect that my next phone will come from eBay, since that's the only place that I can find an iPhone like the iPhone SE.

What's Wrong With Apple's Products
Apple's product mess extends far beyond iPhone X series. Over the holiday break, Macrumors published this post, "What do you want to See From Apple in 2019?" While lower prices topped the comment responses, you'll also see several top ranked comments focused on product. A couple of highlights include:

"Some new leadership, especially over in product." (the second most up-voted comment)

"Back to basic that Design is about how it works, not how it looks."

These comments echo the kinds of things being said within the professional design community where Apple products have been a staple for decades. Cast in a different light, these are things the "Pro" user community is saying.

Consider this Techcrunch post lamenting the loss of the headphone jack from over the break. Normally, I'd expect a "will the next iPhone include Bluetooth 11.7 Superband and theoretical 6G wireless?" from many of the tech blogs, but this post actually includes a look back at the history of the headphone jack on cellular phones. It's actually a nice walkthrough and a reminder of what a significant step it was for Apple to include a standard headphone jack on the iPhone and how that changed the industry. It was an important design decision that, by the time we got to 2016, Apple forgot it.

Why? The Techcrunch piece focuses on the idea of selling proprietary Airpods, but I think that is just another symptom because this disregard for the factors behind some of these design decisions, factors that were solved by Apple, then forgotten and abandoned. Good design understands history. Fashion follows the wind.

While I've written also about my complaints about the removal of the headphone jack, the removal of the MagSafe charging interface is another example of this same kind of disregard for the value and historical significance of the design. Over the years, I've has a number of Apple laptops. From Powerbooks to Macbook Pros, I've used and carried multiple versions over the years. Before MagSafe, all of my Apple laptops suffered from the same problem -- the charging connection became problematic and would only work in certain positions and my laptop became a desktop because I couldn't unplug it risking that I couldn't get it plugged in again. This issue was always caused by the same thing -- periodic accidental yanking of the cord like when the laptop was moved or when you happened to trip over the cord or such.

The MagSafe interface was a godsend. I can't tell you how many times the power cord was ripped from my laptop with the MagSafe connector on -- with no problem. Typically, these instances involved a few strong words, a sense of reassurance, and a return to work. Having spoken to product people in the PC industry, this was one of the most envied, desired features for PC laptops, but Apple's patent mojo was strong. There's a reason why Microsoft included a magnetic charging connection on it's Surface Pro devices.

And what did Apple replace it with? A USB-C charging interface that requires a special class of USB-C cables to charge the device. Gone is the magnetic connector. Gone is the LED that displays whether the device is charging -- another extremely popular, easily overlooked innovation that took multiple years and multiple product iterations to bring to market.

What's worse is that, while the old MagSafe charging port was kind of dumb, using a data-capable USB-C port for charging presents a potential threat vector. Back in September, I came across this article about hackers/security experts crafting a malicious USB cable that could be used to compromise a system in a few seconds. It's probably also worth noting that the USB-C standards body has just recently began to discuss an Authentication Program to protect against malware and firmware/hardware based attacks. So, while I haven't ever had to worry about malware and viruses through my laptop charger before, Apple's new systems have all incorporated this brilliant innovation.

Resistance to Upgrading
One of the factors cited by Apple in their recent earnings call was an observed slowdown in the rate of users upgrading from their existing devices. Some of this is similar to what we saw in the PC industry several years ago. While processor performance provided some percentage of performance improvements, when the base level of the device had reached "good enough" and perceived requirements were not growing at the same rate, people started holding onto their systems longer and longer.

Remember when the idea of "Netbooks" were all the rage? Remember how people were pushing for Apple to offer a Netbook? In a sort of response, Apple introduced the iPad and we all know how well that went. Looking back, we now know that Netbooks didn't really succeed in doing anything other than undercutting most PC hardware manufacturers' average selling price and devaluing their hardware on the whole. Meanwhile, the creeping trend for today's Apple has been increasingly trying to convince people that the iOS-driven iPad Pro is as good as a Macbook and that a lot of core iOS software framework should be used on the Mac.

If you didn't believe them initially, wait until you see how they've added an iPhone like LCD function-bar to your Macbook Pro so that you can watch your laptop battery juice ooze out. Can't believe on revolutionary and innovative it is? Wait until you see us add it to all of our other systems' keyboards (oh wait). Still concerned about how much power it might drain? Try our new "dark mode" in the Mac OS...

Remember when getting the Beatles on iTunes was a big deal? Little did everyone realize that "Helter Skelter" was going to become the soundtrack for Apple's product strategy.

To add insult to injury, you get things like this, Yes, the 2018 MacBook Air's FaceTime HD Camera is Awful. Yes, finally the venerable MacBook Air was upgraded in 2018. Finally it had a Retina display. Sadly, it was also the end of MagSafe and the end of USB-A support on Apple's portable line. Other than that, it seemed like a pretty decent upgrade -- until you started to look into the nooks and crannies and under the rug. Hidden from view, they stuck an Intel Y series processor. Of course, Apple didn't really play this up (and most consumers look at the "i5" or "i7 number), but many of the things that I read were poo-pooing this decision.

I could go on for a while with more examples. Perhaps the simplest thing to say is, many people characterize this reluctance to upgrade being driven by price or a lack of innovation driving enough need/interest in newer hardware (remember when everyone was looking for "the killer app"). I think that there may be a third contributing explanation that is being under-factored into a reluctance to upgrade -- a concern that from a quality and utility perspective, the newer product is going to be worse by many degrees of measure.

Is this Apple Ragnarøkkr -- the "twilight of the gods"?

Apple Denies "Spy Chip" Story

You may have already been following this, but Apple has now denied the Bloomberg spy chip story a couple of times. Here's my original post, Has Your Electronic Hardware Been Hacked?, and the original Bloomberg post, The Big Hack: How China Used a Tiny Chip to Infiltrate U.S. Companies. Techcrunch has a prior story with links to more of the denials.

While I'm in no position to know whether the story is valid or not, it can be an interesting exercise thinking about why the various respective parties might have an interest in denying the story. Similarly, it's probably worth spending a bit of time thinking about why, if it isn't true, the story was published and what might be behind it.

All of that being said, thematically, concerns about technology back doors being placed into electronic devices -- and the implications of these vectors -- will continue to be an ongoing theme.

Caveat Emptor.

------- Update:  ----------

You may find this to be pushing into the "conspiracy" end of the spectrum, but here's an interesting look into some of the nuances of the language of rebuttals from the Emptywheel blog. There's also a good breakout of the story into a timeline with links to some of the stories at the time they emerged (I found the Apple, SuperMicro firmware thread to be particularly interesting.

Rattled: China’s Hardware Hack 

There are more posts breaking down the language in some of the denials, but this one has the timeline.

Why I switched from a new iPhone Xs back to an iPhone SE

The one thing that I was hoping for in the Apple iPhone announcement back in early September was an updated iPhone SE. While I'd seen enough on the Apple rumors sites to be concerned that, if the rumored updates to the iPhone SE were true, I'd probably be unhappy with that device. As it was, the rumors sites were talking about a glass-backed iPhone SE with no audio port and no home button -- but I tried to remain optimistic. I'd even considered, in the days prior to the iPhone Xs announcement, purchasing a 128GB iPhone SE just so that I'd have a new one without 2 years of wear and tear on it.

Don't get me wrong, my iPhone SE is still a great phone that still only shows minor scrapes and scratches despite two years of life without a case.

At the same time, you couldn't help but notice the better image quality from her iPhone 8. It didn't help that there were three little spots that I kept seeing in my photos, imperfections that I came to realize was probably the result of damage to the camera lens.

With the iPhone Xs announcement, I'd hoped that Apple would, at least, continue to sell the iPhone SE - dated as it is/was. Seeing it EOLed was probably the worst aspect of that announcement.

So, grudgingly, when orders opened up for the new iPhone Xs back in September, I ordered one. It sounds like a simple decision, a simple action, but it was something more. At the time, I rationalized my decision a couple of ways.

First, I told myself that I'm adept enough with electronics that I could overcome the failures of the design in the iPhone Xs. After all, I thought, how bad could it be? I was sure that, while it might be mildly frustrating at times, I would be able to use the device and would benefit from the new camera. What was surprising was how wrong that prediction turned out to be.

From a size standpoint, I thought the iPhone Xs would end up being about the same size as the iPhone 8. Having used an iPhone 6s Plus for a year, I knew that that phone was just way too big, but I was under the impression that the iPhone X brought something close to a "Plus" size screen into the smaller non-plus sized body. While I knew that it would be larger, I wasn't prepared for how large the iPhone Xs turned out to be.

This week, after almost three weeks of using the iPhone Xs, I switched my phone back to my iPhone SE.

As I used the iPhone Xs, a number of issues because clear. First, while the whole notion of Face ID seemed like an idiotic authentication interface to me, in practice, it proved worse. While I'd initially been impressed with it's ability to recognize me and unlock the device -- almost like it authenticated without effort -- as I used it day-in-and-day-out, I began to notice that it seemed like it failed more often than it succeeded. Running the out-of-the-box software configuration, Face ID fails when you're wearing sunglasses. In other words, when you're using the device outside, you have to stop what you're doing, lift up your sunglasses and force the device to authenticate. It's worth noting that the fingerprint sensor on my iPhone SE worked equally well inside and outside, without regard to whether you were wearing sunglasses.

Face ID also often failed to work if I tried to access my iPhone while it was sitting on my desk in front of me, at a table in a restaurant or a number of other locations that I tried to casually access my iPhone from.

So, imagine yourself at lunch with a colleague and you hear your phone chime indicating that you'd received a text. With iOS 12, the default information displayed on the lock screen is that your received a message from a specified contact. In order to view that on the iPhone Xs, you have to pick up your phone and look at it, something that can be disruptive and be perceived as rude. In contrast, with the fingerprint ID, you can simply touch your iPhone, look down, and you can see whether the text is important or not.

I can't tell you how many times I repeatedly went through scenarios similar to this, particularly since, for many text messages, all you really need to do is determine whether the message is important or not. And worse, because the iPhone Xs locks quickly, you can find yourself having to repeat the whole exercise multiple times in during a single window of receiving multiple texts. It's not just bad, it's terrible.

Additionally, I thought that the lack of a headphone jack might simply be an inconvenience that I would get used to. In practice, I found that this also wasn't true. I should note that, prior to my iPhone Xs, I used my iPhone for all of my telephone communications. It's also worth noting that, while I have Apple Airpods and I use them as a Bluetooth headset when driving or some other activities, when I need to make calls where I want to ensure the audio quality of the call, I use the Apple earbuds that came with the phone. Often, sitting at my desk, I would have my iPhone SE plugged in and charging while using the earbuds for a call.

With the iPhone Xs, initially I brought the lightning based earbuds along, but I soon found myself trying to decide whether to charge the iPhone or to plug in the headset and make a call. Over nearly three weeks of use, I found myself hesitant to make phone calls. Eventually, I put my Lighting earbuds into my backpack and only took them out once or twice. Essentially, whether it was just psychological or practical, I realized that my iPhone Xs was barely functioning as a phone.

Another aspect that anticipated how much of a problem it would be was the lack of a home button. I wish I could tell you how many times I used a "Sweep Up" gesture on the device with no results. It doesn't just fail once or twice, I would estimate the failure rate at greater than 20%. You might argue that the case is a contributing factor, but I don't think that's actually the case. This failure to function has a significant impact on how well the device functions day to day. For example, if you have a problematic app and you want to "double-tap" the home button in order to bring up the multi-task screen and kill the app, you may find yourself trying for 20-30 seconds before getting the interface to change. That's just one example. It happened more frequently than I would have imagined, ane particularly frustrating if you're trying to do something like kill an app.

----

So, after a particularly frustrating round of receiving texts on my iPhone Xs and wrestling with the device functionality just to access them, I decided that I was done with it -- that I was going to switch back to my iPhone SE. I figured that I could simply carry the iPhone Xs around, using it for it's camera functionality and, since it was sometimes convenient to have the larger display, use it as a wifi-based device when I needed the larger display. If I need network access, I could simply use my iPhone SE to create a hotspot for the Xs.

I wish I could share with you the immense sense of joy that I felt once I switched back. Holding the smaller device in my hand brought me an unexpected sense of elation.

At this point, I've been back on my iPhone SE for a couple of days and I'm much happier. The iPhone Xs is sort of like having a pocket-sized iPad. At this point, give me old, obsolete Apple over the new Apple. Whether you want to blame it on Tim Cook, elements in the org further down, or something else, the company is just not doing design and functionality the way that they used to.

Has Your Electronic Hardware Been Hacked?

This is something that you should read. The Big Hack: How China Used a Tiny Chip to Infiltrate U.S. Companies is a story from Bloomberg Businessweek about SuperMicro server motherboards being hacked by the Chinese military, adding a hardware device to the board enabling access to the server. The hardware device was designed to look like an innocuous component, and the compromised servers may have gone to companies like Apple and Amazon, into their AWS cloud.

If you're looking for more analysis, here's a Techcrunch post on the article.

Needless to say, these are worth your time to read.

I got an iPhone Xs. I hate it.

So I've written a number of posts on Twitter talking about the recent Apple product announcements and how the company has quit designing phones that match my needs. I was particularly disappointed with the recent announcements when they EOLed the iPhone SE. For the past two years, I've been using a 64GB iPhone SE, the best iPhone I could get when the iPhone 7 came out and Apple abandoned the headphone jack.

For the past two years, I've used the iPhone SE. While the smaller display can be frustrating at times, I think that most of my frustration with the display was that Apple has designed the software for much larger screens. Even while they claim the UI is responsive and can adapt to screen size changes, it turned out that changing that setting in iOS 11 and making the type and interface larger caused significant performance issues on iPhone SE. Apple Support helped me diagnose that back in March of this year.

After two years using my iPhone SE, it's still a great phone, but it's been wrestling with a few small issues. What we noticed the most was the significant difference in the camera performance between the iPhone SE and my wife's iPhone 8. In addition to the photos on the iPhone SE not having anywhere near the clarity of those shot on the iPhone 8, my iPhone SE has picked up a few blemishes on the camera lens that shows up as spots on photos. Normally, I might not care -- at least, I wouldn't care enough to downgrade and loose my headphone jack -- but as noted in a previous post, we have a two-year old son that we like to take lots of picture of. When you have to wait to get someone else's phone to take a picture (or it goes to sleep and you need to re-authenticate), it sucks. This is what drove me into an iPhone Xs purchase.

My new iPhone Xs arrived on Friday, and I've used it over the weekend. As noted in the title, I hate it.

Before I tell you about all of the ways that I hate it, in keeping with one of my college writing classes, I'll start by saying something nice about it. Something I like. The camera. It's great. While it's possible to manipulate your images in Photoshop to match the portrait mode effects, the iPhone Xs captures these kinds images simply and easily. It really works well. The shots are beautiful.

Other things that I've found to be nice about the iPhone Xs -- Face ID works better than I expected. Often, if the iPhone is looking at you, Face ID will unlock the device. That being said, if I'm wearing sunglasses (like when I'm using the iPhone outside at the farmer's market), it won't work unless I lift up my sunglasses. It also doesn't like it when the device is laying on the table, looking up at me. This seems even more problematic when I'm wearing glasses. In short, for all of the times when it knows me, there are many annoying times when it doesn't. In general, my fingerprint worked better (it only failed when my hands were wet or when the sensor got dirty).

Now, let's get to the things about the iPhone Xs that suck.

It's really big. It's been a while since I had the iPhone 6s Plus, but the iPhone Xs feels big like that. And this is the smaller device. Imagine how big the Max must feel. In short, the iPhone Xs has the same problem that I had with the iPhone 6s Plus -- it's too damned big.

For comparison, here are the two versions when I hold them in my hand.

Holding the iPhone SE - front facing

Holding the iPhone Xs - front facing

Holding the iPhone SE - side view

Holding the iPhone Xs - side view

While it may not seem like much of a difference from the images, you can kind of see how much more open my hand is holding the iPhone XS. In real world interaction, this translates into less grip on the phone and, from my previous experience, a greater likelihood of drops. It also makes it extremely difficult to use the device with one hand. In contrast, with my SE, I can spin the device around in my hand without really loosing my grip on it.

You know what's even better than an iPhone that's so big, it's difficult to hold onto? Making the iPhone enclosure almost entirely of glass. Take a look at a couple photos of my iPhone SE.

I've been using this device for two years without a case. As you can see, it has sustained a few drops. What I've highlighted with these two photos are two corners of the iPhone where you can see that the phone took a pretty significant impact. In the top corner photo, it hit the asphalt so hard that it took a big cut out of the metal. Rather than leaving a sharp edge, I used a nail file to smooth the metal, something that required me to sand it down below the surface metal to the red material below.

Would an iPhone XS survive these kinds of impacts? In a case, perhaps, but a bare iPhone Xs? I'd bet not.

I don't think that I'm particularly hard on my devices. I would consider this normal wear and tear. But it does give you a sense of the design priorities driving Apple's iPhones these days.

So, let's move on to more things that suck.

All things charging suck. Pick a topic - wireless charging? I don't have it, haven't imagined I'd need it, nor would I have ever traded my metal enclosure for it -- or the headaches associated with another glass-backed iPhone. There was a reason why the iPhone 5 was a huge improvement over the iPhone 4.

But beyond the glass, why should I have to go out and spend another $50+ for a wireless charging mat when the only thing I can charge with it is this stupid iPhone - particularly when I can just as easily guarantee that the device is being charged when I plug it in.

Then there's the BS "fast charging" feature. Note that this only works IF, you spend another $60 with Apple to buy their more powerful charging brick and another $30 for their USB-C to Lightning cable, neither of which are useful to me or anything other than fast charging the stupid phone.

But don't get me wrong, after I experienced half a day of battery drain on Saturday, I considered fast charging. It's probably worth some analysis and comparison, but if I didn't know any better, I'd almost think that Apple slowed the regular charging speed on the iPhone Xs -- even using the iPad charger, it charges painfully slow and the battery usage seems high.

What else sucks about the iPhone Xs?

No home button really sucks. Yeah, they've figured out a way to make the interface run without a home button, but it doesn't work well. Essentially, sliding up from the bottom edge of the screen is supposed to equal a home button. Sometimes it works, sometimes it doesn't. There are times I've had to make 3 or 4 swipes up just to get the interface to do what it's suppose to.

Perhaps the bump created by the bottom edge of the case makes your finger skip, but would you even consider carrying this expensive piece of glass without a case?

The other thing that comes into play with the iPhone Xs is, since there isn't a home button, it wants to wake up whenever you touch the phone or it moves. This leads to lots of false wake-ups. At the same time, whenever it wakes up, it also starts to look for your face -- I suspect that this may contribute to why it seems like the battery drains as fast as it does. Maybe it's just me (or maybe it's the default auto-lock setting on this device), but it also seems like it goes to sleep faster than it did previously. Maybe that's a feature to highlight how well their Face ID works.

It goes without saying that the lack of a headphone jack also sucks. First, there was the "I need to carry two pairs of headphones with me to work today, one for this stupid iPhone Xs, and one for everything else." Then, when I got to work, I plugged my iPhone in to recharge from listening to streaming audio on the way in during the commute. I briefly thought about listening while I recharged the iPhone, something I could have done in the past, but quickly remember that I can't do that on this stupid iPhone.

Bottom line -- yeah, it sucks. It sucks, but the camera is great.

At this point, I've considered switching back to my iPhone SE as my primary phone, disabling the cellular on the iPhone Xs and just using it as a camera. It's a difficult decision, but it seems like the kind of decision that Apple is forcing us to make these days. In the same way, caught between choosing a new Macbook Pro or a refurbished pre-USB-C version late last year, we opted to buy Apple products that were, essentially, three years old. It really says something about the state of Apple, doesn't it.