V3 progress

[WhyAsh5114]

Many people want to know about the progress of V3 and when I plan to release it. I won't be able to give a fixed release date as that forces me to deliver an incomplete product like I did with V2, you can read more about that here.

I'll create a progress list here to avoid keeping everyone in complete darkness and update it regularly, I've removed most of the completed items from this to condense it like ExerciseSplit and Mesocycle stuff:

Working on right now

• Workouts
  • add and edit exercise
  • modify mesocycle exercise split days according to workouts
  • different set UIs for setTypes and modularize ExerciseCard
    • straight
    • v2
    • drop
    • myorep
    • myorep match
    • down/top
  • create workout endpoint
  • scaling bodyweights (1/3 for push ups, 1 for pull ups, etc.)
  • Temporary exercise skipping
  • ESLint CI/CD job
  • workouts list view page (basic)
  • workout view page
  • edit and delete workout
  • workout skipping
  • basic tests
  • overview page
  • compare action button implementation
  • Prefill exercise rep, load, RIR values when adding new ones
  • notifications! card example, scroll to the bottom
    • persistent workout time
    • card in settings and push notifications permission stuff
    • options to enable/disable particular types of notifications
  • Progressive overload function...
  • 1 RM calculation when changing rep/load values
  • comprehensive tests
  • workouts list view page filters

Soon

• PWA not working properly: offline support and caching should be tested thoroughly
• posthog for analytics
• Mesocycle end options: extend, deload, finish
• Automatic deload creation
• Thorough tests for exercise splits and mesocycles, (start immediately, cut, copy, paste, progression overrides, swap split day exercises, warnings, errors, etc.)
• Migrate to cuid2, cuid package is not secure Make cuid2 available in @default prisma/prisma#17102
• manual update & app version section in settings
• Offline indicator icon
• Clear local storage runes whenever PWA updates
• Post activation potentiation Menno's post
• DOCS! each info popover should link to a docs section?
• Consider wrapping Prisma queries in try-catch, errors do happen like can’t reach database and transaction failures Prisma Docs
• Helper popovers in exercise-splits
• A zone mode for mesocycle cyclic set changes that has levels of specialization each with its own setChange property for volume distribution, can be represented in DB with optional zone property
• Lengthened partials should be set by using -negative RIR, -2 RIR means 2 lengthened partials?
• Shallow routing for drawers
• Also proper routing for Previous and Next buttons during big form creations. Using previous and then hitting back, does weird stuff, make it more intuitive
• Make sure logging out and logging in again doesn’t leak previous user info
• motivational quotes pre, intra, and post workouts?
• Web metrics Fireship video
• Migration function from v2 (maybe v1)
• Index creation (cockroachDB gives recommendations in the databases section), also checkout insights section
• Home page (meso info, today’s workout, stats)
• Settings (preferences like weight increments?)
• Profile (workout stats and stuff)
• Checkout GitHub issues of repo for feature requests https://github.com/WhyAsh5114/MyFit/issues
• Offline testing for saving workouts offline
• Allow workout creation without a mesocycle (with option to manually select a reference workout. With a mesocycle, reference workout will be set automatically)
• Weight units (lb and kg)
• Exercise swapping, when you change gyms and stuff, you can swap out exercises, a swappedOut state for the swappedOut exercise maybe?
• mesocycle workouts tab, progression, list, and a lot of stuff
• speed up /workouts/new/start and /exercises page, it takes quite the time to load
• backgroundSyncPlugin queue UI and sync implementation (show pending requests in UI)
• Migrate to shadcn charts?
• Replace onMount functions with $effect to refresh page when page data changes
• Data entry
  • exercises
  • splits
  • helper popovers

Pre-production

• A proper CI/CD pipeline with database migrations, simulate workflows locally, see fireship video https://youtu.be/yfBtjLxn_6k
• GitHub sponsorships (in repo settings)
• About section with donation options in the app itself
• Privacy policy, user consent, update OAuth providers and more if wanted?
• https://web.dev/articles/building/an-adaptive-favicon#markup
• Publish on GitHub apps and Play store
• Complete svelte 5 migration, enable runes mode in compiler option
• Move other vercel projects to different vercel account
• New README, contributing guidelines, code of conduct
• database backups, a migration model

Maybe

• Re deploy v1
• use bun instead of npm
• Help migrate svelte-sonner and cmdk-sv to svelte 5
• i18n
• Monetization? Ads model (show ads and go ad free with premium), freemium model (100 workouts free), donations only?

Post production refactors

• use builder design pattern to build the create query of complex nested objects on the frontend itself. To ensure the create query is safe, use EntityUncheckedCreateWithoutUserInput to avoid unauthorized user creation
• separate create, edit, and view pages, avoid using manage for both create and edit, too many if conditions
• use svelte query to manage loading and error states
• wrap every possible error in trycatch
• change bodyweight fraction from null | number to just number, 0 by default instead of null

[yzee-tech]

Are there things other people could help you with? For monetization, I think you should do a paypal link!

[WhyAsh5114]

It depends on your experience with svelte and the rest of the tech stack. You can help me with either super basic stuff like the data entry section, or even implement your own feature in a PR. Just a suggestion before starting to create a new feature, try to discuss it here so you can make sure that it'll be used and implemented appropriately.

[yzee-tech]

Not too familiar with svelte, is there an intro/tutorial that you recommend?

[WhyAsh5114]

You can start with their official tutorial: https://learn.svelte.dev/tutorial/welcome-to-svelte
Although keep in mind that I'm currently using Svelte 5 which is in release candidate and should be released soon, there are a few differenced in both but they are both inter-compatible, Svelte 4 code will (mostly) work with Svelte 5.