Built by Ky'lin Spears at 16.

I'm Ky'lin Spears, a Class of 2027 student at Suitland High School in Prince George's County, Maryland. Atomency started from a classroom problem: chemistry tools were hard to access, too closed off, or too simplified to help students really see what was happening.

Sole developer.

I built the molecular engine, Chemical Bench, simulation modules, NGSS alignment documentation, evidence portfolio, and this website myself. No team. No company.

16years old when building Atomency
2027graduating class at Suitland High School
1sole developer across product, chemistry engine, and site
The school context

Atomency was built from Suitland High School in Maryland, not from a company roadmap. That matters because the product is shaped by real classroom friction: school devices, short class periods, teacher trust, and students who need to see chemistry instead of only read about it.

The build

I wrote the molecular builder, valence rules, bond detection, formula checks, multi-vessel Chemical Bench calculations, simulation modules, standards notes, and public pages myself. The goal is not to look like every other education template. It should feel specific to chemistry.

The bet

If a student can build a molecule, drag atoms, pour one solution into another, watch color, gas, heat, and precipitate evidence, inspect speciation and pH, and explain what changed, chemistry becomes less abstract and less worksheet-only.

The standard

Atomency needs to earn classroom trust: fast enough to use live, clear enough for students, honest enough not to act like every task is just a calculator problem, and simple enough to deploy with no required backend.

Connected molecule preview with carbon, oxygen, hydrogen atoms, and visible bonds.

A tool with fingerprints.

The new direction should feel hand-built and specific: chemistry notebook, lab bench, molecular model, teacher desk. Less template. More purpose.