Technologies for Interactivity
HEADS UP!
I am rebuilding all content from the ground up as I had to migrate to a new CMS. The older content has been archived, but will slowly return!
Hi! I’m Chuan Khoo, PhD (IPA: ʧuɑn ku) and the author of Technologies for Interactivity (TforI).
I’m creative practitioner, researcher and educator, and enjoy working between the digital and tangible realms in designing interactivity.
Technologies for Interactivity is a learning supplement to the technological components that I teach across multiple courses surrounding interactive technologies. The content here is specific to a range of hardware and software frameworks I employ in working with digital media, electronics and interactivity. If you are a student in one of my courses, refer to the course materials first, and consult this online resource as a scaffold to the core content.
This resource does not cover the basics of electronics prototyping – there are plenty of resources available online for that. You may want to refer to the Curated Links pages for links to useful, relevant Internet resources. Additional links provided within each article will also point you towards the right direction.
Who is this for?
Technologies for Interactivity is written for anyone who wants an introduction to the world of physical computing, pick up some software frameworks and coding to prototype and integrate ideas related to interactivity in their creative work.
It is pitched towards creative practitioners who have moderate to little experience in coding, electronics and related software platforms, but want to experiment with these technologies in their own field of creative work.
Disclaimer
You assume personal responsibility and liability in assessing the suitability of the circuits, your own wiring and further modifications to the code. The recipes and information are provided only as a starting point and safety concerns should be sensibly considered on your own part. I will not be responsible for any electrical catastrophe, injury or death that may arise from the use, improper or otherwise, of my code and example circuitry.
Referencing
Please be nice and respect the usage licenses for the content published here. This free online resource takes a lot of time and effort to produce, update and maintain (including the occassional rebuild).
If you reference and post derivatives of the work online, please note that all content on this website, unless otherwise stated, is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Sample code is generally released under the MIT license. Please check the individual examples for further details.
If you use the content here (notes, circuits, example code), please cite the source properly using an appropriate format as required by your academic submission requirements.
Digital Object Identifier (DOI)
Technologies for Interactivity has a DOI: https://doi.org/10.26180/25608399.v3
Please use the DOI if you are referencing the site in its entirety. If you are referencing a specific page, here are some examples for citing them (or follow your library’s citation templates):
Chicago 17th (B)
Khoo, Chuan. 2024. “Servos”. Physical Computing/Expressions, Technologies for Interactivity. Educational resource.
Published September 23, 2024. http://chuank.github.io/learning-v2/permalink.
Harvard
Khoo, Chuan 2024. Servos - Physical Computing/Expressions, Technologies for Interactivity, viewed 23 September 2024, <http://chuank.github.io/learning-v2/permalink>.
APA 6th Ed.
Khoo, Chuan. (2024). Technologies for Interactivity. Servos - Physical Computing/Expressions. Retrieved from
http://chuank.github.io/learning-v2/permalink
As content can get updated over time, please refer to the footer of each page for the Last Updated datestamp.
Acknowledgements
Acknowledgement of Country I wish to acknowledge the Traditional Owners of the unceded land, the Wurundjeri Woi-wurrung and Bunurong peoples, on which the content and intellectual property of this website was produced.
Technologies for Interactivity would not have been possible if not for the open-source community, including open-source hardware vendors, the software libraries contributed by the coding community, and of course the various toolkits and support software used to build this site.