Internal product · Production validation
WholePath is a mobile-first self-improvement and reward app for Jehovah’s Witnesses. It brings spiritual goals, study, meetings, ministry, congregation assignments, privileges of service, family, health, work, and household responsibilities into one realistic plan—without treating app activity as a measure of spirituality.
Current implementation
Inside the product
The technical story is maintained alongside the product so architecture and design decisions remain understandable as the implementation evolves.
Conception
The product began with a study of flexible gamified planners—especially LifeUp—alongside gentler habit and goal systems. WholePath carries forward user-defined activities, points, rewards, focus, and visible progress, but establishes a strict boundary: the game describes engagement with a personal plan. It does not infer faith, worth, congregation standing, qualifications, or God’s view.
Experience design
The mobile-first interface combines JW-tailored activities with family, health, household, work, school, financial, and personal responsibilities. A rolling rhythm replaces fragile perfect streaks. One major life direction and up to three growth goals create focus, while a permanent Path Tower preserves reached goals instead of letting them disappear into an archive.
Architecture
WholePath is an Odoo 19 application with Python domain models and controllers, PostgreSQL persistence, a QWeb delivery shell, and a focused vanilla-JavaScript client. The model covers profiles, recurring and one-time activities, completions, rewards and redemptions, major and growth goals, connected goal steps, ministry sessions, return visits, follow-up interactions, and passwordless authentication records.
Domain engineering
Activities and goals share controlled aspect tags. A completion creates a goal step only when those aspects overlap, making ordinary actions legible as incremental progress toward a larger aim. The curated library spans spiritual goals, service and congregation responsibilities, relationships, hospitality, health, home, learning, and finances; custom goals use the same understandable tags.
Identity & privacy
Email magic links are single-use and stored as hashes. Remembered-device sessions use selector-and-validator tokens with hashed validators, secure cookie handling, explicit logout, and CSRF-protected changes. Personalization rules are enforced on the server as well as in the interface. Ministry and return-visit tools are positioned as private organizers, not congregation reporting systems.
Delivery
The current application is deployed behind Nginx with HTTPS, a dedicated Odoo website, installable manifest, service worker, responsive interaction patterns, and automated model and route checks. The web foundation is intentionally portable: validate the core interaction model first, then package it for native mobile distribution without rebuilding the product logic around a second source of truth.
Living roadmap
WholePath’s roadmap separates shipped foundations, present validation work, near-term product capabilities, and longer-horizon mobile and collaboration ideas. It is maintained as editable Odoo data so the public plan can change with the actual product.
Define the motivational model, JW-specific scope, whole-life balance, and guardrails against shame or spiritual scoring.
Compared LifeUp, Habitica, Finch, TickTick, Todoist, Amazing Marvin, and SuperBetter; translated the strongest patterns into autonomy, gentle recovery, meaningful rewards, connected goals, and progressive complexity.
Deliver the core phone experience, responsive views, installable manifest, service worker, and production HTTPS hosting.
Implemented the Today, Goals, Ministry, Rewards, activity library, Insights, More, Help, onboarding, and Developer views as a focused mobile application within Odoo.
Support email magic-link login and keep a trusted device signed in until explicit logout.
Shipped hashed single-use login tokens, selector-and-validator remembered sessions, secure cookies, expiry handling, CSRF protection, and account-scoped profiles.
Support recurring and one-time activities across spiritual and secular life, with user-controlled growth, tokens, rewards, and optional skip adjustments.
Includes daily, weekly, monthly, and one-time rhythms, repeat targets, durations, due dates, pause/archive behavior, a focus timer, rolling progress, and a personal reward shelf.
Connect everyday activity to one major direction and up to three growth goals, while preserving every genuinely reached goal.
Shipped a broad curated library, custom aspect-tag attachment, automatic connected steps, goal state management, reflections, history, and the visual Path Tower.
Provide useful personal service-time, session, Bible-study, and return-visit organization without becoming a congregation reporting tool.
Includes an elapsed-time service timer, manual sessions, monthly summaries, minimal return-visit records, next steps, follow-up history, and optional inclusion of follow-up minutes.
Use required first-run personalization to keep curated assignments and goals relevant while retaining shared spiritual, ministry, and secular content.
The server conservatively filters clearly male-only curated roles and matching task suggestions from female profiles while preserving custom goals, history, and shared congregation participation.
Make the product explain itself in plain language and expose shipped definitions for development review.
Shipped a searchable 52-article guide, contextual tooltips, automated help-coverage checks, and a read-only Developer View covering predefined goals, activities, rewards, penalties, areas, aspects, and limits.
Validate the daily loop, onboarding clarity, scoring defaults, goal connections, and mobile ergonomics with real use before expanding the surface area.
65%Current work should favor observed friction, data integrity, accessibility, performance, and clear product boundaries over adding novelty systems too early.
Harden the branded magic-link sender before broader distribution.
The existing Odoo transport can send mail, but the launch path needs WholePath-specific sender alignment, DKIM, SPF review, bounce visibility, and delivery monitoring without creating an unnecessary provider account.
Let users take a useful copy of their activities, goals, history, rewards, and ministry records with them.
Design a versioned, understandable export that supports user ownership and recovery while avoiding accidental exposure of sensitive return-visit information.
Add depth for assignments and routines that need preparation steps without cluttering the calm default experience.
Planned capabilities include reusable checklists, activity subtasks, optional if-then cues, reference links, attachments, and email reminders; push notifications wait for the native phase.
Connect chosen tasks and responsibilities to real schedules without turning calendar access into surveillance.
Explore explicit import/export and recurring-event sync, with user-controlled scopes, clear conflict behavior, and no hidden ingestion of unrelated calendar data.
Help users plan compassionately around capacity without medicalizing the product.
Any mood or energy check-in must be optional, use user-controlled retention, avoid diagnosis, and support adjusting the plan rather than judging the person.
Explore shared responsibilities and private encouragement without leaderboards, congregation comparisons, or group punishment.
Potential modes include an opt-in accountability partner and household responsibilities with explicit consent, granular sharing, easy revocation, and no authority or spirituality implications.
Port the validated interaction model to app stores while keeping one authoritative product backend.
The PWA establishes responsive flows first. Native wrappers can later add platform distribution, deeper offline handling, and opt-in push reminders without duplicating domain logic.
Consider custom achievements, level curves, crafting, and randomized rewards only after the core planning loop proves durable.
These LifeUp-inspired systems can reward deep customization, but they should remain optional and must not obscure the practical task and goal system.
Roadmap items are directional product goals, not release promises. Resolve Softworks updates their order, stage, and detail from the product’s Odoo management view.
Studio focus
Resolve Softworks is not currently accepting client work. Product development, production validation, and responsible long-term operation are the present focus.