Nestle, Bharti Airtel, Bajaj Finserv, ICICI Bank and Maruti were the other big laggards

The BSE Sensex plummeted 662.87 points or 0.83% to settle at 79,402.29. The NSE Nifty tanked 218.60 points or 0.90% to 24,180.80

Equity indices fall due to foreign fund outflows and muted earnings, with Sensex and Nifty declining in early trade

Forex traders said the strength of the American currency in overseas markets dented investor sentiments, while easing crude oil prices and any intervention by the Reserve Bank of India (RBI) may support the local currency at lower levels

At the interbank foreign exchange, the rupee opened at 84.06 against the greenback. It traded in a tight range and ended the day at 84.09 (provisional), down 4 paise from its previous close

Why is gold considered a safety cushion by central banks? When does demand for the yellow metal peak in India? Why does the World Gold Council expect an increased demand for gold from rural areas? What factors determine gold prices?

The BSE Sensex declined 326.58 points to 78,455.66 in early trade

Forex traders watch U.S. election impact on markets as rupee hits record low against dollar, with RBI intervention expected

U.S. stocks rally on election day, with S&P 500 and Dow Jones climbing, despite uncertainty over results

The U.S. Fed is expected to announce a rate cut in a meeting scheduled later this week, with further easing of up to 100 basis points projected for 2025

Market analysts said unabated foreign fund outflows and mixed global cues further dented investor sentiments

Stock markets tumble over 1% as investors await U.S. Fed decision, with Sensex and Nifty dropping significantly

The rupee touched fresh record lows again on the back of weak domestic equities and sustained FII outflows

Heat stress is repeatedly causing disruptions in ecological and economic systems, SPC report titled ‘Beating The Heat-Tamil Nadu Heat Mitigation Strategy’ said.

Chennai district collector has declared holiday for schools on November 12 owing to rain

BJP’s Tamilisai Soundararajan says that it is not necessary that only parties with similar ideologies should form an alliance

Andy Bell rings out a fresh call in support of the timeless concept of progressive enhancement. What does it mean to build a modern JavaScript-focussed web experience that still works well if part of the stack isn’t supported or fails? Andy shows us how that might be done.

Those that know me well know that I make a lot of side projects. I most definitely make too many, but there’s one really useful thing about making lots of side projects: it allows me to experiment in a low-risk setting.

Side projects also allow me to accidentally create a context where I can demonstrate a really affective, long-running methodology for building on the web: progressive enhancement. That context is a little Progressive Web App that I’m tinkering with called Jotter. It’s incredibly simple, but under the hood, there’s a really solid experience built on top of a minimum viable experience which after reading this article, you’ll hopefully apply this methodology to your own work.

What is a minimum viable experience?

The key to progressive enhancement is distilling the user experience to its lowest possible technical solution and then building on it to improve the user experience. In the context of Jotter, that is a humble <textarea> element. That humble <textarea> is our minimum viable experience.

Let me show you how it’s built up, progressively real quick. If you disable CSS and JavaScript, you get this:

This result is great because I know that regardless of what happens, the user can do what they needed to do when the loaded Jotter in their browser: take some notes. That’s our minimum viable experience, completed with a few lines of code that work in every single browser—even very old browsers. Don’t you just love good ol’ HTML?

Now it’s time to enhance that minimum viable experience, progressively. It’s a good idea to do that in smaller steps rather than just provide a 0% experience or a 100% experience, which is the approach that’s often favoured by JavaScript framework enthusiasts. I think that process is counter-intuitive to the web, though, so building up from a minimum viable experience is the optimal way to go, in my opinion.

Understanding how a minimum viable experience works can be a bit tough, admittedly, so I like to use a the following diagram to explain the process:

Let me break down this diagram for both folks who can and can’t see it. On the top row, there’s four stages of a broken-up car, starting with just a wheel, all the way up to a fully functioning car. The car enhances only in a way that it is still mostly useless until it gets to its final form when the person is finally happy.

On the second row, instead of building a car, we start with a skateboard which immediately does the job of getting the person from point A to point B. This enhances to a Micro Scooter and then to a Push Bike. Its final form is a fancy looking Motor Scooter. I choose that instead of a car deliberately because generally, when you progressively enhance a project, it turns out to be way simpler and lighter than a project that was built without progressive enhancement in mind.

Now that we know what a minimum viable experience is and how it works, let’s apply this methodology to Jotter!

Add some CSS

The first enhancement is CSS. Jotter has a very simple design, which is mostly a full height <textarea> with a little sidebar. A flexbox-based, auto-stacking layout, inspired by a layout called The Sidebar is used and we’re good to go.

Based on the diagram from earlier, we can comfortably say we’re in Skateboard territory now.

Add some JavaScript

We’ve got styles now, so let’s enhance the experience again. A user can currently load up the site and take notes. If the CSS loads, it’ll be a more pleasant experience, but if they refresh their browser, they’re going to lose all of their work.

We can fix that by adding some local storage into the mix.

The functionality flow is pretty straightforward. As a user inputs content, the JavaScript listens to an input event and pushes the content of the <textarea> into localStorage. If we then set that localStorage data to populate the <textarea> on load, that user’s experience is suddenly enhanced because they can’t lose their work by accidentally refreshing.

The JavaScript is incredibly light, too:

const textArea = document.querySelector('textarea');
const storageKey = 'text';

const init = () => {

  textArea.value = localStorage.getItem(storageKey);

  textArea.addEventListener('input', () => {
    localStorage.setItem(storageKey, textArea.value);
  });
}

init();

In around 13 lines of code (which you can see a working demo here), we’ve been able to enhance the user’s experience considerably, and if we think back to our diagram from earlier, we are very much in Micro Scooter territory now.

Making it a PWA

We’re in really good shape now, so let’s turn Jotter into a Motor Scooter and make this thing work offline as an installable Progressive Web App (PWA).

Making a PWA is really achievable and Google have even produced a handy checklist to help you get going. You can also get guidance from a Lighthouse audit.

For this little app, all we need is a manifest and a Service Worker to cache assets and serve them offline for us if needed.

The Service Worker is actually pretty slim, so here it is in its entirety:

const VERSION = '0.1.3';
const CACHE_KEYS = {
  MAIN: `main-${VERSION}`
};

// URLS that we want to be cached when the worker is installed
const PRE_CACHE_URLS = ['/', '/css/global.css', '/js/app.js', '/js/components/content.js'];

/**
 * Takes an array of strings and puts them in a named cache store
 *
 * @param {String} cacheName
 * @param {Array} items=[]
 */
const addItemsToCache = function(cacheName, items = []) {
  caches.open(cacheName).then(cache => cache.addAll(items));
};

self.addEventListener('install', evt => {
  self.skipWaiting();

  addItemsToCache(CACHE_KEYS.MAIN, PRE_CACHE_URLS);
});

self.addEventListener('activate', evt => {
  // Look for any old caches that don't match our set and clear them out
  evt.waitUntil(
    caches
      .keys()
      .then(cacheNames => {
        return cacheNames.filter(item => !Object.values(CACHE_KEYS).includes(item));
      })
      .then(itemsToDelete => {
        return Promise.all(
          itemsToDelete.map(item => {
            return caches.delete(item);
          })
        );
      })
      .then(() => self.clients.claim())
  );
});

self.addEventListener('fetch', evt => {
  evt.respondWith(
    caches.match(evt.request).then(cachedResponse => {
      // Item found in cache so return
      if (cachedResponse) {
        return cachedResponse;
      }

      // Nothing found so load up the request from the network
      return caches.open(CACHE_KEYS.MAIN).then(cache => {
        return fetch(evt.request)
          .then(response => {
            // Put the new response in cache and return it
            return cache.put(evt.request, response.clone()).then(() => {
              return response;
            });
          })
          .catch(ex => {
            return;
          });
      });
    })
  );
});

What the Service Worker does here is pre-cache our core assets that we define in PRE_CACHE_URLS. Then, for each fetch event which is called per request, it’ll try to fulfil the request from cache first. If it can’t do that, it’ll load the remote request for us. With this setup, we achieve two things:

1. We get offline support because we stick our critical assets in cache immediately so they will be accessible offline
2. Once those critical assets and any other requested assets are cached, the app will run faster by default

Importantly now, because we have a manifest, some shortcut icons and a Service Worker that gives us offline support, we have a fully installable PWA!

Wrapping up

I hope with this simplified example you can see how approaching web design and development with a progressive enhancement approach, everyone gets an acceptable experience instead of those who are lucky enough to get every aspect of the page at the right time.

Jotter is very much live and in the process of being enhanced further, which you can see on its little in-app roadmap, so go ahead and play around with it.

Before you know it, it’ll be a car itself, but remember: it’ll always start as a humble little <textarea>.

About the author

Andy Bell is an independent designer and front-end developer who’s trying to make everyone’s experience on the web better with a focus on progressive enhancement and accessibility.

More articles by Andy

As the #IWearHandloom campaign gathers steam, a look at some of the new players in Hyderabad’s handloom sector

Designer Neeta Lulla on the fairytale-like silhouettes for Samantha Ruth Prabhu’s mythological romance drama ‘Shaakuntalam’

Sip a coffee as you browse designer brands at the recently-opened The Galleries at 32nd in Gurgaon

Blossom Kochhar says if you can eat it, it can be used on your face.

Experts share cool tips for a hot weather workout.

While the IMD has strived to improve its predictive models, global warming is the wild card factor

A surge in prices of fuel, metals and industrial feedstock led to a spike in production and operating costs this quarter, denting profit growth

It is increasingly being realised that achieving net-zero is not possible without nuclear energy

Land records remain contested, despite over 90 per cent digitisation. Concerns over data theft and cyber fraud cannot be disregarded

The incentives for all private vehicles are lower than under the five-year FAME 2 scheme which came to a close this April

Kashmir’s heartening turn towards electoral politics

MFIs should not justify steep rates with access issues, says Jayant Kr Dash, Executive Director; Senior RBI official suggests Blended Finance could hold some answer for this issue

Net interest margin rose to 9.7 per cent in Q2FY25 against 9.4 per cent in Q2FY24

Zuno General Insurance continued to grow faster than the industry in the second quarter of this fiscal, says Shanai Ghosh, MD & CEO of the company

Bankers expect pressure on NIM to continue in Q3

The NPAs on block were part of YES Bank’s legacy bad loan portfolio.

All 3,443 complaints received in 2023-24 have been disposed, says Sunita Sharma, Insurance Ombudsman 

Montreal : National Film Board of Canada, 2008