I’ve mentioned before that we’ve used FPro as a type of Rapid Application Development Platform. Building a fully functioning prototype using this high-level (largely graphical) database application has allowed us, as non-coders (albeit with a decent understanding of how a properly architected database should be structured), to develop our therapy-smarter tool in an iterative way, without spending large amounts of money.
Another benefit is that the product we are using remains fully accessible to us at the architecture and data level, and is largely self-documenting. FilemakerPro produces human-readable graphical representations of its database structure as a standard report and the functional scripts are basic-like in their use of real language, and thus easy to follow.
What this means is that, for a team like ours, without coders, the scary step of commissioning native code from people whose work we will ultimately not be able to judge in detail is made much less risky. When we judge that the time is right to take the system to the next level – when we need it to go faster and handle more clients, we will have to get the thing recoded – and this will mean bringing developers in.
For startup teams without coders, this is a terrifying point. How do you find the right person? How do you choose which framework, which language, which platform, which architecture? How can you even begin to judge the recommendations you are hearing? How can you describe the features you want?
Continue reading “Using FilemakerPro as a RAD platform just got more interesting”