Boris Portarski

I m building APEX PULSE PRO around a simple idea:

Personalization is useless if the system forgets your constraints.

If you say avoid overhead pressing , asking for a harder upper-body workout shouldn t quietly bring overhead pressing back later.

That sounds obvious, but I think it s a good test of whether an AI coach is actually adapting or just generating another workout.

I m building APEX PULSE PRO, an AI fitness and performance product.

The idea is not to make another workout tracker or a chatbot with fitness prompts.

I want the product to feel like one connected system where the athlete, training decisions, feedback, and AI all work together.

A big part of that is APEX Core - the visual and interactive center of the product. It is meant to communicate state and make the experience feel more alive, rather than just adding more dashboards and metrics.

I ve been paying closer attention to onboarding flows lately. A pattern I keep noticing is that products often try to explain everything before the user has done anything. Feature tours, tooltips, welcome screens, setup questions all before the user has experienced the core value. I used to assume more explanation meant less confusion. Now I m not so sure. The products I remember most clearly tend to get me to one useful action first, then explain things when they become relevant. I d be interested in how other makers think about this: At what point does helpful onboarding become friction?