TECHNOLOGY RADAR

We try to stick to a single language. We use Typescript for everything. We know many more, but regardless we’ll do everything with Typescript where it is good enough.

For Web and Mobile. We continue to assess other options as serious ones pop up, but nothing much better, and its ecosystem has ever shown up.

Not much to say. We’re a JS shop and except Deno there aren’t any serious options.

We use this for websites. It has the needed features like SSR, SSG, ISG, and a routing architecture which is a perfect fit for websites. No need to poke around with the build.

Fullstack JS framework. Built on top of React/NextJS/Prisma/Postgres. We use it as our “Ruby on Rails” for Web Applications. It’s mostly an opinionated collection of libraries on top of NextJS and incredibly productive.

An ORM with excellent developer experience. It doesn’t abstract too much and produces efficient queries. Provides strict typing for all DB access and solid DB migrations. We use it to access Postgres.

Databases come and go, except Postgres, it always stays because it is solid and extensible for most use cases.

Great for Caching and Queueing. Sometimes as a message bus.

It’s easy to pick up. It has very little abstraction. It produces CSS as external style sheets which are important for Website projects.

Similar to Heroku, but it’s moderately priced and will do the boring OPS work for us that repeats itself in every project. Let’s us create scaleable web apps with postgres + redis with prodution and staging environments and automatic deployments, distributed logging an in less than half a day.

Serverless deployment platform. Great for websites when paired with NextJS. Global CDN. Automated website performance monitoring built in.

UX/Design tool of choice. Good for communicating ideas.

When Mobile, then React Native

Headless CMS with a Visual Editor. It’s extensible enough for most our use cases in websites and has among the best user experiences for content editors.

Pairing Sanity with Shopify projects is a great choice because of their excellent integration.

Modern, react-oriented, and battle-tested in our production-grade projects animation framework. Creating a bit more complicated animations with this tool feels like a breeze ;-)

The way we structure our commit messages (https://conventionalcommits.org/).

Released by Shopify enables you to build a custom, headless, and optimized-for-performance e-commerce experience. Greatly aligns with our company tech stack.

We’re trialing this. Remix architecture is brilliant in its simplicity due to it leveraging common web standards. We use it in our Shopify projects for admin apps and it's been working great. However, Next.js is still our preferred option. If BlitzJS adds support for Remix then we’ll likely take the plunge.

We usually don’t have a need to muck about with build tools since we always base our projects on frameworks that make the build tool choice for us, but Vite is on the radar when it’s not an option.

We’d like to get deeper into web based 3d, specifically with React.

New kid on the block. All-in-one Javascript runtime. It’s still in the early days but with great promise.

Fastest way to deploy Hydrogen storefronts.

T3 getting a lot of attention and traction lately. We feel this might be the framework which potentially can replace Blitzjs, which currently feels a little bit stagnant at the moment.

After recent changes in Render pricing, we believe there are more affordable solutions available. We have heard great things about the Digital Ocean App Platform and are excited to give it a try!

We find Astro to be superior in certain use-cases, particularly when content is crucial and optimal performance is needed to satisfy SEO gods.

We're putting Chakra UI on a little break for our Web Apps. It's been great, but there are some cool new ways to style apps popping up. Time to see what's out there and keep things fresh!

Keeping our eye on this if we’d get a specific use case, but its ecosystem is too minimal, nor does its advantages bring enough value considering its disadvantages in comparison to React.

We’ve trialed VueJS and deduced there is no reason to use it over React. For our engineers and projects, it’s worse in all regards.

We’ve had to use Angular due to customer requirements. We no longer accept any projects from customers who require Angular.

We’ve trialed this when the use case seemed to be a fit. We find it has too many rough edges and it diverges too much from our core JS foundation.

We consider GatsbyJS a great framework, but that other frameworks have driven past it, leaving it obsolete.

We rarely need pure backend frameworks. If we did, we’d explore other options before trialing NestJS again. E.g. Moleculer, AdonisJS, or just plain express.