Katrin

[Katrin @nrksochi]

Scrolling Pinterest for the hundred-thousandth time, I caught myself thinking that AI design, for all its flaws, did one useful thing. It finally killed clean style and that damn minimalism. After all these years, I was sick of it. It proves once again that everything moves in cycles. After the era of South Korean templates and Flash came the sleek Apple style. Now it's bright colors, animation and video all over again. Welcome to the era of visual anarchy. 😁

[Katrin @nrksochi]

Hello )

[Katrin @nrksochi]

Clean revamp - the hero headline is clear and the workflow card on the right explains what you do faster than the copy does. One small thing: I count three "Book a call" buttons above the fold (nav, hero and the floating one), which starts to feel a bit pushy. I'd keep the hero CTA and show the floating button only after the user scrolls past the hero.

[Katrin @nrksochi]

Testing against real Stripe test clocks instead of your own expected values is the right call - proration and credit balance edge cases are exactly where homegrown billing logic drifts. Making the TestSprite checks required for admins too is a nice detail most teams skip. Curious how you handle mid-cycle tax rate changes in the timelines.

[Katrin @nrksochi]

One promise plus one URL field is the right call, and showing a real scrollable report right under it does more than any testimonial wall. One note from the video: the small grey body copy on the dark sections is hard to read, so I'd bump contrast and size there. Also worth adding a sample URL people can try in one click if they're not ready to paste their own.

[Katrin @nrksochi]

The particle black hole is a great hook - a backend engineer shipping a WebGL hero is a story in itself. One thing I'd check: on low-end phones and with prefers-reduced-motion it should fall back to a static frame, so the canvas doesn't block first paint. And let the systems work show up within one scroll - that's what a hiring manager came for.

[Katrin @nrksochi]

Making featured brands the landing page makes sense - people come to an inspiration site to see work first, and the dark frame lets the store screenshots carry all the color. Loading placeholders are a good call too. One idea: use a blurred low-res preview or the dominant color of each screenshot instead of flat grey, so the grid feels alive even on slower connections.

[Katrin @nrksochi]

The serif headline over the mountain shot gives this a calm, almost editorial feel, which suits a sponsorship platform. The search bar with campaign, category and sort filters is nicely compact too. One small thought: with 11 categories in one list, grouping them or adding small icons could make scanning faster. Looking forward to your Framer MCP notes on Monday.

[Katrin @nrksochi]

15 minutes from sketch to a responsive page with reusable components is impressive, and the OmniLab layout already reads clean - strong hero image, one clear CTA, tidy footer. If you go for the Marketplace, I'd spend the extra time on what MCP won't do for you: tablet and mobile breakpoints, real content edge cases and clear component naming so buyers can customize easily. That polish is what sells templates.

[Katrin @nrksochi]

Love the receipt as a project index - a list of projects, types and years fits that format naturally, and the hand-drawn circle on the active row is a lovely detail. The dithered photo with the caption card feels like part of the same visual family. Curious how it behaves on mobile, since the mono type inside the receipt is already quite small.

[Katrin @nrksochi]

The humor does the heavy lifting here - the "Who it's for" list with Mom, Group chat and Landlord plus their unread counts sells the concept faster than any feature grid could. The dissolving pixel GHOST wordmark is a great closer too. One small note: the nav and hero microcopy read quite tiny at this size, a bit more size or contrast would help on laptop screens.

[Katrin @nrksochi]

Clean launch. "Your files, in the notch" explains the product in five words, and showing the real panel with Downloads, Drops and Screenshots folders makes the idea click instantly. One small thing: the feature list under the button is quite small and low contrast on the dark background - a bit more size or brightness would help people skim it before downloading.

[Katrin @nrksochi]

Really cohesive onboarding - one strong visual per intro screen keeps each value prop easy to scan, and the one-question-per-step flow with a progress bar feels light. Small thought: the selected states in the goals list look quite subtle on the dark background, a brighter fill or accent border would make the choices pop at a glance.

[Katrin @nrksochi]

Turning the split into a branching curve is a smart way to explain the product - invoice to payment to split reads left to right without any copy. Nice that the end points actually sit at their real proportions, a lot of marketing charts skip that. One small thing: the gray descriptions under Get paid / Auto-split / Relax look quite light on that beige, a touch more contrast would help on mobile.

[Katrin @nrksochi]

Congrats on the first 100 - the dark profile-style layout with the starry banner feels personal. One small thing on desktop: the floating bottom nav sits right on top of the intro paragraph on first load and hides part of it. A bit of bottom padding or a fade behind the dock would fix that, and moving one featured project above the fold would help new visitors reach your Proof of Work faster.

[Katrin @nrksochi]

Clean direction - the teal with the yellow accent on "Stay connected" gives the headline a clear focal point. One thing I would test: the five feature rows have borders and read as tappable, while the real actions are Skip and Next at the bottom. Dropping the outlines or making Next a full-width button would make the flow more obvious, and the grey subtitles could use a little more contrast.

[Katrin @nrksochi]

Clean direction - the lime on near-black gives Rushmo a strong identity and the single CTA keeps the first screen focused. One small thing: the grey 'Absente' state almost disappears on the dark background, so it is worth bumping its contrast and maybe adding a pattern or icon per state for colour-blind players. A placeholder in the pseudo field would also make the first step more obvious.

[Katrin @nrksochi]

Curious how it behaves on existing projects. The real test for me is whether AI edits respect the components, variants and breakpoints you've already set up, or start adding one-off layers. If it keeps the structure clean, this could save a lot of time on routine content updates for clients.

[Katrin @nrksochi]

A, but I'd confirm it with data first. If people scroll past the hero and leave, the headline isn't saying clearly what they get and who it's for. If they click the CTA and drop on the form, it's the signup flow. A simple funnel from visit to CTA click to signup plus a few session recordings usually shows which one within a day.

[Katrin @nrksochi]

This is a great example of designing for the moment of highest risk. A key shown once is exactly when people paste it into a notes app or a Slack DM, so making the safe path the shortest path changes behavior more than any warning text. Would love to see the same on webhook secrets and OAuth client secrets, those get mishandled even more often.