A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Just published 15,000+ words on security keys. 🔐📱💻

With SIM attacks at their highest, now is a great time to take a closer look at your online security.

Removing SMS from your two-factor auth is a start, but authenticator apps have downsides too...

https://t.co/Dk0MPJHL2V

Just look at these headlines from recent SIM swap and port attacks.

It's all too established for attackers to find ways to socially engineer control of your phone number and start gaining control of your accounts.

I first talk about some general security tips.

Unfortunately not all websites let you remove your phone number from accounts.

You may consider migrating your phone carrier to @googlefi , which requires email account access to do anything (and can be locked down with security keys and even Advanced Protection)

Beyond SMS, I talk about issues that TOTP authenticator apps (the code generators) have as a form of two-factor auth. They're so, so much better than relying on SMS for your second factor but they still have issues like utilizing shared secrets and lacking phishing prevention.

Enter security keys!

Utilizing public key cryptography they don't have any shared secret between the client and the server. They prevent phishing by taking the website domain into account.

Even if you get tricked by a clone phishing website, your key won't.

For decades, Jeff Bezos shunned ads.

But now, Amazon’s ad business is huge: it’s on a $30B+ annual run rate (more than 2x the combined sales of Twitter, Snap and Pinterest).

Here’s how it happened 🧵

1/ Amazon doesn’t break out its ad business separately in financial filings. However, most analyst believe ads make up the majority of its “Other” revenue segment.

This figure has exploded from $1B in 2015 to a current annual run rate of ~$32B.

2/ In 2009, Bezos said “ads are the price you pay for a crappy product”.

But the business is so lucrative that Amazon’s interface has been swamped with ads:

◻️ First 3-7 search results (left in red)
◻️ Most of the product page (right in blue)

3/ Prior to the rise of ads, Amazon set out to build the ultimate organic customer recommendations engine.

The approach was codified in a famed 2003 research paper: “Amazon Recommendations: Item-to-Item Collaborative Filtering.”

4/ In recent years, Amazon organic recommendations:

◻️"Customers who bought this also bought this"
◻️"Customers who viewed also viewed"

Have been replaced w/ ads:

◻️ "Sponsored products related to"
◻️ "Brands related to this category"

#UX and #design friends, we need to talk about estimating. I'd like to share some advice that's come up 3 times this week, in hopes it's useful. And it's echoed, by the way, in the BUSINESS OF UX course @EliNatoli and I are teaching at my UX 365 Academy (link at the end).

(1/12)

Avoiding wars with clients is a matter of how you structure your engagements, along with how you spell out what you're doing in your proposals/contracts. That starts with estimating.

The biggest 2 rules I follow are these:

(2/12)

1. I do not EVER estimate a project in full from start-to-finish.

2. Once we're past initial Discovery (see below), I estimate in small chunks, e.g. "here's what will take us to the next iteration/review."

(3/12)

NEVER estimate past the point where you may get new information based on a build/test cycle.

Believe me when I say that you'll be wrong every time. Ask me how I know ;-)

(4/12)

So instead, first, I estimate a Consult/Discovery part that details what I think we need to do to get a handle on what's actually wrong here, and how long that will take.

For example...

(5/12)