As each of our clients weathers unique challenges, “digital transformation” comes to mind as something that exists in different stages. Some organizations are long-since transformed by technology, while others shifted more recently toward work dominated by the distributed as well as the digital.
In building custom applications to automate workflows, streamline operations and leverage technical advantages through innovation, we harness the power of digital transformation. We’re helping many organizations maintain existing momentum to position themselves for positive upswings, and others to recover from economic downturns, overcome turbulence in operations, or head off uncertainty about technical resources.
Digital transformation supports organizational transformation. And it can also lead this transition.
Have you ever opened an existing solution, took one look at the source code – and your eyes just glazed over – as if you were attempting to decipher the Matrix?
You’ve entered the world of DX, or “Developer Experience”.
Just as User Experience (UX) refers to the experience of users, Developer Experience (DX) focuses on the experience that Developers have within the code of your system. This applies whether that’s code you inherited, code you passed on to someone, or code you originally wrote — all situations which affect a person I would call ‘Developer Next’. This could certainly be your-good-self, in six months time.
Jinal Shah is a UX Designer at Beezwax. She shared the process for creating Google Display ads, using a system to optimize collaboration between Design and Marketing teams.
Our design team wanted to implement a design system that could quickly generate different variations of Google Display ads in multiple sizes. This system had to balance creative freedom and brand adherence. We wanted a user to be able to change content, colors, backgrounds, buttons and other visual elements without further involvement from a designer. However, it was important to create a controlled environment so the ads would stay on brand and follow a conceptual and visual pattern.
FileMaker 19 introduced support for Dark Mode. Not only does the application’s chrome support Dark Mode (like many applications), but developers now have the ability to detect the OS Dark Mode setting.
Let’s look at three easy techniques to give FileMaker Pro users a choice between Dark Mode and Light Mode, plus an option to automatically adapt modes based on OS settings.
Greetings from the Mandalay Bay Convention Center!
It’s Day 1 of the Tableau Conference 2019, and there is so much to see and do here! Prior to tonight’s kickoff, one of the exhibits that I was keen to visit is a Viz Gallery set up on the second floor. Studying each piece, I found myself struck with inspiration with regards to how I feel about data. Continue reading “The Impact of Data Viz | Tableau Conference 2019 Day 1”→
Way back when FileMaker 14 was released, as developers we were treated to the new-and-improved script workspace, adding all kinds of features from line breaks to auto-complete/type-ahead coding. To any of us who spend most of our day working in FileMaker, the response was sheer joy.
For all of its speed, flexibility, and ease-of-use, sometimes our favorite platform is missing some of those “standard”, quality-of-life features you would expect. For a long time, Layout mode has been lacking a few key features you would normally expect to see in a modern design application. With FileMaker 17, we get much closer to bridging that gap, receiving a whole bunch of handy, time-saving features along the way. Let’s dive in and take a look. Continue reading “Lost in Layout Space: Getting to Know FileMaker 17’s Layout Mode”→
We’re thrilled to announce the official, “integration-ready” version of LOgiCATOR. LOgiCATOR is a modular search interface for FileMaker that can be easily integrated into new or existing solutions. It’s designed to help users locate data with logical precision, via a powerful yet intuitive interface for searching across FileMaker tables. This article includes a download link for the module and demo file, describes what’s changed since the preview version (a lot), and explains how to integrate LOgiCATOR into your FileMaker solutions.
In Part 1 of this series, Introducing LOgiCATOR, I mentioned that LOgiCATOR grew out of a search interface I developed for a project several years ago. In ways we’ll briefly consider here, it wasn’t extensible, but all that has changed. As that early search interface grew into LOgiCATOR, it made a quantum leap in context independence. The reason we were able to accomplish that can be attributed to a powerful synergy of FileMaker card windows, JSON, window improvements, new functions, and the Layout Objects window — in short, FileMaker 16!
We’re excited to announce the release of LOgiCATOR, a new modular search interface for FileMaker. It’s designed as a module you can drop into a FileMaker application and, with minimal configuration, add a rule-based search interface to any number of layouts in that solution. LOgiCATOR is also a springboard for learning about some great new design and integration features of FileMaker 16, like card-style windows and native JSON.
In Part 1 (“Check Please,”) and Part 2 (“Expert Panel,”) of this series, we had some fun doing things with button bars that showed off some of their unique usefulness within the FileMaker design-layer toolbox. Often as not, your button bars are going to include icon labels, with or without a supporting text label, and you want those icons to look great.
FileMaker Pro 14 includes a new feature to add placeholder text to fields on a layout. What is placeholder text? Simply put, it is a way to put text inside a field when it is empty. This feature is useful for mobile, web and desktop users alike.
FileMaker 14 introduces new controls available in the mobile FileMaker Go app that help to bring the media player experience in FM Go more in alignment with iOS. These changes, compatible only with FileMaker Go 14, include 3 new script steps, 3 new script triggers and 1 new calculation function. In addition, the script step Insert Quicktime has been removed (developers should use the Insert Audio/Video script step, which we have had since FileMaker 12).
When you’ve been using FileMaker as long as I have, you know we’ve done all kinds of crazy things to get image masks to work on our buttons. For example, we would use a set of grouped native FileMaker line objects to cover an image just to get an ugly looking mask. I hope that not many developers suffered for too long using that technique.
It’s FileMaker Developer Conference time, with 8 Beez in San Antonio for DevCon. We’re studying new development techniques from FileMaker Inc. and our industry peers, sharing a few methods of our own and even riding a few mechanical bulls at a real live cattle ranch!
As a participant-driven “Unconference”, d3.unconf allowed us to interact with other d3 devotees in sessions that ranged from “New to d3” through “Multivariate Data” and “Visualizing Neural Networks”.