Week #2

Week #2 #

Detailed Requirements Elaboration #

Mobile App

  • UseCases: Start a workout. Dynamically change it during session. Save it locally in database.
  • AI: See review of the workout. (Might be additions)
  • UI: Pages and widgets related to workout session. Graphs for tracking progress (exercise analytics, workout calendar)
  • Datasources: Prepopulated exercise information. Sql-based Database for local memory.
  • Design: Following clean architectures principles
  • Backend: For Synchronisation and AI endpoints usage.

Admin panel:

  • UseCases: Admins see analytics in the app
  • What Exactly?: Last Seen in Application; How often is usage; What is user doing in app (and more).
  • UI: Graphs, tables, logs
  • Backend: Endpoints for collecting data.
  • DataSource: Database for tracking UID of User with related data to it.

Prioritized backlog #

https://nodoser.atlassian.net/jira/software/projects/SCRUM/boards/1/backlog (Some tasks are omitted, for detailed contribution check weekly commits)

Project specific progress #

Mobile App #

  • Workout-related data (pictures; json) was created.
  • Model for exercise-information was designed.
  • Basic CI/CD (linting) was built and tested.

Main Backend (for mobile app) #

  • Based architecture was created (see more in personal contribution)

Frontend (Admin Panel) #

  • UI based on static data was created (see more in personal contribution).

Backend (Admin Panel) #

  • Based architecture was created (see more in personal contribution)

Weekly commitments #

Individual contribution of each participant #

Ivan Chabanov:

  1. Build basic CI/CD pipeline (linting)

  2. Implement model for exercise and generate a json of 30 exercises.

  3. Find a model for picture gen (SORA). Generate most of gym exercise pictures.

https://github.com/IU-Capstone-Project-2025/gym-genius/pull/7 https://github.com/IU-Capstone-Project-2025/gym-genius/pull/8 https://github.com/IU-Capstone-Project-2025/gym-genius/pull/9 https://github.com/IU-Capstone-Project-2025/gym-genius/pull/10

Vlad Kuznetsov:

  1. с нуля ΠΈΠ·ΡƒΡ‡ΠΈΠ» Π³ΠΎΠ»Π°Π½Π³; Ρ€ΠΎΡƒΡ‚Π΅Ρ€ chi, ΠΎΡ€ΠΌ gorm
  2. описал Π±Π°Π·ΠΎΠ²ΡƒΡŽ Π°Ρ€Ρ…ΠΈΡ‚Π΅ΠΊΡ‚ΡƒΡ€Ρƒ прилоТСния

https://github.com/IU-Capstone-Project-2025/gym-genius/pull/5

Egor Dushin:

  1. ΠΈΠ·ΡƒΡ‡Π°Π» Π΄ΠΎΠΊΡƒΠΌΠ΅Π½Ρ‚Π°Ρ†ΠΈΡŽ Nuxt 3

  2. Π²Ρ‹Π±ΠΈΡ€Π°Π» Π°Ρ€Ρ…ΠΈΡ‚Π΅ΠΊΡ‚ΡƒΡ€Π½ΠΎΠ΅ Ρ€Π΅ΡˆΠ΅Π½ΠΈΠ΅ - Π²Ρ‹Π±Ρ€Π°Π» atomic design Π°Ρ€Ρ…ΠΈΡ‚Π΅ΠΊΡ‚ΡƒΡ€Ρƒ ΠΈΠ·-Π·Π° возмоТности быстрой Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠΈ Π² ΠΊΠΎΠΌΠΏΠΎΠ½Π΅Π½Ρ‚Π½ΠΎΠΌ Π΄Π΅Ρ€Π΅Π²Π΅

  3. Π’Ρ‹Π±ΠΈΡ€Π°Π» ui kit, остановился Π½Π° Nuxt UI ΠΈΠ·-Π·Π° Π΅Π³ΠΎ ΡΡ‚Π°Π±ΠΈΠ»ΡŒΠ½ΠΎΡΡ‚ΠΈ ΠΈ лаконичности

  4. Π’Ρ‹Π±ΠΈΡ€Π°Π» стСк для Π³Ρ€Π°Ρ„ΠΈΠΊΠΎΠ², взял ChartJS, ΠΊΠ°ΠΊ ΡΠ°ΠΌΡƒΡŽ ΠΏΠΎΠΏΡƒΠ»ΡΡ€Π½ΡƒΡŽ Π»ΠΈΠ±Ρƒ для Π³Ρ€Π°Ρ„ΠΈΠΊΠΎΠ²

  5. Π Π΅Π°Π»ΠΈΠ·ΠΎΠ²Π°Π» Π³Ρ€Π°Ρ„ΠΈΠΊ активности ΠΏΠΎΠ»ΡŒΠ·ΠΎΠ²Π°Ρ‚Π΅Π»Π΅ΠΉ с Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΡΡ‚ΡŒΡŽ ΠΏΠ΅Ρ€Π΅ΠΊΠ»ΡŽΡ‡Π°Ρ‚ΡŒ ΠΈΠ½Ρ‚Π΅Ρ€Π²Π°Π» Π²Ρ€Π΅ΠΌΠ΅Π½ΠΈ. На статичСских Π΄Π°Π½Π½Ρ‹Ρ…, СстСствСнно

https://github.com/IU-Capstone-Project-2025/gym-genius/pull/6

Kirill Nosov

  1. Π‘ΠΎΠ·Π΄Π°Π½ΠΈΠ΅ структуры Π±Π΅ΠΊΠ΅Π½Π΄Π° Π½Π° Π°Π΄ΠΌΠΈΠ½ΠΊΠ΅
  2. ΠŸΠΎΠ΄ΠΊΠ»ΡŽΡ‡Π΅Π½ΠΈΠ΅ Ρ„Ρ€Π΅ΠΉΠΌΠ²ΠΎΡ€ΠΊΠ° для api (fiber)
  3. Π˜Π½ΠΈΡ†ΠΈΠ°Π»ΠΈΠ·Π°Ρ†ΠΈΡ Π±Π΄ (ΠΏΠΎΠ΄ΠΊΠ»ΡŽΡ‡Π΅Π½ΠΈΠ΅ gorm)
  4. Π˜ΠΌΠΏΠ»Π΅ΠΌΠ΅Π½Ρ‚Π°Ρ†ΠΈΡ ΠΌΠ΅Ρ‚ΠΎΠ΄Π° для получСния ΠΈ записи активности ΠΏΠΎΠ»ΡŒΠ·ΠΎΠ²Π°Ρ‚Π΅Π»Π΅ΠΉ
  5. Π˜ΠΌΠΏΠ»Π΅ΠΌΠ΅Π½Ρ‚Π°Ρ†ΠΈΡ ΠΌΠ΅Ρ‚ΠΎΠ΄Π° ΠΎΡ‚ΠΏΡ€Π°Π²ΠΊΠΈ активности ΠΏΠΎΠ»ΡŒΠ·ΠΎΠ²Π°Ρ‚Π΅Π»Π΅ΠΉ для Ρ„Ρ€ΠΎΠ½Ρ‚Π° (Π² процСссС)

https://github.com/IU-Capstone-Project-2025/gym-genius/pull/11

Aleksandr Mihailov

  • Research Go docs
  • Research Fiber, Gorm libraries for backend
  • Decided whether to use cloud-based AI models or lightweight local ones.
  • Researched a cloud-based AI models services and pick model for application
  • Thought of where to use AI solutions in Mobile App

https://github.com/IU-Capstone-Project-2025/gym-genius/pull/12

Plan for Next Week #

Continue working on our features. Some of the tasks can be seen in backlog already: https://nodoser.atlassian.net/jira/software/projects/SCRUM/boards/1/backlog

Confirmation of the code’s operability #

We confirm that the code in the main branch:

  • [+] In working condition.
  • [+] Run via docker-compose (or another alternative described in the README.md).