-
Notifications
You must be signed in to change notification settings - Fork 1
Lab‐6 User Stories
Bulingo currently only offers a light theme, which can be uncomfortable for users in low-light environments or at night. Dark mode is becoming a standard feature in applications, as it reduces eye strain and can save battery life on devices with OLED screens. By implementing dark mode, we can improve user experience and increase usability for those who prefer or require a darker interface.
- Age Range: Primarily 15-40 years, as well as adult language learners.
- Tech-Savviness: Users are generally comfortable with technology, expecting intuitive interfaces and customization options like dark mode.
- Primary Usage Times: Many users access the app during early morning, evening, and late-night hours, often in environments with low lighting.
- Device Types: Users typically access the app on mobile devices, particularly smartphones, with a portion using tablets and desktops.
- Accessibility Needs: Some users may have visual sensitivities or other accessibility needs that make dark mode a preferred or necessary option.
- Enhance User Comfort: Allow users to enable a dark theme to reduce eye strain, especially during nighttime use.
- Increase Accessibility: Ensure the app is usable and visually pleasing in both light and dark environments.
- Retain User Preferences: Save the user's dark mode preference so they don’t need to toggle it each time they open the app.
- Meet User Expectations: Provide a dark mode option to keep up with user expectations for modern applications.
As a user who frequently studies vocabulary at night, I want to enable dark mode in the app settings, so that I can continue to use the app comfortably without straining my eyes in low-light conditions.
Most Turkish students have a lot to do during their educations. They need to optimize their daily schedule to study, work and learn English which can be frustrating. While solving quizzes on the app, students may remember another urgent task that they've forgotten and may need to quit quiz immediately. After they are done with their other work, they can continue the quiz from where they've left without losing their progress.
- Age Range: Any user who has a busy daily schedule, mainly students and workers who need to multitask.
- Primary Usage Times: Students may need this feature after they return from school, during evening and night hours.
- Device Types: Users can solve quizzes from their computers or tablets when they are home and from their cell phones in anytime.
- Duration: Solving few quiz may take up to 40-60 minutes.
- Letting users to keep their progress even if they quit the quiz before it's done.
- Letting busy users, such as students workers, to multitask and be able to use the app even in their rush times.
- A Turkish student opens the BuLingo app after she/he returns from a busy day at school.
- The student needs to solve quizzes before her/his IELTS exam next week.
- After solving a quiz for a while, she/he remembers that she/he has a job interview in 5 minutes.
- The student quits the quiz immediately and handles the other task.
- When the student comes back to the same quiz, she/he sees a resume quiz button and clicks it.
- The student sees that her/his progress is not lost and continues studying.
🏠 Home
- Oktay Özel
- Aras Taşçı
- Yunus Emre Özdemir
- Kaan Yolcu
- Elif Nur Deniz
Eymen Çeliktürk- Anıl Köse
Battal Hazar- Halil Özkan
Ebru Özçakı- Ali Tarık Şahin
- Ahmet Oğuz Engin
- Yağız Güldal
- Lab Report 1
- Lab Report 2
- Lab Report 3
- Lab Report 4
- Lab Report 5
- Lab Report 6
- Lab 7 PR
- Lab 8 PR
- Lab Report 9
- Lab Meeting 1
- Weekly Meeting 1
- Lab Meeting 2
- Weekly Meeting 2
- Frontend Meeting 1
- Lab Meeting 3
- Weekly Meeting 3
- Lab Meeting 4
- Frontend Meeting 2
- Weekly Meeting 4
- Weekly Meeting 5
- Frontend Meeting 3
- Lab Meeting 5
- Weekly Meeting 6
- Weekly Meeting 7
- Lab Meeting 6
- Weekly Meeting 8
- Lab Meeting 7
- Lab Meeting 8
- Weekly Meeting 9
- Requirements
- Elicitation Questions
- Project Plan
- Use Case Diagram
- Sequence Diagrams
- Class Diagrams
- Front-End Mockups
- Mobile Mockups
- User Scenario 1
- User Scenario 2
- User Scenario 3
- User Scenario 4
- User Scenario 5
- RAM
- Tags Documentation
- Domain Specific Improvement Ideas
- Lab-6 User Stories
- Customer Milestone 2 Plan
- Software Quality Plan
- Implemented Requirements For Milestone 2
- Customer Milestone 3 Plan
📅 Meetings
- Meeting 1
- Meeting 2
- Meeting 3
- Meeting 4
- Meeting 5
- Meeting 6
- Meeting 7
- Meeting 8
- Meeting 9
- Meeting 10 - Class Diagrams
- Meeting - Frontend 1
- Meeting - Backend 1
- Meeting 11
- Meeting - Backend 2 Wikidata
- Meeting - Frontend 2
- Meeting - Deployment
- Meeting - Frontend 3
- Meeting 12
- Meeting - Backend 3
- Meeting - Backend 4
- Meeting - Frontend 4
- Meeting 13
- Meeting 14
- Meeting 15
- Meeting 16
💻 Project
- Class Diagrams
- Sequence Diagrams
- Use Case Diagrams
- Requirements
- Elicitation Questions
- Project Plan
- Work Done By Each Member
- Milestone Report 1
- Scenarios-Mockups
- Responsibility Assignment Matrix
- Responsibility Assignment Matrix Old Version
- Related Software Analysis
- Workdone Each Member Milestone 2
- Milestone 2 Report
- Work Done By Each Member Milestone 3
- RAM 3
- Milestone Report 3