Inspiration
Two of our members are currently enrolled in CS350 (Operating Systems Course), and we wanted to play around with what we learned about processes. We also wanted to see how far the kernel will let us mess around terminating processes and see what protections there are.
What it does
It allows a mobile device to track the processes of a computer. It also allows the mobile device to send signals (SIGINT and SIGTERM) to processes.
How we built it
We split the development between front and backend. The frontend is made with React Native and the backend is made with Python. They both communicate with each other through FastAPI and Uvicorn.
Challenges we ran into
A lot of the issues we ran into were mostly due to inexperience with React Native, FastAPI, and Uvicorn. We also ran into problems with eduroam and end-to-end communication between two devices.
What we learned
The most important lessons we learned are of communication and project management. We had to quickly brainstorm our ideas and divide the work amongst ourselves whilst helping each other get through unfamiliar tools.
What's next for Remote Process Tracker
We're aiming to better refine the tracker and improve the UI/UX experience. We also want to add more information and functionality for the user.
Log in or sign up for Devpost to join the conversation.