So you are a scientist or engineer who has some good science that you would like to share with others. You can publish papers and formulae, but most of us aren't good at looking at formulae and understanding what is going on. We are even worse in getting round to putting those formulae into Excel or software so we can explore the ideas ourselves. So a lot of great science and engineering is wasted because potential users cannot use it. This is a big problem!
There are two problems in creating a technical app.
- Writing the scientific code
- Creating the app infrastructure to run on all devices
The truly hard bit is providing the app infrastructure. It used to be hard enough when you were targeting large laptop screens on a single browser, but it's even harder when the app has to work on iOS, Android, PC, Mac, Chrome, Firefox, Edge, Safari... It has taken me 5 years to get my own coding structure and I've been through 4 iterations. The most recent iteration required the skills of a young, web-native coder who transformed my messy and inelegant infrastructure into something lean, simple and clear. Anyone can make something complicated, it takes a genius (Sean Cooper) to make something simple.
Your personal App-Writer
A key point here is that I use this tool for all my own apps. I simply don't have time to remember how to create a fresh app, how to place graphs in the right place, how to format four columns of sliders and how to read the input from a combobox. I just use my own tool to get the hard work done, then I can focus on the scientific coding.
Yes, I'm being a bit too simplistic. The first app or two will be challenging. But I've provided lots of extras and prototypes in the basic app so that you can focus on getting your scientific code correct rather than having to remember how to plot a graph or work out how to know if a checkbox is selected. It tends to be the little things that soak up programming time and because I've taken care of those, you have more time for your own code.