It is now possible to book the Baby Builder. The installation has proven to be a perfect match for places (e.g. festivals, exhibitions, museums, schools) on the cutting edge of technology, science and art.
To accomodate the exposition of the installation we have updated it with some quality of life changes. One of the new features is an automated reset that occurs if there hasn’t been user-input for more than 90 seconds. This has been implemented to allow the installation to keep running on its own, even if a user abandons the installation halfway through. Among other things we have also simplified the survey at the end.
We also implemented an option for the user to opt out of any data being saved. The data we save from the session is already pretty limited, but choosing to opt-out doesn’t save any session data at all. All it does is add an entry that the user opted out; this way we can still confirm that the user completed an entire session of the Baby Builder.
The Baby Builder is an interactive installation in which you can design your own child through genetic engineering. It is built using the Unity engine and designed for use on touch screens. I worked on the application from the prototyping phase onwards. I have now developed it into a full-fledged application that has been on display at several exhibitions and festivals. The Baby Builder has also been nominated for the Young Talent Award at the Dutch Design Week 2020.
“Whatever your point of view may be, the Baby Builder challenges the audience to confront the ethical, societal and moral questions raised by the development of genetic engineering.”1
I developed the interface of Baby Builder to be scaleable to most, if not all, aspect ratios. Since the design went through quite some iterations I made sure that the moving around of elements wouldn’t impact my development time. The result is a very flexible application that can be displayed on any kind of screen. Be that on a mobile phone, a tablet or a large touchscreen for example.
The first iteration started out with a simple interactive prototype. After prototype testing with several test groups, an improved design was created and delivered to me. You can see some frame elements carrying over in the screenshots of the first and second prototype below. The first prototype was pretty limited so most elements were created from scratch while implementing the final design.
Given the design contains many recurring elements; I made sure to develop all frames modularly based on prefabs. Updating existing frames or adding new ones is just a matter of using/editing the building blocks already created.
The Baby Builder gives you a score at the end based on how many modifications you applied. This score is calculated from each frame using Scoring Modules. Scoring modules are currently configured by hand and manually plugged into the score calculator. In case of further development I would rewrite this to a dynamic system that passes through all frames and calculates scores based on the contents of the frame automatically.
One of the requirements for the Baby Builder was to store the data produced by the application. Given the limited scope of the project I solved this by locally saving the data. All data produced from the application is saved to a single comma seperated file (.csv). The file creates a backup after every session. An example of the data saved is shown below.
The video below shows the Baby Builder application front to back.