Starter files give an instant boost to your development. Our starter files provide the basis for your development. Yet, there are different starter files. How they might differ is described in this post.
What is a starter file?
Use a starter file to begin your next FileMaker project. It is a shortcut to your solution, as it begins with a set of functions for your ultimate goal. You do not need to start with an empty file, but can start with a proven set of functions, thus skipping probably months of development time. A starter file gives you the expertise of someone else, to start your next FileMaker project with ease.
Which approach do you prefer?
A starter file is not magic. It is solid work, put together for developers like you. Yet, what a starter file actually is, highly depends on how you look at it. We noticed there are two sorts of starter files, which differ in approach:
- More is more
- Less is more
The first option seems a quick fix to your software needs, as it provides a seemingly complete solution. But, apart from the attractive approach to put in as many functions as possible, it is quite possible that your business needs differentiation in areas the “More is more” solution is not fitted for. That usually requires significant effort. The second option does not start with a final result, but rather with a starting ground for you to work with. This also requires significant effort to arrive at a usable solution. However, you can build up, and don’t have to break down. If you need to make substantial effort anyway, the second option might be more efficient, as you can exactly build what you need.
Because of these differences in approach, it is important to look at more details, before you decide what is “cheaper” or “quicker”.
Type 1: More is more
Ready-to-go starter solutions
These solutions follow the concept: The more functions, the merrier. These are not starting points, but present themselves as close to an outcome as possible. That might suggest it is a quick solution, which, of course, sounds attractive. But this only works, if you need not change any important parts, which is highly unlikely for most businesses.
PRO: If you need no change of functionality, it can be a fantastic fit.
CON: If you need a change, this is where it quickly turns into a lot of work. Think of removing unneeded elements, replacing or adding new elements, or reconsidering already implemented workflows.
Type 2: Less is more
Basic functionality and high configurability
These solutions follow the concept: Create a sound basis for development, not an end point. Less is more because: Who knows the end goal, if not only the client? It is impossible to create functionality for something you do not know. This concept leads to more basic functionality, intended to help you build your solution from the ground up. To not offer everything is a bold and useful concept if you look to make amendments, changes anyway. It is a cleaner start
PRO: Efficient tools, structures and modules you need for almost any FileMaker project.
CON: No suggestion of “having it all” instantly shows that work is inevitable.
Questions to ask
Let’s say you work internationally, then you might need multilingual features, multiple currencies and the like. To retroactively build that into a single-language and single-currency solution requires not only skill, but also a crazy amount of work. The more functionality you have, the more work it takes to implement those features. Thus, it is important to choose your starter file wisely, considering future developments.
To decide which starter file serves your purpose best, try to figure out:
- What skills you have
- What skills you miss
- What you want to achieve
- Which workflows need to be implemented.
Ask more questions to enable better answers.
Concepts of our starter files
We create starter files, not “do-it-all”-solutions. Intentional limitations are what improves the basis. The more you define as a final result, the more limited it is. Let’s assume you make a small tool to scan and capture barcodes along a process line, there is no benefit of starting with a business starter file. Yet, you will need generic things like a navigation, probably a project structure and some other functions. We found that less is more, as a simple basis can be used for many purposes.
Some of the concepts we follow rigorously:
- Less is more (if it is done better)
- Separate settings from functionality
- Make settings available in regular layouts
- Create a dashboard for the developer only, to combine all settings of the application
- Think modular and keep it simple
- Provide a clear project structure
- Instead of rules, use structures. This makes you less dependent on a certain developing style.
We developed two starter files with different purposes in view. Let’s compare these two products:
FM Starter
FM Starter is a generic starter file with basic functionality working for you “behind the scenes”. It’s a lightweight solution for almost any project, relieving you from basic requirements.
- Dynamic and global navigation
- Multilingual with automated DeepL-translations
- User account management
- Simple project structure
- Modular approach
- Developer dashboard for easy configuration
- Many more basic modules included
- Great for international projects.
FrankCRM
FrankCRM builds on FM Starter, but was enhanced to give you a solid start with a real application as well. Basic requirements for addresses, contacts, products and sales are included.
- Based on FM Starter
- Modules: Addresses, Contacts, Sales documents, Products
- Extensive VAT-handling
- Multi-currency with automated updating
- Highly configurable, as configuring is simpler than developing
- Perfect for developing international business solutions
The right starter file
Selecting the best starter file for your upcoming project is an important step to succeed. Whichever solution you choose, be prepared to invest substantial effort to create the software you need. Especially if you require a cheap solution, it’s helpful to not only consider the initial cost, but also the costs to make it work the way you want.