Project Info
This project did not submit a demo video on Devpost.
Inspiration
Inspired by the pressing issues of the lack of tools to aid with non-verbal people, Flowspeak was born. Pulled from the ideas and struggles of non-verbal communication, Flowspeak is designed to solve most of the issues in terms of accessibility and ease of use.
What it does
Flowspeak utilizes Picture Exchange Communication System (PECS), an evidence-based and proven method of communication for those who are non-verbal. In this context, non-verbal refers to the inability of communicating using verbal and social cues, and mainly affects those who live with autism, cerebral palsy, down syndrome, and many others. With these cards, an online collection can be created, cataloged, and utilized by the end user. Out of a selection of the collection, possible sentences are formed and processed by Google Gemini, and returned as a set of possible expressions. For example, if a user selects the cards “Mother”, “Park”, and “Ice cream”, a possible sentence would be generated as “Mother, I want to go to the park and eat ice cream”. As a result, the text-to-speech engine takes the sentence and describes it out loud.
How we built it
Our tech stack mainly consists of a traditional full-stack application: React Native for the frontend, FastAPI and SQLite for the backend. Google Gemini powers the possible prompts, which allows for a much faster, and widely accessible platform. The backend also contains most of the data processing, as images are stored internally as their original bytes + hashed w/ SHA-512 to create a unique identifier. This would allow for thousands of images to be stored, and migrations to PostgreSQL can be done very easily through SQLModel.
Challenges we ran into
We found our final team member late, which set us behind schedule. Our planning took too long, and software limitations added further delays. We also struggled with React Native issues, forcing late-night fixes. Despite these setbacks, we learned the importance of careful planning and communication.
Accomplishments we're proud of
What we are most proud of is how we developed much faster processes for development. Utilizing templates, we were able to create our applications much faster and develop standards on the protocol. For example, the backend is designed with a philosophy of rapid iteration rather than spending time learning new technologies. With this, we were able to spearhead operations and develop something that we are ultimately proud of creating in the first place.
What we learned
We learned quite a bit. Ranging from working with React Native and getting emulators properly set up, to faster implementations for backend code and AI integration. This was really a time to shine despite all of the flaws that had been made. We also learned that careful planning really does matter. Without the planning of every single tool used, the designs, and so much more, this would result in finishing the project much faster and not spending so long spending those countless precious hours on it.
What's next
FlowSpeak has major potential for a proper deployment. With the right amount of internal funding, and support, we can entirely deploy this into production. The backend server is entirely designed to be operated with tools such as Docker, and our React Native codebase would need to be polished up in order to be deployed. The next step would be to deploy this to the real world and to get some test results!
This repository has no readme, or GitHub could not be reached.
Analysis
View
Metric
- 16
- 4
- 2
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- FastAPIIn code
- HTMLIn code
- JavaScriptIn code
- PythonIn code
- ReactIn code
- TypeScriptIn code
- Google GeminiClaimed
7 of 8 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
96 KB
Source files
65
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
UCMercedACM/flowspeak
323 files · 6.7 MB · @ d84f1fb
Structure
Interface
68 files · 21%Screens, components and styles rendered to the user.
API & routing
17 files · 5%Request entry points: routes, handlers and controllers.
Data & schema
3 files · 1%Schema definitions, migrations and data access.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- JavaScript78%
- Python18%
- YAML1%
- HTML1%
- CSS1%
- TypeScript0%
- Other (1)0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
app/package.json
npm · 9- @react-native-async-storage/async-storage
- expo
- expo-localization
- expo-speech
- expo-status-bar
- react
- react-native
- react-native-storage
- +1 more
server/requirements.txt
pypi · 9- aiosqlite
- fastapi
- google-generativeai
- orjson
- PyYAML
- sonyflake-py
- SQLAlchemy
- sqlmodel
- uvicorn[standard]
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.