The app turns `marsharbel.com` into a focused native experience. Instead of asking people to bounce between pages, it gives them one calm home, one illustrated story path, and one practical Rosary companion they can return to every day.
What matters most is clarity: children can open the story like a real picture book, adults can move directly into the Rosary, and both paths stay connected to the same live media and prayer library already maintained on the website.
The story side is intentionally simple. One saint, one shelf card, one swipeable reading flow. That keeps the first experience understandable for children while leaving room to add more saints later as reusable books.
The Rosary flow is designed for people who want to begin praying quickly. The recommended mystery set is surfaced first, the prayer sequence is visible immediately, and each mystery opens into its own set of spiritual fruit, prompts, and guided audio.
This product works best when it feels intentional rather than overloaded. The home screen routes, the story screen invites reading, and the Rosary screen reduces decision fatigue.
The story artwork, narration, and Rosary audio stay aligned with the existing marsharbel.com media library.
The illustrated reading flow is easier to understand than a long saint biography page on mobile.
The Rosary opens with the practical next step instead of asking users to memorize schedules and structure.
The same structure can support additional saint stories and future prayer paths without redesigning the app.
The current docs and README use iPhone captures from the running app. The next media pass should mirror this exact sequence on Android so Play Store assets and docs stay visually consistent.
Capture home, story shelf, story reader, Rosary hub, and mystery set with the same narrative order.
Adapt the same core frames into App Store and Play Store aspect ratios instead of designing two different stories.
Use the same copy themes across README, docs, and future storefront metadata so positioning stays coherent.
Promote the capture flow into repeatable release tooling once Android screenshots join the asset set.