
Your city, your story—report issues in a tap with InCity.
‘25
Mobile UX
Capstone Project
The Future of Community Based Compliance
A mobile-first reporting platform that modernizes non-emergency city service requests for Atlanta residents. InCity streamlines how people submit geotagged reports, track progress, and receive real-time city updates. Promoting transparency and community involvement.
Role / Context
Lead UX Designer
Lead UI Animator
Researcher/Personas
Prototyping/Wireframing
My Team

Wineury Almonte (Me)

Anderson Fisher (Team Lead)




+ 4 Team Members
Tools

Figma
Designing Layouts/Flows

Adobe Illustrator
Creating vector assets

Adobe After Effects
Animation
Leveraged Skills
Prototyping
Crafting interactive experiences
Motion Design
Animating micro-interactions
Accessibility
Inclusive, compliant design
Your city, your story—report issues in a tap with InCity.
‘25
Mobile UX
Capstone Project
The Future of Community Based Compliance
A mobile-first reporting platform that modernizes non-emergency city service requests for Atlanta residents. InCity streamlines how people submit geotagged reports, track progress, and receive real-time city updates. Promoting transparency and community involvement.
Role / Context
Lead UX Designer
Lead UI Animator
Researcher/Personas
Prototyping/Wireframing
My Team

Wineury Almonte
(Me)

Anderson Fisher
(Team Lead)




+ 4 Team Members
Tools

Figma
Designing Layouts/Flows

Adobe Illustrator
Creating vector assets

Adobe After Effects
Animation
Leveraged Skills
Prototyping
Crafting interactive experiences
Motion Design
Animating micro-interactions
Accessibility
Inclusive, compliant design
Problem
What's the issue?
The desktop-focused ATL311 hid crucial information behind tiny menus, causing frustration for residents who wanted clear, timely feedback.
Many users reported abandoning mobile submissions when they never saw confirmation or updates.
How might we transform ATL311 into a thumb-friendly, transparent mobile experience?
Problem
What's the issue?
The desktop-focused ATL311 hid crucial information behind tiny menus, causing frustration for residents who wanted clear, timely feedback.
Many users reported abandoning mobile submissions when they never saw confirmation or updates.
How might we transform ATL311 into a thumb-friendly, transparent mobile experience?

Desktop-first Design
ATL311’s desktop-centric interface burdens mobile users with tiny controls and hidden menus.
Buried Workflows
Critical reporting paths are scattered across multiple taps, forcing users through eight steps to submit.
Opaque Status Updates
Without real-time feedback, residents remain in the dark about the progress of their cases.
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
1 of 5
Research
Interviews
We kicked off the project by speaking with four Atlanta residents and consulting two city officials—including Marty Hughes, Assistant City Manager of Kennesaw—to understand how individuals and administrators currently or how they would like to experience ATL311 on mobile.
2 of 5
Research
Competitive Audit
Alongside these conversations, we performed a competitive audit of peer-city reporting platforms (like NYC311, Austin311, and CHI311) to identify best practices and recurring usability challenges.
3 of 5
Lit Review and Competitive Audit to research the context of our product domain
4 of 5
Research
Interview Summary
Interviewees still rely on local news and TV for city updates, so reliable push alerts for weather, traffic, and events are essential. Digital payments for utilities and fines worked half the time, workflows such as Medicaid applications and permit payments continued to demand in-person visits.
Finally, privacy concerns—particularly among older users—underscored the need for secure, transparent processes. These insights directly shaped our core features: an inclusive UI, streamlined report flows, customizable alerts, and robust security measures.
5 of 5
Research
Personas
These cards represent our core user archetypes whose unique needs and workflows informed every design decision.
Hover
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Tiny Controls and Hidden menus
Lack of real-time feedback
Lack of real-time feedback
ABOUT ALEX
Alex
27
Web Developer
PERSONA
Summary
Alex lives in Kennesaw, GA, and uses her smartphone for traffic alerts, event planning, and daily tasks. He expects a two-tap report flow, instant confirmation, and a high-contrast interface with engaging micro-interactions.
Pain Points
Lack of real-time feedback
Manual routing & misdirected requests
Inbox overload
Blake
49
Parks & Rec Adm.
PERSONA
Takeaways
Takeaways
Icon‑Driven CTAs
Consistent icons enhance learnability and minimize errors.
Granular Notifications
Daily, weekly, or event-based alerts let users tailor their updates.
Front‑loaded Map
Immediate geospatial context boosts discovery and engagement.
Unified Report Flow
Combining category & description slashes submission taps from eight to two.

More - Wireframe

Submit a Case - Wireframe

Home - Wireframe
Ideation & Wireframes
Low Fidelity Wireframes

More - Wireframe

Submit a Case - Wireframe

Home - Wireframe
Ideation & Wireframes
Low Fidelity Wireframes


High Fidelity & Motion
Meet InCity


High Fidelity & Motion
Meet InCity
4× fewer taps
Streamlined flow cut user effort by 75% (8 → 2)
75% faster submissions
Reduced wait time boosted user confidence (~40 s → ~10 s)
Decreased error rate
Fewer mistakes led to smoother reporting ↓ (30% → < 5%)
Prototype & Testing
Metrics After
Prototype Testing
4× fewer taps
Streamlined flow cut user effort by 75% (8 → 2)
75% faster submissions
Reduced wait time boosted user confidence (~40 s → ~10 s)
Decreased error rate
Fewer mistakes led to smoother reporting ↓ (30% → < 5%)
Prototype & Testing
Metrics After
Prototype Testing
Impact & Next Steps
Impact & Next Steps
What's Next?
Offline reporting
Allows users to file reports without connectivity, syncing automatically when online.
Community badges
Rewards citizens for active participation, encouraging repeat engagement.
Advanced filters
Lets users drill into cases that matter most, improving search efficiency.
Auto-escalation rules
Automatically alerts administrators when reports stagnate, ensuring timely resolutions.
Please Open in Desktop View