I recently made a content management system. The application, called “Strong Grips” allows the user to record the duration of exercises of their grip strength exercises. Users can make and log into accounts, and all of their exercises belong to their account. I realized the importance of using good security practices no matter the importance of the application. For an application as basic as strong grips, the immediate risks are quite low stakes. If the information about the exercises were stolen or destroyed, that would not be the largest concern. Far more worrying would be the possibility that the usernames and passwords could have been stolen. Many people reuse the same username and password on multiple sites. So a failure on my end even for an application not pertaining to any sensitive data could endanger other accounts with sensitive information.
Beyond security, an application like this needs to be centered around the user. Convenient, functional, and not overwhelming. When designing Strong Grips I wanted the user to be able to do exactly everything they would want to do. That is, no more than they’d need to. Anything can be added to forever and at some point of adding functionality you begin to make the interface less functional. Finding the balance between these too is difficult. As a side note, it occurred to me while building strong grips, that you must prefer the experience of the user over the experience of the developer.
Building Strong Grips was more satisfying than building my previous application. It is a functional application, with an html page that works. Strong grips resembles something that people use on the internet today. I am excited to see what I build next.
Top comments (0)