Karma Numbers: controlled course access, PWA and Telegram

The public catalogue introduces materials, while the account organizes content granted after payment or approval. Access can be time-limited. This separation allows courses to be presented without automatically exposing restricted materials.

The admin panel and CRM bring together the catalogue, enquiries, orders, users and media files. PWA and Telegram mini-app access provide return paths for an audience using phones and messaging.

Karma Numbers has two usage contexts. Someone discovering the platform explores its public offer of courses, meditations and practices. A user with access already granted looks for materials inside a personal account. Separating these contexts lets presentation pages explain products while the account focuses on content available to a particular person.

For an educational product, this distinction affects navigation and action labels. Reading a course description and opening assigned material are different moments. The platform connects them through the account and access administration. Visitors can understand the offer before using its content, while returning users have a dedicated place for the materials available to them. The account therefore extends the product experience rather than repeating the public catalogue and its introductory explanations for prospective customers.

In Karma Numbers, access may follow payment or approval and can be limited to a defined period. These conditions belong to product organization, beyond the commercial presentation. A resource can exist in the public catalogue without being automatically open to every visitor. The account reflects the content granted to its particular user.

A relevant scenario is returning to a course after access has been obtained. The user needs to find the appropriate resource, while administration needs to follow the grant and its availability period. That relationship between user, product and access distinguishes this project from a website containing ordinary course pages. Its structure centers on controlled content delivery, with a clear separation between public presentation and the use of materials reserved for an entitled user.

The admin panel and CRM bring together the catalogue, enquiries, orders, users and media files. Their value lies in the relationships: a resource belongs to an offer, an enquiry belongs to a person, and access needs to be understood in relation to the relevant product. Administration becomes the operational center of the educational platform.

For the team managing Karma Numbers, content and user relationships are closely connected activities. Publishing or organizing resources is not entirely separate from incoming enquiries and orders. A shared system supports those working contexts. The public presentation therefore needs to relate to what the team can manage and what users can access. This structure explains the project more fully than the appearance of its homepage alone, particularly for ongoing content delivery.

The PWA and Telegram mini-app add access options for an audience using phones and messaging. They complement the website and account, keeping the platform close to everyday user contexts. Someone returning to a resource needs product recognition and a route to the relevant area, rather than another introduction to the overall offer.

Karma Numbers is live and development continues. Its direction connects catalogue, resources, users and administration, with web and Telegram entry points. The screenshot retained in this case shows the real public website and product identity. The explanation adds what an image cannot demonstrate by itself: how the presentation area relates to the account and access management. Those relationships define the course platform and the technical contribution documented here, beyond its public visual presentation.

The screenshots added on 26 September 2026 show performance 99/100 on desktop and 88/100 on mobile. Accessibility and best practices each score 100/100 in both tests. SEO scores 92/100 in the desktop report and 100/100 in the mobile report. LCP is 0.7 s on desktop and 3.8 s on mobile; CLS is 0 in both runs.

The gallery below preserves the full reports and lets visitors open them at their original size. These PageSpeed Insights / Lighthouse measurements complement the design presentation with loading data and technical page checks. Scores may vary between runs and do not represent Google rankings or a complete assessment of real-user experience.