Imagine we have a PWA and it’s an online shop. Usually, we navigate between products and check them. When you like a product, you may check it many times and it has a bad experience if every time you should wait for getting product data from the server. We have two solutions to have a better experience.

One. Using Redux (Not recommended)

We can use Redux and have a state to push the product data in this state. But when you have developed a large scale application, It’s not a good solution.

Two. Cache Requests (Recommended)

CACHE REQUESTS. Why using Redux until you can cache requests?

We can have cache storage to store the requests data and when an API request called, first we looking for the response in the cache storage, and if we don’t have it, now we need to call the API request.

We have many ways to implement this feature and I will show you some of them.

• You can implement it as the following:

Or if you are using axios, you can also use axios-extensions or axios-cache-adaptor packages.

Stop using Redux, cache requests was originally published in Dev Genius on Medium, where people are continuing the conversation by highlighting and responding to this story.

In most websites, Users can log in using the OTP code. When you receive the OTP code, it’s so boring to leave the browser and go to the messages and see the OTP code.

Now, I want to tell you a way to show the OTP code in the iOS keyboard like the following.

How to implement this feature?

First of all, you should set auto-complete=”one-time-code” on your input like the following:

<input type="tel" name="otp-code" auto-complete="one-time-code" />

Now, it’s time to update your SMS message. You should have "code” word in your SMS message.

For example: Code: 123456 is your verification code

Autofill OTP code in iOS was originally published in Dev Genius on Medium, where people are continuing the conversation by highlighting and responding to this story.