Arena 360
A simplified mobile UX case study for a government-affairs app that helps users search legislation, review resources, prepare meetings, report assets, and support phone outreach in the field.
Product
Mobile App
Arena 360 is presented here as a phone-first government-affairs application.
Role
UX Design
Mobile flow structure, lo-fi wireframes, and simplified product storytelling.
Focus
Field Use
Search, meetings, asset reporting, resources, and communication support.
A Field App For Government-Affairs Work.
Arena 360 is framed here as a mobile application. The page now focuses on the phone experience only, keeping the story simple and centered on what users need while away from their desks.
The app needed to make dense civic context feel reachable on a phone.
The design story is intentionally reduced to a few practical mobile tasks: find the right information, understand the relationship context, take action, and record what happened.
Legislator and legislation lookup
Mobile asset reporting
Meeting history and scheduling
Phone bank communication
The Main Flows Were Kept Short And Action-Oriented.
Instead of presenting a large feature inventory, the page now explains four core mobile flows that support the product’s purpose. Each flow is written as a concise UX responsibility rather than a full product specification.
Mobile asset reporting
District, state, municipal, PAC, committee, and client-footprint data needed to be condensed into a clear mobile reporting path.
Meeting preparation
Users needed quick access to legislator and staffer history before scheduling, attending, and recording meeting notes.
Phone bank communication
The app needed a simple structure for call lists, talking points, outcomes, and follow-up actions.
Search and resources
Legislator search, legislation search, open activities, and resource links had to stay easy to reach on a phone.
Rough Mobile Sketches Show The Thinking Without Overloading The Page.
The lo-fi section has been reduced to four mobile-focused artifacts. These sketches show how the experience could support reporting, meetings, phone outreach, and detail review before moving into the final app screens.
Lo-fi / mobile reporting
Asset Reporting Map
A rough phone layout for footprints, contribution context, and client data around a selected area.
Lo-fi / meeting workflow
Meeting Tool
A compact view for history, scheduling, notes, and follow-up after a legislator or staffer interaction.
Lo-fi / communication
Phone Bank Flow
A simplified calling experience that keeps the next contact, script, and result capture close together.
Lo-fi / detail screen
Mobile Detail View
A field-friendly detail view for contributions, committees, footprint tags, and quick activity logging.
The Final Artifact Shows Three Core Mobile States.
The supplied Arena 360 image is kept as the primary final artifact. The page no longer suggests desktop usage; the screenshots are presented only as mobile app screens.
Mobile screen / 01
Home
The home screen gives fast access to Legislator Search, Legislation Search, Open Activities, Resource Center, latest searches, and upcoming activity.
Mobile screen / 02
Bills List
The Bills List screen keeps search and filtering available for users who need to review legislation while mobile.
Mobile screen / 03
Resource Center
The Resource Center turns frequently used links into a lightweight support area inside the mobile app.
The Page Now Reads As A Simple Mobile App Case Study.
The revised version removes the heavier detail-oriented structure and keeps the story focused on mobile context, mobile flows, mobile sketches, and final mobile screens.
Mobile-only framing
All project language now describes Arena 360 as a phone-first app experience.
Simpler narrative
The case study moves faster, with fewer sections and more direct explanations.
Cleaner portfolio flow
The page still fits the portfolio style while avoiding unnecessary product depth.
Next