As a developer, when it comes to your web application, you want to make sure that you have the best project setup that will enable you to focus on your development without any issues.
You probably will look for a boilerplate with a small example, a build-ready project that you can just take its result and deploy it.
When you look at the bigger picture, and you need to define the infrastructure for a project that will give you full flexibility to add features, a project that includes placeholders for core functionality, business logic, configuration, common functionality, routes, translations, state-management…
Role based access control is a policy access control defined around roles and permissions.
In the early stage of the design for your web application and in case you are planning to enable authentication you may consider to implement roles-based-authorization mechanism to control what will be displayed to the end-user and what would be enabled or disabled according to pre-defined set of rules.
In the following, I am going to show you a simple approach how it can be done with minimal coding, We want to make sure that this mechanism will be standalone and maintainable by the development team…
Nowadays spinners are one of the most important parts of your web application, most of the asynchronous activities need to be indicated to the user in some way and the most common way to do it is with a spinner, a gif, that you display and hide when such activities finish their work.
In this article, I am going to show you how I wrote my spinners, How I am integrating them with my React-based web application in a way that they work as a standalone mechanism, Shall we?
When we talk about asynchronous activities, the first thing that came…
Once delivering your web application to the end-user, you want to make sure that the client receives the best user experience, You don’t want dead ends in your app, every flow, every page has its own starting-point and ending-point.
So you have a plan how to create your website, you listed all the 3rd parties that you are going to use and you setup your backend to deliver the data for your web application and now the story begins.
When we design a well-planned web application, we want to make things as simple as possible to make our life easier…
Nowadays there is an increased demand for fast response web applications, product owners, Users want to get their feedback from the website without waiting even a second, we want to make sophisticated activities but still keep our code clean and simple.
Think about creating live stock dashboards, support chats for e-commerce websites and the list is long.
You might say that we are probably going to talk about WebSockets and you are right! nonetheless I am going to show you something slightly different.
Software Architect at Amdocs