ChemLab is a planned interactive chemistry environment for
building experiments from substances and conditions. The design
covers reaction equations, stoichiometry, concentrations,
temperatures, pressure and laboratory equipment. A timeline
would allow users to slow down fast reactions or accelerate long
experiments, with visual explanations, safety context and
reproducible experiment sessions.
Planned interactive reagent selection and laboratory
Planned interactive reagent selection and laboratory
equipment. This capability is documented in the project
material; the detail page distinguishes its intended user
experience from the supporting implementation and any
configuration needed to run it.
02
Planned slow/fast reaction visualisation with adjust
Planned slow/fast reaction visualisation with adjustable time.
This capability is documented in the project material; the
detail page distinguishes its intended user experience from
the supporting implementation and any configuration needed to
run it.
03
Planned temperature, concentration and kinetic model
Planned temperature, concentration and kinetic models. This
capability is documented in the project material; the detail
page distinguishes its intended user experience from the
supporting implementation and any configuration needed to run
it.
04
Planned experiment saving and educational safety exp
Planned experiment saving and educational safety explanations.
This capability is documented in the project material; the
detail page distinguishes its intended user experience from
the supporting implementation and any configuration needed to
run it.
02 · Technical structure
How the system works
Planned component boundaries and data flow.
01
The README describes a proposed modular architecture. No
executable implementation is verified in the repository.
01 · Input or user action
The workflow starts with the corresponding user choice or data
entry. Planned interactive reagent selection and laboratory
equipment. This capability is documented in the project
material; the detail page distinguishes its intended user
experience from the supporting implementation and any
configuration needed to run it.
02 · Application processing
The relevant component must interpret the input, apply the
project rules and coordinate any necessary storage, network
access or computation. The documentation below identifies
where that responsibility appears in the source when it is
evidenced.
03 · Result and feedback
The resulting screen, calculation or stored record should
reflect the processed state. Planned temperature,
concentration and kinetic models. This capability is
documented in the project material; the detail page
distinguishes its intended user experience from the supporting
implementation and any configuration needed to run it.
04 · Boundaries and verification
This page describes the documented behaviour, not an
independently verified live deployment. Runtime configuration,
permissions, test data or connected services may still be
required.
PROJECT WALKTHROUGH
Design & planned systems
Concept modules described in the product roadmap.
01
Experiment builder — planned
The design proposes selectable chemicals, concentrations,
equipment and environmental conditions as inputs to
laboratory-style experiments.
02
Reaction-time controls — planned
A central feature is the ability to slow down rapid processes
or speed up slow reactions while observing intermediate
stages, with reproducible time parameters.
03
Chemistry calculations — planned
Stoichiometry, balanced equations, yields, concentration and
thermodynamic constraints are to be connected to the visual
experiment.
04
Learning and safety — planned
Substance information, hazard awareness, guided exercises and
clear separation between simulated results and real chemical
procedures are part of the educational design.
03 · Explore
Project-specific preview
Planned interactive workbenchVisual preview · no reaction calculated
The liquids and colours are illustrative. No experimental
reaction, temperature curve or chemical measurement is being
simulated.
Visual studies · project-specific
Interface and system concepts
Independent illustrative views of the documented or proposed
workflows. They are not connected to a running backend, and
their values are not actual measurements.
Proposed digital lab · illustrative
Experiment preparation bench
A
B
Model
A safe educational setup specifies model inputs and
supported reactions before calculating or displaying
outcomes.
Reagent AReagent BVirtual vesselConditions
Proposed observation view · illustrative
Reaction timeline and measurements
A simulated timeline should derive its curves from a named
validated model rather than animating an invented reaction.
ConcentrationTimeTemperatureMeasurements
04 · Source and design
Implementation examples and code walkthrough
Illustrative design-only code. This is not part of an implemented
or executable application.
A proposed simulation step (pseudocode, not source code)
experiment = create_experiment(validated_reaction_catalog)
experiment.add_substance("A", quantity=0.1)
experiment.add_substance("B", quantity=0.1)
if reaction_catalog.supports(experiment):
results = kinetics.solve(experiment, time_step=0.01)
graphs.show(results, units=True, error_bounds=True)
else:
ui.show("Unsupported reaction — no result invented")
Code samples are excerpts or documented illustrations; surrounding
project files, configuration and dependencies may be required to
compile or run them.
05 · Visual material
Interface & screenshots
Screenshots from supplied documentation and repository media.
Missing visuals remain placeholders rather than invented screens.
▧
No verified product screenshot yet
To fill this space, add an approved screenshot with the exact
filename shown below. The site currently displays a neutral
placeholder.
assets/img/projects/chemlab/screenshot-01.webp
06 · Technology
Programming languages & stack
C++
Qt 6
QML
Core technologies and integrations used or planned for this
project.
File types identified: 1 .md
07 · Reality check
Status, evidence & limitations
The project status is based on repository sources and supplied
documentation. It may be updated as the project evolves. A
published case study is not a certification of production
readiness.
Features are based on the supplied README and code inventory; no
end-to-end runtime certification is implied.
08 · Resources
Downloads & project resources
Installers appear only after a verified release is added to the
public download directory. Unavailable builds are marked clearly.