responsive principles

1

Responsive Principles

More than designing for size

@shoobe01 #float2012

22

Learn by typing, talking, and sharing.

33

Select a platform first, right?

44

Lies, damned lies, and statistics.

55

You are screwing yourself.

66

Fragmentation is great.

77

Design for every platform, and every screen.

88

Design responsively, right?

99

Responsive design isn’t new.

1010

But that’s okay.

1111

Device detection and server-side software.

1212

RESS isn’t new, either.

1313

But it’s a convenient acronym.

1414

1515

Design beyond pixels.

1616

Percent? Em? Point, pica, mm, inch, twip.

1717

Design for the real world.

1818

1919

2020

2121

2222

2323

Respond to more than scale.

2424

2525

Principles > Patterns > Templates > Pages

2626

Features != pages

2727

2828

Design for every screen.

2929

Then design for each screen.

3030

Enhance for each platform.

3131

Stick to your principles.

3232

Design to make decisions.

3333

Products, not platforms.

3434

Customers, not users.

3535

Is it still any good?

3636

Is it still the right thing to make?

3737

Then change your principles.

3838

Execute for every screen.

3939

Data and services first.

4040

Build for the future.

4141

Layers and planning.

4242

Do everything once.

4343

Platform teams should borrow and cheat.

4444

Yes.

4545

4646

Don’t copy that last chart.

4747

Actually, don’t copy anything I’ve done.

4848

Principles > Patterns > Templates

4949

Principles > Practices > Tactics

5050

Responsive,native,physical,buildable,extensible.

51

Steven Hoober

steven@4ourth.com

+1 816 210 0455

@shoobe01

shoobe01 on:

www.4ourth.com