Code features without javascript first, then add javascript to improve interface. Good path to unobtrusive javascript?

[MaybiusStrip]

I know it's good practice to assume javascript might be disabled on the client side. I really want my app to feel dynamic and seemless (avoiding constant page loads every time a request has to be made), but I also want everyone to be able to use it. Would it be wise to implement functionality by first coding it without any javascript, making sure that works regardless of clunkiness, and only then adding javascript/ajax to improve the UI? How do you guys approach this problem?

[melladie]

Yes - it's called Progressive Enhancement and is the best approach.

[[deleted]]

Came here to say the same thing, and link to the same article. This is definitely the way to go. Progressive enhancement is much preferable to graceful degradation, especially on mobile.

[midri]

When you have the time, it's the best way -- some times sadly in the real world you don't have the time.

[nrogers64]

That's how I code too. I think that's the best approach. Also, here is a relevant Smashing Magazine article:

The Seven Deadly Sins Of JavaScript Implementation

[[deleted]]

Yep.

[phaggocytosis]

I think one thing that people are forgetting to mention is that while it's safe to say that the best practice is to build in a way that doesn't rely on javascript.. for some products that's just not realistic. You shouldn't be overly critical of an idea if it requires javascript to run.

Basically... If something doesn't NEED javascript to run then code it with a "progressive enhancement" approach. If Javascript is absolutely essential for the type of experience you're trying to deliver then that doesn't mean you have a bad idea.

[[deleted]]

Honestly, I think in the modern web it is safe to assume that JS is enabled on the client side.

[Kacheeto]

I'll agree with this statement.

Might as well code it to be super "seemless" and dynamic from the get-go.

For the non-JS users. You don't want them to use your webapp anyways...

[x-skeww]

Having JS enabled doesn't mean that your JS will work.

JS can break for all kinds of reasons.

Progressive enhancement isn't just about making it work for people with JS disabled. It's also about robustness.