Theme development, Module 4, lesson 22, 14 min

The constraint puzzle: a countdown, no app

From

Priya Nair

Founder & CEO

Monday, 8:15am

Countdown for the drop. No apps.

you. Cold Brew Season drop goes live this week and I want a countdown in the announcement bar, urgency works.

One constraint: I'm not installing a countdown app. We're cutting monthly fees, not adding them. Figure out the right way, then build it.

Priya

How this works

The feature is trivial. The constraint is the lesson: the client wants a countdown and refuses a paid app. Your first move isn't code, it's choosing the approach that honors the constraint without creating a maintenance trap.

Make the call. The right road puts the deadline where the merchant can edit it (a section date setting rendered into a data-ends attribute) and keeps the JS to arithmetic: milliseconds remaining, split into days, hours, minutes.

Why this matters in production

The 'they want X but refuse the app' ticket is weekly agency life. Countdown apps charge monthly for what is, natively, a date setting and twelve lines of JavaScript. Knowing when native wins is billable judgment.

Report a bug or suggestion

Architectural decision

Priya wants a countdown and refuses an app. What do you build?

The scenario

The announcement bar needs a live countdown to the Cold Brew Season drop deadline. Priya will move the deadline at least once (she always does). She will not pay for a countdown app. The store has no other use for one.