ISO FileMaker Magazine

One of the nicest feelings in the world is getting something for free. Especially when it really helps you out and it's valuable.

At the small cost of giving up a little bit of data, to one of the world's biggest data collectors, you can see how users use your FileMaker solution and what they do.

In fact, what you collect, and how, is totally up to you. You can control pretty much anything in terms of what you transfer to Google Analytics.

Many developers who have implemented Google's Analytics only go a short distance to what they could potentially collect. They often point to some remote site with embedded analytics code provided as the default by Google.

However, the usage of the default code is SO LIMITING. You can get as creative as you want when pushing data to Google Analytics. The big trick is to know what can be sent, how it's sent and what to do when Google has the data.

The reporting aspect, on Google's side, is where most of the power lies. What you need to do is determine what you want to push and when. Fortunately, this video has all the nitty gritty details for making things super easy for you!

There was a day, when either computers were simply too slow or people just weren't used to the idea of seeing themselves on the computer screen. Probably the later. The screen was for showing data, not for personal flattery.

However, the web and social media exploded and having some sort of user image, or avatar, is quite the norm these days.

Using a mobile device like an iPhone or iPad and taking advantage of FileMaker Go allows for all kinds of opportunity when it comes to capturing user images. The embedded cameras are great and take pictures which are just fine.

So fine, in fact that it may be too much information for simple use to display on the screen. There are also considerations related to the Retina display and how much more of an image you need than the actual size - it's double actually.

In this video, I provide the perfect mix of tools and information in order to really take advantage of mobile device cameras and the ability to present a picture perfect image - of whatever the user wants to use as their avatar within your FileMaker solution. Need some fancy graphics wrapped around? No problem. Just watch this video and use the code to integrate into your own FileMaker solution quite easily!

Having personally developed with both languages and frameworks which implement strong sets of standards, I quickly found that having some form of standards imposed, allowed me to focus more on the solution once the conventions were learned. I wasn't doing the same type of thing in two different ways due to the current "known" way.

Notice, I didn't say the "right" way. There's often more than one way to accomplish something. It's like driving a car however. No matter which one I hop into, they all have many of the same parts in the same place. Steering wheel, brakes, accelerator, etc.

Sure, nuances like the radio and air conditioning may be different, but they don't move the steering wheel around on you.

This makes it easy to adapt when moving from one car to the next. It provides a basis from which I can start to learn what I may not know about.

In 2010, I started documenting some of my own personal standards for FileMaker specific development - and invited others to join in. In this video, I discuss some of those standards and the why and how they work.

Over the few years since starting the web site, the number of people using them has increased. This has allowed the standards to grow based on the feedback and input from others. This video provides a variety of topics related to standards which may help you evolve your own or take advantage of, and leverage, those which have already been started.

When it comes to using Custom Menus within FileMaker Pro, I often get the impression that many developers consider this a "nice to have" feature - not the "go to" feature it could potentially be for any solution. You'll often here developers talk about teaching users "How to use FileMaker".

What this means is that not too many developers are taking advantage of Custom Menus.

Here's the trick. Put them in from the start.

Their lack of general use may be attributed to the process of creating them - it isn't quite user friendly. You have to be willing to dive into the dialogs in order to implement. Yet, FileMaker 12 made Custom Menus even more powerful - another good reason to use them.

The good thing about Custom Menus is that once you start the process it's any easy thing to keep adding to.

So, the goal is to start simply and implement menus as you develop your solution. If you take this approach, then the "hassle" of adding them after the fact isn't really a hassle at all.