Duo and Nucli

One mascot for splitscreen.me, one for the handler tools. Both grow out of the splitscreen.me logo: Duo is its split blue window; Nucli is a quiet, helpful atom whose electrons are the players. One colour scheme each, the same in light and dark. The motion borrows BSManager's tricks: a wind-up before every move, squash and stretch, overshoot, and a pause before the spin.

Players: split and merge

One mascot per player. Duo splits off a new friend when a player joins and two of them crash back into one when a player leaves; Nucli pops an electron out, or swallows one. Each player can be present (a controller Nucleus can see), assigned (placed on a screen, holding a controller) or active (their game is running). Try the buttons, or click a mascot. Several clicks in a row run faster. Press 1 to 8 on your keyboard to press a button as that player.

1 player
  • Present Nucleus sees the device. Duo looks around; Nucli's electron is hollow.
  • Assigned Placed on a screen. Duo holds the player's device, ready; the electron fills in.
  • Active Their game is running. The Duos hop to a shared beat; the electron speeds up with a trail. Everyone active is a party, and even Nucli gets excited.
  • Device The small icon next to each player: controller, keyboard and mouse, keyboard only, or mouse only. Duo holds it and Nucli's electron takes its shape; a new device pops in with a jiggle.
  • Input When a player presses something, their Duo hops and their device and electron jiggle, like a haptic tap.

Quality pass

Every animation, with what I did to it. The lessons: long holds then a snap, hit stop on the big hit (impact frames tried, then dropped: they read as glitches), Duo bouncy (a bouncy ball), Nucli firm (a basketball), follow-through, and setup, pause, payoff. Everything as it was before is kept: the page before the quality pass, all animations and emoji included.

Duo's animations

For the app, the Hub, the website and Discord.

Nucli's animations

For the workbench, the VS Code extension and the CLI.

Loader experiments

Little Duos as loaders. Five tries, with my verdict on each; the winners are used below.

Earlier versions of each loader are folded away in its card. The whole page as it was before the quality pass: here; every step is also saved in the workbench repo (design/mascots/history/).

In the product

Loaders and states, ready to drop in. Each is one small SVG with CSS; nothing moves when the device asks for less motion.

Player setup

The player setup example is now its own page: App concept: player setup.

Discord emoji

Static and animated, at Discord's sizes: 22 px in a message, 48 px on their own, 16 px as reactions.

Small and in one colour

What I dropped, and why

Cushy (the couch) and Pip & Pod (the twins) were cute, but neither reads at 16 px, and the twins double every drawing. Nab (the bug-catcher) says "you made bugs", which is the wrong tone for beginners. Padd (the gamepad) is nearly a generic controller icon and repeats Duo's idea. The palette switcher is gone too: the logo's own colours work everywhere, so each mascot gets exactly one look.

Next steps

  1. Pitch Duo to the Nucleus Co-op maintainers (Discord). Nucli can start in the workbench right away.
  2. Once they're picked: export the emoji (128 × 128 PNG and GIF, under 256 KB each) and a sticker sheet.
  3. Workbench: Nucli in the empty Check tab, Test all (progress ring), fixes (toast), failed loads; Duo for Hub loading and the 404 page. Off in the alpha 8 look and when the device asks for less motion.