WiTalk

We connect newcomers to interpreters.

Comment

Inspiration

In our commitment to fostering inclusivity and easing the transition for newcomers to Canada, our team was inspired by the challenges faced by individuals navigating a new environment with a different language and culture. Recognizing the crucial role of interpreters in bridging communication gaps, we aimed to create a solution that would streamline the connection process between newcomers and skilled interpreters. The idea emerged from a desire to make essential services, such as medical appointments, immigration processes, and community interactions, more accessible to those who may face language barriers. The app serves as a digital platform, leveraging technology to match newcomers with interpreters who specialize in their specific needs, ensuring a smoother integration process. By embracing innovation, our team aspires to contribute to a more inclusive and supportive Canadian community for everyone, regardless of their linguistic background.

What it does

WiTalk is more than an app; it's a digital bridge fostering connections and empowering Canadian newcomers through language access. As part of our mission to create an inclusive community, WiTalk allows both newcomers and interpreters to sign up for distinct accounts, creating a platform where language is no longer a barrier but a bridge to opportunity.

Newcomers can seamlessly request and connect with skilled interpreters, ensuring clear communication in essential services such as medical appointments, immigration processes, and community interactions. With a user-friendly interface, WiTalk caters to individuals at all skill levels, creating a space where everyone can actively participate and contribute meaningfully.

In our commitment to building stronger, more connected communities, WiTalk envisions a future where language barriers are overcome, fostering understanding and inclusivity. Join us on this journey as we connect, bridge, and empower lives through the transformative power of language.

How we built it

In our collaborative effort, we collectively decided on a technology stack that complemented the diverse expertise within our team. Recognizing the varying skill levels, especially with some team members being beginners, we opted for a tech stack centered around vanilla HTML, CSS, and JavaScript for the frontend. This choice was intentional, as these technologies are widely understood and provided a solid foundation for everyone on the team. Despite our desire to create a mobile app, it was acknowledged that none of us possessed sufficient experience to justify its immediate implementation. Therefore, the decision was made to prioritize a web-based approach initially.

To ensure a smooth learning curve and create an environment conducive to collaboration, we deliberately avoided the complexity of frontend frameworks, focusing instead on building proficiency with fundamental web technologies. This decision allowed each team member to contribute effectively and laid the groundwork for a cohesive understanding of the frontend.

Simultaneously, we made the strategic decision to deploy the API as a separate service. This architectural choice not only facilitated a clear separation of concerns between frontend and backend but also positioned us for future enhancements. The separation ensured that, should the team decide to adopt a frontend framework in the future, the existing API service could be seamlessly integrated, allowing for flexibility and adaptability.

Our collective approach to the technology stack exemplifies our commitment to creating an inclusive and collaborative work environment. It balances the need for current proficiency with an eye towards the future, providing a strong foundation for the team to learn, grow, and adapt as our project evolves.

Challenges we ran into

Navigating the 36-hour hackathon posed a significant challenge due to strict time constraints, requiring the completion of the project within this limited timeframe. The fast-paced and intense nature of hackathons contributed to burnout among some team members, resulting in reduced productivity and motivation.

Another hurdle we faced was finding the right balance between the level of complexity and the team's competency. Our group comprised members at varying skill levels, including some who were relatively new to hacking. This prompted a crucial decision-making process—whether to develop a more advanced and technical product to challenge and innovate with the knowledge of experienced members or opt for a simpler approach that would allow our beginners to successfully contribute based on their current skill levels. This delicate balancing act aimed to ensure that everyone could actively participate and contribute meaningfully to the project.

Accomplishments that we're proud of

Our accomplishments stand as a testament to our dedication and teamwork. Leveraging Figma, we designed user-friendly interfaces that not only meet project requirements but also elevate functionality with an aesthetic touch. Demonstrating effective time and resource management, we successfully met deadlines, delivering a mostly functional project that aligns seamlessly with project specifications. Our proudest achievement, however, lies in our collaborative spirit. As a team, we seamlessly blended our strengths, navigated challenges together, and ultimately produced a high-quality project that reflects the collective efforts and dedication of each team member.

What we learned

While some of us were new to coding, we successfully designed and deployed a single-page web app. Our learning journey included mastering data storage with MongoDB, utilizing GCP to host the API for data retrieval, and deploying our website. The development process involved building a single-page app from scratch using pure vanilla JavaScript.

In addition to honing our coding skills, we became adept at collaborative work using GIT and implementing version control for our application. Our efficient collaboration extended to working closely with our UI/UX designer. Through constant communication, we ensured that design and functionality aligned seamlessly with our project goals. This collaborative approach allowed us to track changes effectively, managing the evolution of our application.

This collective experience not only bolstered our technical capabilities but also significantly enhanced our teamwork and communication skills.

What's next for WiTalk

Integrate a frontend framework like React or React Native to leverage built-in features such as routing and state management, streamlining the development process with functionalities that may be challenging to configure manually. Fortunately, implementing a frontend framework is feasible for us, given that our API is accessible irrespective of the frontend.

Enhance API security by implementing authentication headers. This additional layer of protection will safeguard against unauthorized access and potential security breaches, ensuring a more secure and resilient API.

Develop robust authentication and authorization mechanisms, prioritizing the secure and safe storage of user data to fortify overall system integrity.

Share this project:

Updates