As your application complexity increases, you may start thinking about implementing a session timeout in instances when there is no activity for a period of time. Whether you want a session timeout to increase your web app securities or to avoid unnecessary automatic API calls, it’s good to have some sort of idle check and log out built into your application.
State machines are an old concept. They are a proven solution that provides a solid architectural foundation for application processes. In this article, I hope to provide an introduction to what they are and how they can be useful for a modern web or mobile application engineer. We’ll be focusing on one library in particular – xstate – and how it can allow anyone to easily leverage state machines for managing global or component state.
Keyhole Labs has announced the release of Version 2.0 of its free UI design tool MockOla, adding features and capabilities that enhance the design process.
MockOla is a free 2D drawing tool that allows users to easily build UI wireframes, free-form designs, and UML diagrams with a simple drag-and-drop editor. MockOla is available online, is free to use, and allows users to easily create custom designs and mockups.
This new version of MockOla includes a new dashboard with an enhanced look and feel, the addition of new palettes and elements, a function to upload and add photos into designs, and the ability to use the tool without creating an account or logging in.
So you want to host a web application on Azure with minimal overhead, but how is this done? Azure makes it possible by running an App Service using Docker containers. Setting up an App Service is simple and can be accomplished with a few steps.
In this blog, I’ll explain the steps necessary to generate a Docker image in Azure. Then, we will deploy a web application based on an image we generate. We host the application with the following steps:
1. Create a Container Registry
2. Build a Docker image
3. Create a Web App
With the recent news, many companies currently find themselves in the real situation of a sudden transition to a remote staff for the first time. With the snap of a finger, your team members suddenly lack the proximity to be able to function in the same exact way. Yet, work must be done and deadlines still need to be met.
In this blog, we introduce tips, suggestions, and takeaways for Agile software development team members to successfully work remotely or distributed for the first time.