littleBits XOR Bit (w17) vs Sequencer Bit (i22): Which Logic Bit Fits Your Build?

Quick answer

The littleBits XOR Bit (w17) and Sequencer Bit (i22) are different tools, not interchangeable logic blocks. The XOR Bit is a logic gate that outputs when exactly one of two inputs is active, so it suits conditional, either/or behavior. The Sequencer Bit is a timing and sequencing block that steps through outputs in order, so it suits patterns and timed routines. If you need branching logic, choose XOR; if you need ordered steps, choose Sequencer. Neither is a substitute for the other, and neither is a good fit for projects that need a simple on/off toggle, a signal split, or a custom circuit—those call for different Bits entirely.

If you're building with littleBits and trying to decide between the XOR Bit (w17) and the Sequencer Bit (i22), the short version is that they solve different problems. The XOR Bit is about making a decision based on two inputs. The Sequencer Bit is about doing things in a specific order over time. Choosing the wrong one usually shows up as a circuit that either fires when you don't want it to, or never advances the way you expected.

This comparison sticks to what the supplied catalog facts actually say about each Bit and avoids guessing at specifications that aren't listed. Where a detail isn't provided, that's a real limitation you should factor into your decision. We'll also point to other littleBits products that cover the jobs these two Bits don't, so you can pick the right part the first time.

What the XOR Bit (w17) actually does

The XOR Bit is a logic gate. Its job is to look at two inputs and produce an output only when exactly one of them is active. In practice, that means it's useful for either/or behavior: if input A is on and input B is off, the output fires; if both are on, the output does not. This is the kind of behavior you want when two sensors or triggers shouldn't be able to activate the same output at the same time.

Because it's a logic Bit, the XOR Bit is best understood as a decision-maker in a chain, not a timing device. It doesn't count, step, or remember a sequence. If your project needs conditional behavior—one trigger or the other, but not both—the XOR Bit is the right tool. For projects that need ordered steps over time, it's the wrong tool, and no amount of rewiring will change that.

• Use XOR when two inputs should never both drive the same output.
• XOR is a decision gate, not a timer or counter—don't expect it to sequence anything.

What the Sequencer Bit (i22) actually does

The Sequencer Bit is a timing and sequencing block. It steps through outputs in order, which makes it the right choice when your project needs a routine: light this, then that, then the next thing. Think of it as the part of the circuit that decides what happens first, second, and third, rather than which of two inputs wins.

This is a fundamentally different job from the XOR Bit. A sequencer doesn't evaluate whether one input or another is active; it advances through a pattern. If your build is about choreography—blinking lights in order, a timed chain of actions, a step-by-step routine—the Sequencer Bit is the natural fit. If your build is about conditional logic, the Sequencer Bit will feel like the wrong kind of control.

• Sequencer is about order and timing, not either/or logic.
• If your project needs a condition (only one input active), a sequencer won't give you that behavior.

The trade-off in plain terms

The core trade-off is decision versus sequence. The XOR Bit gives you a logical condition: exactly one of two inputs. The Sequencer Bit gives you an ordered pattern over time. You can't get either behavior from the other Bit, and the supplied catalog facts don't describe the XOR Bit as a sequencer or the Sequencer Bit as a logic gate. That's the honest limitation to plan around.

A second trade-off is complexity. Logic Bits like XOR add a layer of conditional thinking to your circuit, which is great for interactive projects but can be harder to debug when a build misbehaves. Sequencers add a layer of timing, which is great for routines but can be harder to adjust once a pattern is set. Pick the one that matches the problem you're actually solving, not the one that sounds more advanced.

• If you can describe your project as an if/then condition, lean XOR.
• If you can describe it as first/then/next, lean Sequencer.

Bits that cover the jobs neither one does

Sometimes the real answer is that you need a different Bit entirely. If your project needs one output to drive several inputs at once—say, triggering light, sound, and motion together—the littleBits w2 branch Bit is the practical choice, since it lets you connect the output of a single Bit to as many as three others in different directions. That's a routing problem, not a logic or sequencing problem.

If your project needs a momentary press to become a stable on/off state, the littleBits w8 latch Bit converts a momentary input into a latching on/off output, much like a toggle. And if you're experimenting with audio effects rather than logic, the littleBits i35 delay Bit takes incoming audio and repeats it like an echo. These aren't substitutes for XOR or Sequencer, but they often solve the problem people actually have when they reach for a logic Bit by mistake.

• Branch for splitting one output to multiple destinations.
• Latch for turning a button press into a stable on/off state.
• Delay for audio echo effects, not logic.

How to decide before you buy

Write down your project in one sentence. If that sentence contains the word 'or' or 'only when,' you're describing XOR behavior. If it contains 'then' or 'in order,' you're describing sequencer behavior. This single test resolves most of the confusion, because the two Bits are built for different questions.

If your sentence describes something else—splitting a signal, latching a button, or prototyping a new circuit—look at other littleBits parts first. The littleBits w29 perf Bit, for example, is a standard 0.1" perfboard with a VCC and ground bus connected to bitSnap connectors, which makes it a quick way to prototype a circuit for a brand-new Bit. Buying the wrong logic Bit is a common and avoidable detour.

• One-sentence test: 'or/only when' means XOR; 'then/in order' means Sequencer.
• If neither description fits, you probably need a different Bit category entirely.

XOR vs Sequencer trade-offs

• Decision vs order: XOR answers 'which of these two inputs is active?' while Sequencer answers 'what happens next in the pattern?' Pick XOR for conditions, Sequencer for routines.
• Debugging friction: Logic conditions can be harder to trace when a build misbehaves, while timing patterns can be harder to adjust once set. Choose the friction you'd rather troubleshoot.
• Wrong-tool cost: Neither Bit can do the other's job, and the supplied catalog facts don't describe overlap between them. If neither fits, check branch, latch, delay, or perf before buying.

Product facts

• littleBits w2 branch: The branch Bit gives you more options for connecting your Bits: it lets you connect the output of a single Bit to as many as 3 others, oriented in different directions. If your real problem is sending one signal to several destinations—not choosing between inputs—the branch Bit solves it directly, and neither XOR nor Sequencer will.
• littleBits w8 latch: The littleBits w8 latch Bit transforms any momentary input, such as a button or trigger Bit, into a stable on-off switch, much like a toggle. When you want a single press to stay on or off, latch is the correct tool. XOR and Sequencer don't provide that toggle behavior.
• littleBits i35 delay: The delay Bit takes incoming audio and repeats it, like an echo. If your project is about audio effects rather than logic or sequencing, the delay Bit is the relevant part, and it's a reminder that 'logic Bit' isn't always the right search.
• littleBits w29 perf: The perf Bit is a quick and easy way to prototype a circuit for a brand-new Bit, with a standard 0.1" perfboard with a VCC and ground bus connected to bitSnap connectors. For builders who need custom behavior that no stock logic Bit provides, perf is the prototyping path rather than buying a Bit that only half fits.

Which logic Bit fits your build

Best for

• Builders who need either/or behavior where exactly one of two inputs drives an output (XOR Bit w17).
• Builders who need an ordered, timed pattern of steps in a project (Sequencer Bit i22).
• Makers running interactive or routine-based projects who can describe the goal in one sentence.

Not for

• Projects that need one output split to several destinations—use the littleBits w2 branch Bit instead.
• Projects that need a momentary press to become a stable on/off toggle—use the littleBits w8 latch Bit instead.
• Audio echo effects—use the littleBits i35 delay Bit instead.
• Custom behavior no stock Bit provides—start with the littleBits w29 perf Bit instead.

The XOR Bit (w17) and Sequencer Bit (i22) aren't rivals so much as different categories of tool: one decides between inputs, the other orders events over time. Match the Bit to the sentence you'd use to describe your project, and if that sentence is about splitting, latching, audio, or prototyping, reach for branch, latch, delay, or perf instead. Buying the right Bit once is faster than rewiring around the wrong one.