Stepli

Note: This analysis is based entirely on the self-reported description provided by the author. No external verification, revenue data, customer names, or traction metrics are available.

The description states that Stepli is a bilingual Android accessibility companion that helps users complete unfamiliar tasks in other apps, one calm step at a time.

It supports:

• Task guidance across multiple apps (e.g., Foodpanda, Instagram, WhatsApp, YouTube)
• Creation of user-generated guides
• Visual instruction cards overlaid on top of target apps
• Voice support and manual confirmation features
• Control remains with the user; no automation or data input

The system uses:

• React Native for UI/UX
• Kotlin for Android accessibility services
• Android accessibility tools for screen interaction
• Data-driven guide structure to enable easy expansion

Inference: The product is not an LLM-powered assistant but a manual, structured step-by-step tool.

The author positions Stepli as:

• A personal AI guide for navigating technology with confidence.
• An accessibility tool tailored to people with low digital literacy and confidence.
• A non-automated teaching aid, not an automation platform.

It is described as:

• Designed for older adults in Pakistan, where literacy and digital access vary significantly by gender and region.
• Built to support both English and Urdu users.
• Intentionally calm and beginner-friendly in interface design.

Claim: Stepli aims to empower users to learn how to use apps independently rather than relying on others.

Inference: The positioning reflects a focus on inclusion, dignity, and trust in digital interaction.

The description identifies:

• Primary audience: Older adults (especially mothers or caregivers) who struggle with smartphone usage.
• Geographic focus: Pakistan, where literacy and access disparities exist.
• Demographic characteristics:
  • Low digital confidence
  • Limited English proficiency
  • Preference for visual and voice-based instruction

Inference: The ICP is defined by language, age, and digital comfort level, not by business or enterprise use cases.

Not evidenced.

The description does not mention:

• Any pricing model
• Revenue streams
• Monetization strategy
• Paid features or subscriptions

Absence of evidence: There is no indication of a commercial structure beyond the author’s personal development effort.

The project uses:

• React Native for app logic and UI
• Kotlin for Android accessibility service
• Android Accessibility Tools to monitor screen elements
• WindowManager for floating overlay functionality
• Voice support in both English and Urdu (with fallbacks)
• A data-driven guide system, allowing new guides without rebuilding the app

Key technical features include:

• Visual highlighting that does not block user interaction
• Manual confirmation steps
• Support for multiple UI matchers to handle app variations
• Read-only access, no data input or automation

Inference: The architecture is modular and scalable, supporting future expansion with new apps or languages.

Not evidenced.

The description does not provide:

• Any user base or adoption metrics
• Customer feedback or testimonials
• Usage statistics or retention data
• Product roadmap or release history

Absence of evidence: No signs of traction, growth, or market validation beyond the author’s own development and testing.

Not evidenced.

The description does not:

• Name competitors
• Describe existing solutions in the accessibility space
• Compare Stepli to similar tools or platforms

Absence of evidence: No competitive positioning or landscape analysis is included.

1. No commercial traction or user data – The product exists only as a prototype.
2. Single-person team – Limited capacity for scaling, marketing, or product iteration.
3. Self-reported impact claims – No independent validation of effectiveness with target users.
4. No monetization strategy – Unclear path to sustainability or revenue generation.
5. Limited technical depth in LLM integration – Original vision involved AI but was not implemented due to API constraints.
6. Language-specific challenges – Urdu voice support may be inconsistent across devices.

Inference: The project is a proof-of-concept with potential, but lacks commercial viability or scalability indicators.

1. Have you tested the app with real users from your target demographic in Pakistan?
2. What specific feedback have you received from those users?
3. Are there plans to expand beyond Urdu and English, and how would that affect development?
4. How do you plan to validate or measure success once launched?
5. Is there any intention to partner with NGOs, government bodies, or digital literacy organizations in Pakistan?
6. What are the technical limitations of the current data-driven approach, and how will they be addressed?
7. Do you have access to OpenAI API keys or other LLM resources for future development?