Learning Claris FileMaker

How I became a FileMaker developer

The vast majority of FileMaker Developers are not computer science graduates.

They are folk like you and me who had a data driven problem to solve in their own business and who were attracted by the ease with which you can get started building data powered Apps in FileMaker and ended up becoming a full-time Filemaker Developer.

This is because FileMaker, at its core, is an empowering technology, that enables ordinary people to achieve amazing things.

I have many images scattered over many devices, storage systems and photo handling Apps.

I also get pretty fed up when the one I relied upon stopped being supported i.e. iPhoto then Aperture.

I suspect that I am not alone?

How could I consolidate a single good copy of each of my images into a system which would not be deprecated in several years time, which I could use long term, so all those great images don’t disappear?

Digital images, despite their apparent permanence are potentially much more transient than paper images because they can become lost or inaccessible so easily in the future.

Having recently noticed several proprietory devices offering this sort of service suggest that this is a common problem.

As a Claris FileMaker Developer specialising in performance, I wondered whether I could do this in FileMaker, or could I find a better solution?

How efficiently would FileMaker handle large numbers of images?

...

Getting started building FileMaker Apps for WAN performance.
The universal rule is that users will not use software which they perceive to be too slow.

If they don’t use it they never see all the cool features you have developed.

Thus achieving at least adequate WAN performance is crucial.

This can be defined as the user generally not needing to wait for more than six seconds for the App to startup and no more than a second for their screen to update during normal navigation.

Read more on Medium ...