dotrarufu/is-25-perceivable

[paused] a survey for checking if 25% increase in change is actually perceivable

Is 25 Perceivable?

a survey for checking if 25% increase in change is actually perceivable

Inspiration

If you have read Refactoring UI by Adam Wathan and Steve Schoger, you might have a question, why 25%? In "Establish a spacing and sizing system" section, the book suggest that for a change to be perceivable, it should be around 25%, in other words, it should either increase or decrease by around 25% of the original size. The book did not explain why around 25% specifically.

Goal

This app aims to gather data from internet users to get the average score, and tell if 25% is really the value we need.

How does it work?

It's simple, users just look at the design's initial size, then after x seconds, the design will be resized by a random percentage. Then their score would be sent to the database, to move the centroid.

But isn't perceivable change magnified by the original size?

Yes, that's correct. This is why a user's score is recorded with the element's original size as well. This way, we can see the perceivable change values for different element's original size.

Motivation

I don't expect this project to be a success, but I hope it does. I just thought of this as cool. I guess I just can't get over from my previous project (related with this project)

is-25-perceivable's Issues

setup docker image for forks

initialize svelte project

initialize svelte project with

• tailwind
• routing
• vite

result page

a user must only be able to access this page once they have participated in the survey

• base size - significant change graph
• latest participants table

create readme

microinteractions

setup node server with docker for development

still not sure how back-end should work, but for now,

• docker for sqlite
• node with express (temporary, might use cloud functions)

select a random UI component and apply random sizing

should still look good even with random size

record correct guess

1. setup memory game-like flow
2. log score

limit user write amount

users must have limited amount of writes to scores

landing page

this page should introduce the app to users