Assignment items

Group assignment

Individual assignment

Fab Academy Rubric — Have you?
The criteria evaluators look for this week.





Tools

The process

Group assignment


We, as Vujade Fablab teams, divided the different platforms between us and each one started documenting their use to be compared and shared with the group and it can be found on these links 1 2 3. I will be working on MIT App Inventor as I already have experience with the platform

HTTP link
01| As you see, I already have many projects on MIT App inventor from 2023 and I also won first place in adult team category for creating PAM
HTTP link
02| I first created a new project for FabLab Review
HTTP link
03| These are the main section of this IDE, The palette where you can find all that component you can think about for building and App, the views to see the design of your App as your building and alinging the components, the layers of the components, and the properties which will change based on the component you select.
HTTP link
04| The main Pallettes are the User interface that include the buttons, text labels, input test, sliders, images and list picker are more. the properties of each will change when added to the canvas/phon view.
HTTP link
05| The layout pallets is one of the most important things you need to learn to do, because the arrangement of the element will depend of the nested layouts you create. adding a vertical scroll arrangement with 100% width and height then adding horizontal arrangement to keep selction and buttons aligned.
HTTP link
06| These are the list of the sensors available on the smart phone that we can connect to and use for different projects. Like screen tracking, phone gyro, magnetic field, etc.
HTTP link
07| Connectivity is where we can set up the connection for IoT via bluetooth or WIFI or arduino
HTTP link
08| Extensions is where we need more extension that can be added for more connectivity options and can be found on MIT App Inventor Extensions
HTTP link
09| After adding the components and changing the priorities and the alignment, we can move to the blocks screen to strat coding
HTTP link
10| when selecting any the components added, we will get the list of the functions, commands and attributes related to each.
HTTP link
11| This is a simple code to program a button, on Click function of Button1, Label1 text will change to "Hello World!"
HTTP link
12| then we can use the AI companion to connect the our smart phone and view real-time simulation.
HTTP link
13| By scanning the QR Code real-time simulation will start on your phone
HTTP link
14| the app can also be compiled and share on store
I like App Inventor
  • Feedback: I find it one of the best IDE to create interfaces and Apps
  • Challenge: IoT is challenging but im willing to learn


Individual assignment:


01: Creating my App


01| I created my app using MIT App Inventor platform. I designed the two clips, left and rightt, I added list view to search for Bluetooth devices and I added a number of text labels to update the status of the connection. as well as adding Calibration button to set the acceptable degree within the threshold define on the clips.

02| App inventor provide block programming functionality that eases the use of syntax coding. here I duplicated the same commands for the left and right clips, calling on the bluetooth connection and sending some parameters to the ESP32 C3 microcontroller

Very smooth
  • Feedback: I have previous experience using MIT App Inventor, so the interface itself was not difficult. Connecting it to external devices was a new area for me to explore.
  • Challenge: Next I want to pull data from the clips into the app and plot it in a clean chart — that would give more insight into the user's movements and how often they moved without responding to the vibration reminder.

Reflection

What worked
  • Having prior MIT App Inventor experience meant I could focus on the hard part — connecting the app to my hardware — instead of learning the tool.
  • Block-based programming made the UI logic fast to build and easy to read back.
  • The AI Companion + QR code gave me real-time testing on my phone without compiling each time.
What didn't
  • Connecting the app to the ESP32-C3 over Bluetooth was unfamiliar territory and took trial and error.
  • I duplicated the block logic for the left and right clips instead of finding a cleaner, shared approach.
  • The data-to-chart visualization is still a plan, not a working feature.
What I'd do differently
  • Design the Bluetooth message format first, then build the UI around it.
  • Use one reusable block procedure for both clips instead of duplicating logic.
  • Add the charting feature into the first build rather than treating it as a follow-up.
Key learnings
  • An interface is only as good as the connection underneath it — the hardware link is the real work.
  • Block programming lowers the barrier to building a usable app quickly.
  • Real-time simulation tightens the design loop and catches UI problems early.