Figma is the subject of our first friction log of 2021. Cesar, a developer, goes into the designer's world and discusses the UX from a developer's POV.

We have mentioned Figma since the beginning of Friction Log as the tool that we used to create assets for the webpage, interestingly enough I haven't used Figma before and decided to try it out.

This post has a smattering of random tools that I didn’t think was appropriate for a full friction log (at least not yet). This is more of a “first-time” impressions post.

Matt, Cesar, and Rick have a fireside chat about a hackathon entry, going over the tech details, the stack, and general hackathon thoughts.

Nova is the new code editor from Panic, the makers of software such as Coda and Transmit. Cesar dives in for a first-time experience using the editor. Find out how it went!

Nova is the latest app made by Panic and is a great native Mac app. I had a fairly great experience while trying it out but not without some of the frictions as every new app would have.

How does the Aesthetic Usability Effect play in to Github Codespaces or PlayJS? That and a few more topics in this week’s episode.

All of us technical people make strange associations and this is precisely what this article is about.

AWS Amplify’s value proposition is very attractive. In this episode, we talk about that promise and our first-time experience using it while also delving into the Zeigarnik effect and its contribution to this experience.

I don't recall how I came upon this app but it seemed really compelling. I decided to try it on a trip recently. It's a fun app with some promise but a lot of friction.

Github Codespaces (i.e. VSCode inside Github) is promising. It's remarkable just how portable they've made VSCode. This is a light, quick friction log on a first-time experience setting up Codespaces. More logs will surely come :-)

GraphCMS is a hot topic in the headless-CMS space. This log is a first-time experience study on this CMS. We also touch on the Peak-End Rule of UX.

In this episode, we have two brand new types of friction logs: "end-user" and "feature experience logs. We talk about the Principle of Least Astonishment (POLA) principle.

A fun side conversation on Epic's attack against the Apple App Store rules. In this episode, we share our experiences as mobile developers in an Apple world, ponder what Epic is thinking, and ask the question: "Should we do a friction log on this?".

Friction logs are also great for analyzing end-user platforms. In this log, Rick and Cesar have a fun conversation around Hey.com and it's usefulness.

It's time to update our website that leverages NextJS to the latest release. In this feature experience, I embark on the quick journey of implementing the incremental static regeneration.

We are back with another piece of the stack that powers the Friction Log website: NextJS. In this episode, Cesar interviews Rick’s Log, and they also discuss the speed of applications using the Doherty Threshold as a baseline.

In this episode, Rick interviews Cesar on his first time experience with Vercel (formerly known as Zeit). We also talk about the Visibility of System Status heuristic and why that's so important for a SaaS like Vercel.

In this episode, Cesar interviews Rick about his first-time experience using TailwindCSS. Also in this episode: Hick's Law and how it can be applied.

Welcome to the first episode of the Friction Log podcast! In this episode, we talk about what the Friction Log is all about and cover a brief introduction of Rick and Cesar. We hope you like it.

With the popularity of the JAM Stack, platforms like Vercel and Netlify have become the go-to way to deploy websites. My first experience had to be to deploy FrictionLog's website in Vercel.

I'm trying something different. Yes, it looks like a blog and tech content, but with a slightly different angle: DX (Dev experience) and UX emphasis.

I’ve tried a lot of CMS’s over the years but I specifically wanted to try out using GraphCMS as Friction Log’s headless CMS and I wasn’t disappointed.

I was able to easily spin up a sample project, with a DynamoDB and GraphQL backend, play around with it, make changes, with very little friction. If I would’ve stopped at the introductory tutorial, I think my review would be a little different.

The conventions and philosophy of Tailwind make quick work of converting a design to HTML/CSS.

I’ve always wanted to build something on NextJS. Building out the Friction Log website was the perfect opportunity to do so.