Learning Claris FileMaker
317.3K views | +6 today
Follow
Learning Claris FileMaker
Give life to your data with an easy to use database ... I'll share cool FileMaker stuff for you, avoiding the programming part of it as much as I can.                        #WorkplaceInnovationPlatform #Claris
Your new post is loading...
Your new post is loading...
Scooped by Didier Daglinckx
Scoop.it!

An Often-Overlooked Pillar Of Software Design: User Experience | Portage Bay Solutions

An Often-Overlooked Pillar Of Software Design: User Experience | Portage Bay Solutions | Learning Claris FileMaker | Scoop.it

Before understanding the importance of user experience (UX) and user interface (UI) in custom software design, we first need to understand that these concepts - often used interchangeably as UI/UX - are two distinct areas. 


It is wise to approach the concepts of UX and UI design independently, though they will both be vital to a successful final product. 


UI refers to the aesthetic elements by which people interact 

While UX is about the user's experience with a product or service 


In some companies, a designer is responsible for wearing both hats, while in others, there are separate designers for each focus. Regardless of the situation, the ultimate goal of the designer or designers is to create functional, user-friendly, and aesthetically pleasing products.


No comment yet.
Scooped by Didier Daglinckx
Scoop.it!

Solving the Right Problems with Good UI/UX - Atlanta FileMaker Developer Group May 2022

FileMaker can basically do anything.

 

Scripts and calculations are just part of the puzzle in any Claris FileMaker solution. Martha Zink from Proof+Geist focuses on the importance of UI/UX, showing different ways that thinking about the user and their experience can be a game changer.

 

It's not just about pretty shapes and colors.

Users have a certain expectation in mind and meeting them is important for the success of your app.


Want to learn more about Proof+Geist? Find them at https://www.proofgeist.com/!

Join our Atlanta FileMaker Developers Group at https://bit.ly/AtlFMDevGrp! Membership is free and open to all!

No comment yet.
Scooped by Didier Daglinckx
Scoop.it!

Design Thinking: Get Started with Prototyping | FileMaker UX

Design Thinking: Get Started with Prototyping | FileMaker UX | Learning Claris FileMaker | Scoop.it

...

 

Many times, we tend to invest in exciting new ideas, brainstorming, and planning for their implementation — until we realise, after launching them, that our brilliant designs had no traction with our users.

In other words, the assumptions we based our solutions on might have been wrong – and when they are wrong, they can lead to significant wastes of time and resources.

Prototyping helps prevent this. Prototyping quickly, and frequently, is the best way to test your assumptions, learn about users, and improve on your ideas.

 

Read more on interaction-design blog ...

No comment yet.
Scooped by Didier Daglinckx
Scoop.it!

Building the User Experience : the Three Ds methodology | FileMakerProGurus

Building the User Experience : the Three Ds methodology | FileMakerProGurus | Learning Claris FileMaker | Scoop.it
Building the User Experience : the Three Ds methodology

The author of this post, Erika Pelser, outlines a three step process that could easily be ported to the FileMaker/Database development world:

There are many possible renditions of the UX (User Experience) creative process, designed to help guide a project from conception to completion, but I use the 3D process.

The phases within this methodology are ‘Discover’, ‘Define’ and ‘Deliver’. 

Each of these phases define the steps needed to implement to a solution to a business or user problem, taking it from concept to production. 

The lines between these are blurred, but it provides enough of a framework so you can bring it to your own work.

 

Read more on FileMakerProgurus blog

No comment yet.
Scooped by Didier Daglinckx
Scoop.it!

Design Think Your Code

Design Think Your Code | Learning Claris FileMaker | Scoop.it

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.


....

No comment yet.
Scooped by Didier Daglinckx
Scoop.it!

Get the Right Answers from Your Users: A Guide to Better UI in FileMaker

Get the Right Answers from Your Users: A Guide to Better UI in FileMaker | Learning Claris FileMaker | Scoop.it

...

The FileMaker platform is one of the best tools out there for improving and extending your business and the way you manage your data and workflow.

So why does the UI matter?

Why does the experience of the user matter?

 

Because we’ve all grumbled at bad design.

Because we’ve all yelled at our screen when a website “doesn’t make sense.”

Because bad UI makes for sad users.

 

As a developer, you have the ability to make users happier people, better workers, and more productive employees.

My slides focused on some key questions to ask your users, so that you can empathize and understand what they’re dealing with.

 

...

No comment yet.
Scooped by Didier Daglinckx
Scoop.it!

Don’t design what users want | InVision Blog - FileMaker tip

Don’t design what users want | InVision Blog - FileMaker tip | Learning Claris FileMaker | Scoop.it

Without getting user feedback, we’d have no idea whether our product is meeting people’s needs. 

We get feedback via email, service request tickets, in-person exercises, phone calls, and through our salespeople and account managers.

All this information allows us to understand the pains and frustrations users experience as they use our product and see problems or trends we might have otherwise missed.

But here’s the thing: you shouldn’t design what users tell you they want.



No comment yet.