-
Notifications
You must be signed in to change notification settings - Fork 8
User Manual
Before using our application, Learnify, our users should complete the signup process. This screen asks for a valid username(no other user use that username), an email address and a strong password(please check our glossary for our definition of "strong password"). Lastly, it asks for users to tick the box for accepting our General Terms and Privacy Policy. In this screen, we also have a button that navigates users to login screen.
After all those steps are completed, signup button becomes active in our mobile application. Other than that, it is in deactivated mode.
After pressing signup button, our users receive an email that contains a verification code and our application navigates them to verification screen. If a user tries to log in before completing the verification step, they are navigated to this screen after logging in. After verification step is completed succesfully, our mobile application navigates user to home page, and our web application navigates user to login page.
In our mobile application, verify button is in deactivated mode by default. After filling all 4 code fields, it is activated. This screen also has a countdown timer, resend verification code button and back to previous page button in our mobile application.
Users who completed signup and verification processes can enter our application by logging in. This screen asks users to enter their emails and passwords. This screen also have a button which navigates users to signup screen and a button which navigates users to forget password screen. If entered email address and password match after pressing log in button, our application navigates user to home page of our app.
In our mobile application, log in button is in deactivated mode by default. After filling both email and password fields, it is activated.
Users who can't remember their password can press "forget password" button in login screen to reach forget password screen. In this screen, users are asked to enter their emails. Then, a verification code is sent to the entered email address and users are navigated to verification screen, again.
This screen also has a button which navigates users to login page in our mobile application.
In home screen, enrolled learning spaces of user, top rated learning spaces and recommended learning spaces for user are shown.
In our mobile application, there is a "view all" button for all three types of learning spaces(enrolled, top rated and recommended). That button is activated whenever there are at least 8 learning spaces in that type. By pressing that button, users are navigated to a screen where they can see all learning spaces in the selected type.
This is the screen where you can find learning spaces you wish by entering the correct, related keywords to search bar. We use semantic search to find the learning spaces users aim to find.
In our mobile application, when a user enters the search screen for the first time, they see recommended learning spaces by default. After typing some keywords to search bar and pressing the search button, learning spaces found with related to entered keywords are shown to users. We also have user search in the mobile application. Clicking the found users navigates current user to that user's profile page.
In profile screen, profile picture, username, email and biography of the user are present. Users can change their biography from this screen if they wish.
In our mobile application, we also have two buttons named "Enrolled Learning Spaces" and "Created Learning Spaces". Clicking those buttons navigates user to a page where enrolled or created learning spaces are shown. We also have an indicator showing how many learning spaces the user created, enrolled in. There is also a setting button at the top, which will be detailed below. Finally, there is a log out button next to settings button, pressing that button logs the user out of our program.
In this screen, only enrolled learning spaces are shown. Additionally, there is a button for creating a learning space. Pressing that button navigates user to learning space creation screen.
In this screen, users are asked to choose an image among predefined images, enter a title, a description, a participant limit and choose category related to the learning space. Pressing done button creates the learning space and navigates user to the previous page.
In our mobile application, more than one category can be chosen and done button is activated after necessary fields are filled.
This screen includes detailed information about a learning space. In both mobile and web applications, description of the learning space, name of it, posts, events, discussion forum take place.
In our mobile application, enroll button takes place. Once user presses this button, they enroll the learning space and button text turns to "enrolled". Category takes place under description of learning space. Posts, create post button, forum, events and create event button takes place in this screen. When participants icon is clicked, participants of the learning space are shown. Pressing creator of the learning space navigates user to profile page of course creator.
In our web application, contributors and events take place in the right side of the screen. Posts are shown one after another in the middle and add post button takes place above the posts.
This is not a screen but a functionality. Users can enroll learning spaces in our application by triggering enroll functionality.
In our mobile application, there is a button with text "enroll" in learning space detail screen. Once this button is pressed, its text turns to "enrolled" and user who just enrolled is added to participants list. Also, the newly enrolled learning space is added to enrolled learning spaces list in both home screen and spaces screen.
This components/screens are used to add or edit post/material to a learning space.
In our mobile application, add post screen asks users to add a title and a content for the post to add. Done button is activated only when both input fields are filled. On the other hand, in edit post screen, title and content fields are filled with the texts to be edited by default. Making a change in those fields activates the done button.
This component is used to add comment to a learning space post/material.
In our mobile application, comment button takes place right to edit post button and under the post content. A dialog pops up by clicking the comment button. After inserting the comment in that dialog, done button is activated and comment is made.
Text annotation is one of the most important features in our application in both mobile and web. We have a fully functioning text annotation in both our mobile application and web application.
In our mobile application, posts/materials of a learning space can be annotated. After a long press on a text, text selection functionality becomes active. Then, users can choose the part of the text they want to annotate. After desired part is selected, annotate button can be selected. Then, a dialog for entering the annotation is opened. After entering a text to that dialog, done button is activated and annotation is made. Then, users can view the annotations they have made. Overlapping annotations are available in our application. By clicking on annotated text, users are navigated to annotation view screen. If an overlapping are is clicked, firstly a annotation selection dialog is opened.
Image annotation is one of the most important features in our application in both mobile and web, as well. We have a fully functioning image annotation in both our mobile application and web application.
In our mobile application, images in posts/materials of a learning space can be annotated. By clicking on an image, image view screen is opened. Then, by pressing on a region on the image, a selection rectangle is shown. Users can choose the part of the image they want to annotate with this selection rectangle. After that, a dialog opens again for users to enter the annotation text. After the text is entered, users can view the annotations they have made. Again, overlapping annotations are available in our mobile application. By clicking the annotated parts, users are navigated to annotation view screen. If an overlapping part is clicked both annotation text are shown in the annotation view screen.
Creating event by specifying geolocation is another important feature of our application. We have a fully functioning event creation feature both in our mobile app and web app.
In our mobile application, create event screen can be reached by clicking "Create Event" button in events section of the learning space detail screen. In this screen, users are asked to enter title, description, participation limit and duration of event. Then, they are asked to enter a date for the event. By default, date selection starts from the current time, selecting a previous date is not allowed by the application(it is programmed that way). Next, there is a map, users can select the geolocation of the event from that map, below that latitude, longitude and accuracy of the selected geolocation is shown. By default, first geolocation is the current geolocation of the user. For using this feature location services of the phone must be open. After entering all fields, done button is activated. Pressing the done button creates the event. Attend event button takes place under information of event, pressing that button adds users to participants list. Creator of event is automatically added to that list.
Other users' profile screen is just like user's own profile screen. Only difference is that biography cannot be changed in this screen.
This screen is only available on our mobile application. Users can reach this screen by pressing the setting button at the right top in profile screen. From this screen, theme and language can be changed. Users can also reach our app info and social account info from this screen.
Group Members
Meeting Notes of 451
Mobile Team Meeting Notes
Back-End Team Meeting Notes
Front-End Team Meeting Notes
Meeting Notes of 352
- Meeting #1 (04.03.2022)
- Meeting #2 (10.03.2022)
- Meeting #3 (17.03.2022)
- Meeting #4 (24.03.2022)
- Meeting #5 (31.03.2022)
- Meeting #5.1 (02.04.2022)
- Meeting #5.2 (05.04.2022)
- Meeting #6 (07.04.2022)
- Meeting #6.1 (12.04.2022)
- Meeting #7 (14.04.2022)
- Meeting #8 (21.04.2022)
- Meeting #9 (01.05.2022)
- Meeting #10 (12.05.2022)
- Practice App Requirements
- Practice App Use Case Diagram
- Practice App Sequence Diagram
- Practice App API Documentation
CMPE451 Milestones
- Will be added when ready