Web application users are accustomed to canceling a popup (aka dialog or modal) by pressing the escape key, and many modals can even cancel if the user clicks outside it. How does a React developer code that without a plumbing mess between the modal and every visible component beneath it? How do you cancel a React modal with an escape key or external click?
I’m glad you asked because I have an answer. In this blog, I’ll show a pair of easy-to-use custom React hooks that simplify the task.
Flutter has a lot of amazing plugins that make it easy to develop cross-platform apps. Recently, I had the opportunity to work with a theater chain that made use of a map view to show nearby theaters. We used Flutter in conjunction with Google Maps.
In this blog post, we will take a look at the Google Maps Flutter plugin, which allows you to add an interactive map to your iOS or Android app and customize it in many different ways!
So far in this multi-part series, we’ve used Svelte to make the frontend of a Word Puzzle Game, but it does not receive user input, yet. That doesn’t make for a very fun game!
In Part 2 of this series, we’re going to make our game a little more functional. We’ll accomplish the following tasks: (1) allow users to guess a word, (2) manage state for the guesses, and (3) track the correctness of each letter in each guess.
By the end of this post, we will be one step closer to having a Svelte-based, fully functional Word Puzzle Game! Without further ado, let’s get started.
Developing custom applications is one of the hardest professional endeavors, and making them secure is even harder. Malicious actors are constantly changing tactics and strategies, which, unfortunately, makes it impossible to completely eliminate any security threat.
There needs to be a balance between delivering features quickly to meet business objectives and mitigating security risks. Thankfully, these two goals are not mutually exclusive. This blog post dives into the top mistakes that can be made while developing custom applications.
These recommendations are different from what would commonly be seen in an OWASP list, and they should be used in addition to whatever security practices and procedures are already in place by an organization’s infosec department. These recommendations are also written from an application architect’s (rather than an enterprise infrastructure) perspective, so most of them aren’t covered by existing security checklists.
Often, we are approached by startups and established companies with an idea for a new product. Just as often, there is little to no user base from which to conduct research. In this blog, we’ll look at how to understand the product, its potential users, and how to create the application with minimal user data and investment.