Design Isn’t a Side Quest

We Care About Design, Not Just Functionality

It’s easy to ship features and call it a day. A form here, a table there, a “good enough” UI. For Kernex we decided early that design isn’t a side quest. Every page—About, Pricing, Helproom, the grading dashboard, the sandbox—has to feel like part of the same product. That means consistent typography, intentional spacing, and layouts that don’t all look like the same two-column card we copied from a template.

Why It Matters for a Learning Platform

Students and instructors already have enough friction: deadlines, confusing rubrics, flaky tools. If our UI adds more—cluttered screens, inconsistent navigation, “where do I click?”—we’re part of the problem. So we invest in readable type, clear hierarchy, and distinct sections so each area of the product has its own identity without feeling like a different app. The About page doesn’t look like the Pricing page; the Helproom hero doesn’t look like the sandbox. But they all feel like Kernex.

From Hero to Footer

We think in flows, not just screens. That includes everything from the first thing someone sees (hero copy, one clear question or value prop) to how we use space so sections breathe and don’t cram. We also care about microcopy and CTAs: buttons that say what they do (“Instructors, talk to us.” / “Students — share your input.”) and links that go to the right place (contact page, not a hash). Small details add up. We’d rather ship one page that feels considered than five that feel generic.

Design isn’t about making things pretty. It’s about making the product clear, consistent, and trustworthy so that when someone uses Kernex, they feel like they’re in the hands of a team that cares.