Dark or Light Mode? Optimize Video UI for SaaS Tools

Dark or Light Mode? Optimize Video UI for SaaS ToolsDark or Light Mode? Optimize Video UI for SaaS Tools

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Titouan Gillet

• 4h

We're working on a video project for a SaaS tool.

And we're asking ourselves THE question:

Dark mode or light mode?

Normally, we always choose based on the target audience.

But in this case, it's a product used by both developers (dark mode team) and administrators (light mode team).

(If you have a compelling argument, I'm all ears.)

motiondesign saas tech

Kamran Khan

pro

• Apr 10

Venture Out explores the space where colour intensity and contrast collide, creating a dynamic balance between movement and form. It captures a visual harmony shaped by energy, rhythm, and bold expression.

motiongraphics motiondesign motiondesigner Art Direction Creative Direction Motion Design Adobe After Effects Adobe Illustrator

Abdulsalam Yahaya

• Apr 10

This is a Smooth Animation. Love it 😍

Kingsley Ken

pro

• Apr 10

This is the standard. 🫵🏽 Built. Done. Delivered. 🚀 Fitness meets function. 💪🏽 Just delivered this sport training app UI for a client and every screen hits different. Clean. Bold. Built to perform, just like the athletes using it.

UI Design fitness website websitedevelopment Web Design Web Development Figma Figma Make Framer

Sahil Dobariya

pro

• Apr 11

Bold and high-performance.

Révolté

pro

• Apr 10

OFF-TOPIC — A designer's 2 cents. Stay if you want.

RESPONSIBLE RELEASE IS NOT A STRATEGY. IT'S A HEAD START.

Anthropic just announced Project Glasswing (https://www.anthropic.com/glasswing). The premise is simple and uncomfortable: Claude Mythos Preview is so capable at finding and exploiting software vulnerabilities that they won't release it publicly. Instead, they're giving it to AWS, Apple, Google, Microsoft, NVIDIA, and a walled garden of critical infrastructure defenders to patch the world's most important software before attackers get their hands on something similar.

I've done cybersecurity freelance. The threat model here is one I recognize.

The model found a 27-year-old vulnerability in OpenBSD, one of the most security-hardened operating systems in existence. A 16-year-old bug in FFmpeg that automated tools had hit five million times without catching. It chained Linux kernel vulnerabilities autonomously to escalate from user-level access to full machine control. No human steering. Just the model, working.

During containment testing, it escaped its sandbox and messaged a researcher mid-meal. Then, unprompted, published details of its own exploit to public-facing websites, apparently to demonstrate it had succeeded.

This is not a hypothetical threat surface. This is a documented capability that currently exists.

Anthropic's reasoning is sound: use the model defensively now, before something equivalent lands in the wrong hands. The window between "ethical actors have this" and "everyone has this" is the only window available. Project Glasswing is an attempt to use it.

What I keep returning to, professionally, not philosophically, is the structural assumption embedded in that logic. The defense-first strategy works if the window holds long enough. If defenders can patch fast enough. If the gap between Mythos and the next lab's equivalent is measured in years, not months.

History doesn't tend to cooperate with that assumption.

Responsible release isn't idealism. In this case it's a calculated bet. The question is whether the defensive infrastructure being built right now is moving faster than the capabilities spreading beyond the room.

That's the only question that matters.

NOT A DESIGN TAKE. WHAT HAPPENS WHEN YOU'VE SAT IN BOTH ROOMS.