Back to blog
Live Projects5 min readUpdated

KARMANUMBERS: designing courses, member access and mobile reading

Connect visual identity, the catalogue, content access and administration. Practical design decisions from the structure of the KARMANUMBERS educational project.

Editorial illustration: KARMANUMBERS: designing courses, member access and mobile reading
Contents

KARMANUMBERS is documented as an educational platform for an international Russian-speaking audience. It combines courses, practices, meditations, a member area, PWA and Telegram with administration and CRM tools. Design needs to maintain one identity while explaining what each person can do at every stage.

Organise the catalogue around participation

Courses, practices and meditations involve different ways of using content. KARMANUMBERS presents them as distinct material types. This helps visitors choose an experience suited to their time and interests before reading every product detail, rather than browsing an undifferentiated list of names.

Cards prioritise the name, material type, brief explanation and action. Full pages can add programmes, format and access conditions. Where duration or level information exists, present it consistently so visitors compare products using the same reference points and recognise what remains to be clarified.

Design the transition from presentation to membership

The project separates public information from material available after access is granted. Visitors explore the offer while signed-in users see their content. Design expresses that distinction through precise actions: viewing a course, requesting access and opening a lesson have different outcomes.

Draw the complete product journey: card, description, request or order, confirmation and member area. Every screen explains the next step. A receipt confirmation can describe pending review, while active access can lead directly to the available material.

In a design test, follow someone starting on a phone and later returning through Telegram. They should recognise the product and its state. Consistent titles, images and action names reduce the need to relearn the interface at each entry point and reinforce one coherent platform.

Build an atmosphere suited to reading

Visual identity can use colour, imagery and symbols while keeping the main text legible. Choose a limited scale of headings and paragraphs. Spacing shows which elements belong together and where a new idea starts, providing orientation throughout longer content.

Check contrast against actual backgrounds and text width on phones. Decorative headings can support atmosphere while explanations need familiar, clear letterforms. Reserve strong visual emphasis for important actions so navigation remains recognisable across long pages and different sections.

For spiritual material, identify its educational or interpretative nature. Numerology can be explained as a symbolic practice without scientific guarantees about the future. A clear editorial boundary in the presentation, maintained consistently throughout the product, provides the necessary context.

Make access states visible and explainable

KARMANUMBERS includes access following payment or approval, including defined periods. The member area should express active, pending and expired states through text rather than colour alone. People need to understand what they can open and where to request clarification.

In a hypothetical example, a course is active while a separate practice awaits confirmation. Show each state beside the corresponding product and provide the appropriate action. If the period starts when access is granted, explain that moment; if another rule applies, display the exact condition.

The application checks permissions, including media access. Design explains restrictions and recovery while implementation applies the same rules. Test active access, expiry and a different account so messages describe the actual situation instead of a generic error without a next step.

Treat the player as a central product feature

Meditations and media are used repeatedly, so the player deserves as much attention as the homepage. Display the material name, playback controls and loading state. When chapters or lesson order exist, show the relationship beside the material so learners understand their current place.

Test one-handed use, enlarged text and returning from another application. Prepare explanations for weak connections and unavailable files. Learners should be able to resume or seek help while retaining the context of the material they were trying to open or continue.

Use PWA and Telegram for return visits

The PWA and Telegram mini app are documented entry points. They support repeated phone use: returning to the member area, catalogue or content. Preserve the same navigation logic and access conditions even when the surrounding application has different controls.

PWA installation varies by browser and operating system, as the web.dev guide explains. Offer it after a useful interaction. Check offline behaviour separately: MDN documentation describes mechanisms, but each material type needs its own decision about local saving and applicable conditions.

Design administration around team activities

The documented panel manages content, users, media and access, while the CRM follows enquiries and orders. Organise screens around reviewing a request, publishing material and granting permission. Tables support these tasks, but priority information should remain visible without searching through unnecessary columns.

Show the product, relevant person, state and consequence of a change. Access for a particular period should be easy to review before saving. History and roles let another colleague continue the work and reduce dependence on separate conversations that obscure why decisions were made.

Verify the product through roles and tasks

Test as a visitor, learner and administrator. Ask people to find a course, open appropriate material and resolve a request. Observe hesitation, then correct labels, order or states. Use actual content, including long Russian titles and narrow screens, rather than only tidy short examples.

Measure confirmed requests and access grants separately from clicks. Nonessential tracking requires consent, and account information remains protected. The design goal is a journey each role understands: visitors choose, learners use material and the team can explain and administer access.

Sources and documentation

Share

Your notes

Notes stay in this browser.