Watch this video to get instructions on the hand-off, credit to @Tori Gan @EJ @Rachel Newcomb for the Hand-off template

https://www.loom.com/share/079c503d9c054ef3916b1e5bd0ce9287

Phase by phase (as briefly told by the teams)

Major accomplishments/updates as told by teams per phase

Created content style guide to establish content design guidelines

Developed user stories and user journey maps as well as acceptance criteria to empathize with user needs and goals and inform UXW decisions respectively

Assisted UXR team to brainstorm research questions for evaluating brand voice and tone and generating insight on content style decisions to be made

Conducted literature review of Taíno history and language from Casa Areyto to inform introduction and first lesson content

Collaborate with UXD and Priscilla to iterate on content for introduction, first lesson, and onboarding flows | | | | Research | I conducted a language-learning app to gather insights on all aspects of the app, language, design, content, and legion, and identified commonalities and differentiators between those apps. We conducted an Unmoderated concept test to learn the Taíno community's perception of Gamification and DuoLingo to help the team identify which features to focus on. Brainstormed ideas to create a community and a bigger sample size. Grew our research sample size. Provided feedback and consulted XFN teams based on the insights derived from our concept test. Collaborated and met with Ra Ruíz Lastly, we conducted a Moderated concept test on the "Learn Taíno" flow. | | | | Design | - Competitive Analysis

• User Stories and User Flows (for the first 3 experiences: intro experience, first lesson, onboarding)
• Wireframes: low, mid, high fidelity
• Prototype: mid / high fidelity | | | | Dev | Created the file structure that will serve as the framework to organize the files and code for the server-side and the client-side of app. The server-side is based on the MVC (Model, View, Controller) model and software design pattern. The structure organizes the independent elements and their relationships into a seamless and collaborative architecture. The app.tsx is the entry point of the program on the server-side and will run as a daemon. The created folders on the server-side are models, views, controllers, routes, logic, middleware, public; containing subfolders for fonts, images, and icons, and config[uration]. The file structure and architecture provides an organizational basis for any future work and possible additional code. Within the view folder; provided code that can generate server-side render of UI elements. Provide two options to authenticate the user: Firebase and React-Native option. Created two options to manage the database with MongoDB using mongoose library and mongodb library. The two options can be used separately or work in combination of each other. Created the basic components generic to most mobile app and those individual components contains the basic elements and code necessary to for the basic UI and functionality. The components folder contains a file with code to form the basic theme and styling that will be basis of the UI of the app; and text follows that same pattern. The Error Boundary file and code provides for graceful failure of the code in case of error in production and the code should be the basis of any future work to account for any other issues. The code should serve provide generic error management for most components in the app, but syntax for all the code has a basic starting point for error management unique to that block of code. The typescript compiler options provides configuration for the current code and any future work. Included in the code is a short-list of additional options and descriptions. Provided comprehensive configuration to enforce code syntax in the eslintrc file and some enforcement in the prettierrc file. | | | | Product | | | | | Blockchain Architecture | | | |

Team Deliverables

To avoid duplicating work efforts, and to encourage greater communication and collaboration, look over each teams’ domains of the project.

****Content Style Guide - UXW Figjam (Sprint 3) | User personas - User journey maps - Storyboards - Information architecture - ****Interaction design - Affinity diagrams - Research plans - Presented research results - Surveys - Card sorts - Interview questions - Empathy maps - | - Wireframes and Design System

• Competitive Analysis, User Stories, and User Flows | Code - React Native:   Databases - MongoDB Github Merges - Documentation - Dev Documents Code Reviews - Informal Code Review No Documentation | Roadmaps - User journey maps - ****Development annotations - Flow charts - Sprint plans - ****Backlog upkeep - Competitive analysis - Product-market fit plans - MVP and MMP scope - Product requirements specs - User stories - Acceptance criteria - BDD scenarios - Annotations - | Presentations - Timeline status - Meeting recaps - Project sprint plans -

————— Google Account and Calendar creation and maintenance |

Hand-off files and important information

Subject Matter Resources

Research Team

Design Team

Content Strategy

Dev Team

Blockchain Architecture

Product Strategy

Project Lead

Drop the links to case studies here!

Related & Future Work

Models / Inspiration 🔥