Automated integration tests

Testing states

Two routes

Back and forth costs time

Consider states

Designs for everythin in spec

Budgets squeezed

Fewer staff

Push for improvement

Components portable between projects

Each unique element has a cost

Grid designs

Reusable templates

Outsource functionality

Small pieces lossely joined

Be a small piiece in someone else's puzzle

Save money buy renting expensive solution via API time

Limit scope

Prevent overspend

Control cost on paper

Plan efficiently up front

No surprises!

Broadband is not ubiquitous

Servers are not free

Efficient front - and - back end code

Consider running costs

Don't reinvent the wheel

Evaluate options against spec

Consider design compromises to use off-the-shelf solutions

Buildjust the 10% that's unique

Tech implications of visual choices

Weigh against time to build

Small compromises =big savings?

Learn on modern browser capability

Post-launch costs

Flexible designs

Varying content