Skip to main content

Persona: Youth Pastor Jake — Mobile First

non-critical   Property: ChurchWiseAI   Category: UI / Visual Tier: starter Persona: youth-pastor-jake-mobile Touchpoint: mobile app/site, chatbot widget, voice setup

Preconditions

  • Visitor is youth pastor (20s-30s, tech-native)
  • Always on mobile, configures products from phone/tablet
  • Youth ministry uses WhatsApp/text-based communication

Steps

#ActionExpected Result
1Access homepage on mobile phoneMobile layout loads fast (<3s). Navigation responsive. No sideways scroll needed.
2Navigate to pricing on mobilePricing tiers stack vertically. Prices legible without zooming. 'Get Started' buttons touchable (>44px).
3Start signup flow on mobileSignup form mobile-optimized. No tiny input fields. Keyboard doesn't hide form. One-step flow if possible.
4Configure chatbot from mobileAdmin dashboard responsive. Settings accessible on portrait mode. No desktop-only controls.
5View chatbot preview on mobileLive preview of widget shows how it looks on mobile. Responsive iframe preview.
6Access support on mobileSupport contact clickable. Email/phone buttons use mobile-native handlers (tel: and mailto:).
7Test chatbot widget from mobileChatbot widget loads on mobile browsers. Message input accessible. Keyboard dismiss works.
8Check voice setup on mobilePhone number setup/testing accessible on mobile. QR code for easy reference if needed.
9View analytics on mobileDashboard charts/metrics readable on small screens. Pinch-to-zoom works. Not data-table-heavy.
10Read FAQ on mobileText readable without zooming. Links easy to tap. No pop-ups blocking content.

Known Failure Modes

  • Homepage not mobile responsive — Jake bounces
  • Admin dashboard freezes or lags on mobile — Jake can't work from phone
  • Signup form has tiny inputs — Jake gives up
  • Chat widget doesn't work on mobile — can't test with youth
  • Analytics unreadable on small screen — Jake can't check usage

References

Notes

Jake is mobile-first user (age 25-35, always on phone). Tech-native but doesn't have desktop nearby. Needs: fast mobile loading, responsive layouts, touchable buttons, mobile keyboard handling, live preview on mobile. Desktop-centric design will make Jake abandon the product mid-setup. Test on real phone, not browser DevTools.