Drooid Logo
Back to story perspectives

Full Breakdown

Prototype App to Log Bureaucratic Frustrations Takes Shape Using Claude Pro

5/19/2026, 11:52:49 AM

Core Development: Concept to Prototype

The author visited their mother’s home on a recent Sunday, opened a computer equipped with a Claude Pro subscription, and described a dashboard intended to record incidents of administrative burden. Claude responded with a preliminary interface, producing a functional prototype despite incomplete backend features.

Background and Motivation

Prior conversations with the author’s mother highlighted concerns about AI’s environmental, political, and economic implications. The author sought a concrete use case, targeting “burdensome administrative tasks, bureaucratic sludge, Kafka-esque unsubscribe mazes, byzantine insurance portals, wrongful charges, denied claims, [and] confusing membership plans.” The goal was to aggregate user-submitted data on time spent and annoyance levels, then generate contextual analysis and complaint letters.

Key Participants

  • The author – initiator of the prototype and primary user.
  • Claude Pro – the AI model that generated UI elements, contextual paragraphs, and draft letters.
  • Reddit forum contributors – provided technical advice referenced during development.
  • Harvard CS50, AWS, Kuberns – specific technologies mentioned as potential learning pathways.

Timeline of Development

1. Sunday visit – author opens Claude Pro and outlines the dashboard concept.

2. Claude’s initial response – AI offers a “fantastic idea” and asks clarifying questions.

3. Prototype emergence – a rudimentary “Log Incident” and “Dashboard” interface appears, though functional elements remain inactive.

4. Conclusion – author notes missing data persistence and the need to train Claude on broader context.

Current Functionality and Limitations

The prototype displays “Log Incident” and “Dashboard” tabs, but neither tab records entries. No storage mechanism exists, and Claude has not yet been taught to generate the broader contextual analysis promised in the design. These gaps limit the app’s immediate utility.

Potential Impact

If fully realized, the app could quantify collective time and emotional costs associated with administrative processes, provide users with personalized resistance quotes and uplifting images, and streamline the creation of complaint letters to regulatory bodies. Such data could illuminate systemic inefficiencies across sectors.

Criticism and Technical Barriers

Reddit-sourced advice underscores the technical steepness of the project: users may need to “learn how computers and code works first,” consider enrolling in “Harvard CS50,” or shift from “learning AWS or servers” to using “something like Kuberns.” These suggestions highlight the gap between the concept’s accessibility and the expertise required for implementation.

Verbatim Quotes

  • “I’d learn how computers and code works first.” — Reddit forum advice
  • “I’d look into going through harvards CS50.” — Reddit forum advice
  • “Instead of learning AWS or servers, use something like Kuberns.” — Reddit forum advice
  • “This is a fantastic idea—genuinely useful, with a clear mission and a great sense of humor about a real problem. Let me give you an honest lay of the land before we dive in.” — Claude, the AI model
  • “The “Log Incident” and “Dashboard” tabs didn’t work yet, we hadn’t arranged for the entries to be saved anywhere, and I still needed to teach Claude the wider context part.” — the article’s author

What’s Next

Future development will focus on implementing data persistence for logged incidents, activating the dashboard’s analytical features, and training Claude to produce the intended contextual narratives. Additional testing with user submissions is anticipated to refine the app’s usability and impact assessment.