Building comparison
head to head
Fruit NinjavsWarioWare: Touched!
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Fruit Ninja
Execution · Pure Mechanics
A swipe-em-up arcade game where slicing accuracy against random fruit spawns is the whole skill.
WarioWare: Touched!
Execution · Pure Mechanics
Touch-screen reaction speed against a randomised barrage of microgames.
Fruit Ninja leans Execution (Pure Mechanics); WarioWare: Touched! leans Execution (Pure Mechanics).
Fruit NinjaWarioWare: Touched!
Axis by axis
Execution7 vs 7
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Fruit Ninja
Swipe accuracy and combo timing
WarioWare: Touched!
Instant stylus reactions to five-second prompts are everything
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Fruit Ninja
No opponent
WarioWare: Touched!
No opponent - just escalating microgame speed
Variance3 vs 4
WarioWare: Touched! leans a little harder on variance, though the gap is small.
Fruit Ninja
Random fruit and bomb spawns
WarioWare: Touched!
Random microgame order demands instant recognition
Optimization2 vs 1
Fruit Ninja leans a little harder on optimization, though the gap is small.
Fruit Ninja
Combo and crit systems are shallow but real
WarioWare: Touched!
Each microgame is trivially solvable once recognised
A matching score does not mean a matching test. Two games can both sit at 10 on execution and demand completely different things of you - which is why the reasoning above matters more than the number beside it.