MS7 - Curi-Grupo24/curi_app GitHub Wiki
Value Proposition
We made a Value proposition canvas to understand, articulate, and continuously improve our value proposition. These include customer-centric thinking, strategic alignment, and innovation, that will, ultimately, contribute to the success and sustainability of our business. With this in mind is impossible to not include the smart features because they can significantly enhance its value proposition by providing users with advanced capabilities, increased efficiency, and a better overall experience. These value proposition are also deeply tied to the PAS (Problem, Alternative, Solution), because it can be identifying the problems, Identify the Customer Needs with the alternative we can understand the existing solution and opportunity to differentiate from the rivals and with the solution we can highlight the unique selling points with that in mind the value proposition model must include both which have the smart features that we selected for each type of user added and it can reflect the insights we get when we did the PAS for our app :
Value proposal for a student taking a tutorship:
Value proposal for a student giving a tutoship:
Prototype
At this point we created a basic prototype with hard coded information to set the UI Kit we already stablished, on this Figma file we setted the design of the app we are developing: DESIGN FIGMA
here are the views we worked on:
- José:
Dashboard: In the dashboard we considered important to have the information of the classes I am taking as a student, the classes we have as a tutor and the schedule we have already as shown below:
Profile:
On the profile we want to see the reviews we have as a tutor, also, my main information as a user, so we decided to develop the following screen:
- Boris:
Class List: As we have the acces to our classes, we want to be able to search for them in case we have a great amount of classes, as shown below:
Notifications: As we setted the notifications as one of the core functions of the app we developed the notifications flow, just as following:
- Diana
As it was needed, I setted the constants of the app on the Theme of flutter, and also on the folder core I added constants that we agreed on the UIKit for us to be able to follow good practices on our developement.
Auth:
The first glimpse of the app an user has is the authentication flow, in the design we setted a modal for selecting the university the user is located in, but as we talked on the group, the wise decision to make was to make it only for Los Andes university so we skipped this step for the MVP, we have the flow for login, register and changing password bellow:
Enroll as a monitor:
One of the main flows of the App is enrolling as a monitor, so, following the design, we implemented the following view, we setted a button for entering the flow of enrolling as a monitor, even though the example we hardcoded already was a tutor, just to be able to access the flow, this button will not be there on the MVP, it was placed just for the purpose of accessing the flow: