Interview with Attila Schmidt, BitBakery’s Director of UX/UI

“Your skeleton is your skeleton, no amount of makeup is going to change that.”

 

We interviewed our Director of User Experience and Interface (UX/UI), Attila Schmidt, about his work designing for web and mobile applications.

When he’s not designing, Attila spends time with his wife and two daughters. He makes a mean loaf of sourdough bread and DJs at a club on the weekend. He’s also a staunch defender of the Oxford Comma.

 

What are UX and UI?

“User Experience (UX) is about how you interact and flow through an application. It’s mostly independent from the aesthetics of the app. Where the goal is to help users navigate effortlessly. To do that, you need to understand a users’ intuition. UX could be how a user completes a login form or uses a chair.

“User Interface (UI) is the way something looks. The goal is to engage users with your design. Well-made UI has the ability to direct a users eyes to where you want them to go.

“To sum it up, UX is your skeleton, UI is how you look. Your skeleton is your skeleton, no amount of makeup is going to change that.

How do UX and UI overlap?

“They have to be discussed together. Both must be of a certain caliber to have a good experience. If you have a well-made UX with a UI that has tiny buttons for example, the experience will be frustrating. The UX almost doesn’t matter, because the person can barely interact with it. Conversely, if the interface is gorgeous but the UX is bad, the user will get stuck.

How do you first approach new UX and UI projects?

“With any new project, I first try to understand the requirements both for the client and their users. Then, from those requirements, provide a quality user experience. I try to wear our user’s shoes so they can traverse our designs effortlessly.

What is your core philosophy for UX and UI?

“Don’t reinvent the wheel and don’t do things just for the sake of being clever. What is well-established works. For every platform, there are patterns users expect. It makes more sense to use those patterns than something new. New ways of doing things keep people from using their instincts. For example, if you select date fields on Android and iOS, different interfaces will come up which users expect. To give them anything different is to slow them down. Give people what they already know when appropriate.

What common challenges do you run into when designing?

“There are always tensions between business needs and optimal UX. For example, sometimes business demands require users to answer more questions during the sign-up process than what’s standard because more data is needed. Finding a balance between the two is key.

“Another challenge is tackling the unexpected when deep into a project’s implementation phase. I often ask myself, how can I adjust this without upsetting the plan too much? Staying flexible is important.

What’s your take on UX and UI trends?

“They’re hard to predict. There will always be something that somebody comes up with that others start adopting. That’s when it becomes a trend. For UX, fly-out menus were once new. Now they’re common. In UI, everybody started adopting flat design, now we rarely think about it. When I have a project to complete, I’ll look at alternatives patterns or aesthetics, but I won’t use a trendy new pattern unless it solves a problem which isn’t solved better another way.

How do you approach design for web and mobile?

“For mobile design, you know how people will view it; through a small screen and probably slightly distracted. When native, I’ll often create comps, describe them and offer instructions for recreating them. This usually requires pixel peeping once implemented.

“On the web, there are many browsers and platforms so it’s harder to ensure a common experience for all. I create the front end patterns. That means developers can hook into them without recreating my designs.

Can you discuss designing for accessibility?

“BitBakery complies with accessibility standards, as outlined by the internationally-adopted WCAG 2.1. That means we describe images, use big and appealing fonts, provide lots of contrast, icons and other features for the visually impaired. Alerts, hints and errors are read aloud for the hearing impaired, as are forms with cursors hovering over them.

“When designing for iOS, we follow Apple’s Human Interface and Accessibility Programming Guidelines. For Android, we follow Android Design Guidelines. These are rules developers must follow when building for iOS and Android. We also take material design principles into consideration to improve the user’s experience.

What do awesome UX and UI look like?

“UX and UI work best when the design is seamless and mostly unnoticed. The best experiences happen when users don’t even know they’re being guided. Context matters too. You have to think about where and how a user is using your app.

Bring! is awesome. It’s interface is simple and tile-based. It considers the context of being in a grocery store. Tiles have two different colours for what you do and don’t need. They’re organized by what you’re likely to see as you walk through the store, starting with produce. It can also link accounts. So, when my wife and I split up shopping our unified list is immediately updated.

UI, UX, User Experience and Interface, Bring! app, mobile, phone
UI layout of Bring!

“Other grocery apps I’ve used had long, unordered lists which require two hands. This has big buttons and needs only a thumb. When you pocket your phone, it won’t lock (because it’s annoying to unlock ten times). That UX design transcends just the screen. It’s an example of putting a thoughtful spin on something common.”

The Takeaway

UX and UI are probably what you love about your favourite apps. They’re responsible for your experience when using them. The best apps have great UX and UI, and support your intuition.

 

Thanks for reading! Check us out on Twitter, LinkedIn or our website.

 

By Jack Mitchell and Wes Worsfold

By Jack Mitchell


Jack Mitchell
Jack is a Laurier Business student and is passionate about all things tech


 

Interview with Ryan Sweny, BitBakery’s Director of App Development

Serverless technology

We interviewed BitBakery’s Director of Application Development Ryan Sweny about his interest in serverless technology.

Ryan develops using many tools including Android, Node Express, MongoDB, Angular, Ionic, Go, and Amazon’s AWS (EC2, S3, Lambda, DynamoDB, Route 53, RDS).

1. What is serverless technology?

Serverless technology is a cloud service whereby you don’t need to have your own server.

You only need to write core logic for your server as a bunch of stateless API (application program interface) calls. The provider takes care of hosting for you, including scaling and security issues. This encourages a strict, stateless design philosophy as the server can’t manage tons of information.

This makes things simpler, except at the design and architecture stage. That’s when it becomes more interesting to design. Organizing a serverless database schema requires care because it’s more limited than standard databases.”

2. What excites you about these serverless technologies?

“Serverless makes server maintenance easier. It lessens the amount of stuff that can go wrong, and makes developing easier. People hate worrying about their servers during downtime.

3. How are these technologies influencing the world?

“A lot of companies are integrating serverless technology. It’s easier than ever to build the backend for your new app or game. This helps startups get their products out. A back-end that scales automatically means there probably won’t be a crash right after launch. User experience is improving, too.

Dedicated servers like Amazon’s or Google’s will probably mean fewer credit card hacks. I say ‘probably’ because there is risk of (unlikely) bug exploitation.

4. What are the implications of serverless technology?

“Developers won’t have to do so much back-end plumbing, scaling and security, because serverless takes care of it. More time can be spent on what matters, like UI, design and graphics.

5. Can you expand on how serverless technology helps with scaling?

“Say you write your code in a small, stateless manner. It’s Amazon’s job to deploy that to as many servers as necessary. They do have some limits, but they’re very high. Whether your app does one request per second or 500 makes no difference.

It’s also much cheaper for the developers. You pay a fixed cost to run your own server, which can be $80-100/month. Many startups spend money on inactive servers because an app or product doesn’t need much attention. With Amazon’s Lambda, the bill may only be 10 cents. 

6. How would you start learning about serverless technology?

Projects have different requirements, and you should know all your options. Sometimes going serverless will be best. It’s a quick way to get moving and prototype a system.

To get started with serverless, start with your favourite provider, like Google’s CloudAmazon’s Lambda or Microsoft’s Azure. Learn from their start pages. Some link to DIY features which let you get a feel for the tech.

The Takeaway

Serverless technologies allow for more rapid and secure application development and deployment. 


The Recap – About Ryan

Family: Husband and father of an active 9 year-old diver

Experience: UW Computer Science & Math major who’s been developing since ‘95

Business hero he’d like to have lunch with: Elon Musk

Things most people don’t know:

Ryan was sad to retire his “clicky” PS2 keyboard from 1996

He gets along with MACs and PCs

 

Thanks for reading! Check us out on TwitterLinkedIn or our website.

By Jack Mitchell


Jack Mitchell
Jack is a Laurier Business student and is passionate about all things tech