Another very common question I get asked or better yet, suggested, is why isn’t Reloading Studio offered online, like a web application? There are reasons!
A web application of Reloading Studio has actually been the first prototype! I decided against it. Which is counter initiative in our day and age, especially when yours truly actually prefers cloud applications over desktop, but there are reasons.
Data security and privacy
Considering the nature of the application, the data and what could be extrapolated if it was to be hacked… I just didn’t want to expose any of my users to what could essentially equate to a shopping list of goodies for bad guys.
Unlike financial institutions, small companies are not regulated and will not pay tens or hundreds of thousands of dollars to security consultants, in order to make them secure and stay secure. Even if your data is encrypted on a server, it doesn’t actually prevent data theft through hacking, only through physical access to the server.
I am intimately familiar with this field and I know what it takes to properly secure user data – it’s hard, it’s time consuming and expensive. This is not something I was ready to commit to, because it wasn’t what I set out to do.
In fact! I don’t even keep user’s personal data beyond what I absolutely need, which is an email address, country (because I want to know) and the name. That’s it!
While the desktop application runs on your hardware, a web application runs on hardware rented by me (cloud servers if you will).
Reloading Studio manages your backups and you can use cloud sync accounts that you own, like OneDrive and Dropbox to remotely and safely store these files. A web application would need to manage it for all users. This translates to ongoing running cost of compute (actual processing power) and storage (disk space), which would be passed on to the user as a subscription fee. This is not something I wanted to do, because I aim to deliver the best reloading management software at an affordable price.
Your data is yours! I have no access to it. On occasion, I may request a database file for troubleshooting or testing, but it’s a request and nothing more. You control and own your data. With a web application, the application owner (really) owns and controls your data.
Consider users who live rurally, have bad internet connection or the internet connection simply dies. At this stage, you not only prevented from accessing your data, but you are not able to query the data for reloading tasks. I think that’s a big impact.