Menu
← Back to contributions1 / 3

Product documentation · UX writing · Long-term project

Lapse

Independent Community & Documentation Project

I created an independent knowledge base around Lapse that translated product behavior, policies, and community questions into a clearer resource for non-technical users.

Contribution

Closer to the real product.

Created an independent knowledge base around Lapse to make product information easier for users to understand, navigate, and apply.

What I worked on

  • Organized product information around real user questions
  • Translated privacy and terms into clearer explanations
  • Documented product systems, social features, and account behavior
  • Built a readable information architecture for community resources
  • Balanced accuracy with approachable UX writing

Product work

Independent
product work.

Long-term use of Lapse grew into a product-facing contribution: community research, QA, bug reporting, private feature testing, trust & safety reporting, and direct feedback to the team.

Independent product contribution · not a formal employment role

The work was not one isolated submission. It grew from being an active user and community member into a repeatable feedback loop: notice a pattern, understand the conditions around it, document what happened, and send the team something they could act on.

That meant moving between everyday product use, community conversations, recorded reproductions, private test access, and direct conversations with the Lapse team. The strongest contribution was connecting those perspectives instead of treating each bug, request, or user report as a standalone message.

The loop

01Notice

Spot friction or a repeated behavior while using the product and listening to the community.

02Reproduce

Gather context, test the behavior, and capture a clear example when possible.

03Translate

Turn the raw observation into a concise product, UX, or trust-and-safety signal.

04Follow through

Stay in the loop with the team and watch whether the issue, feature, or experience changes.

  1. 01
    Community signalsOngoing

    Used recurring conversations—not just one-off complaints—to identify where people were getting stuck, what they were asking for, and which behaviors were creating friction. One example was escalating repeated “Vibes” begging around community posts so the team could investigate how people were bypassing existing filters.

  2. 02
    Product suggestionsJune 2024

    Shared a structured set of improvements based on conversations in the Lapse community: a camera timer/countdown, a return to a more navigable feed, group chats, and personal recaps. The timer/countdown and group-chat ideas were later added to the product.

  3. 03
    QA & reliabilityJuly 2024

    Documented a crash around opening chats after sending frequent Instants and included a video reproduction. The report gave the team a concrete path to investigate, and the issue was subsequently fixed.

  4. 04
    Private feature testingAugust 2024

    Was personally invited into the Lapse Camera video-testing program. I installed the test build, exercised the recording flow, and approached the feature as both a user and a QA tester—looking for confusing states, rough edges, and useful feedback before wider release.

  5. 05
    Critical bug reportingAugust 2024

    Found a Vibes reset exploit while troubleshooting an unrelated loading issue: deleting and reinstalling the app could restore two Vibes, a currency-like resource. I reported the reproduction path directly and explained why the behavior was exploitable, rather than treating it as a normal reset.

  6. 06
    Trust & safetyOctober 2024

    Flagged an account whose comments appeared to violate platform rules, while also reporting that the app could crash before the account could be reported in-app. The team confirmed the account had been shadow-banned and was investigating the reporting and enforcement gap.

  7. 07
    Internal product feedbackDecember 2024

    The Lapse team reached out about an internal competition concept built around group chats, prompts, a timer, submissions, voting, and a winner. I gave detailed feedback on creative freedom, presets for users who need inspiration, event use cases, and how the experience could stay fun for larger groups.

01

Field note

Documentation

I organized information about the Lapse experience into a structured resource rather than requiring users to piece information together across product pages, policies, community discussions, and support information.

The project involved understanding the product itself and translating that understanding into documentation that could be used by non-technical users.

02

Field note

Information Architecture

The documentation was organized around the questions a user would actually have rather than simply mirroring corporate documentation.

  • The core Lapse experience
  • Account functionality and social features
  • Privacy and community behavior
  • Platform availability
  • Frequently misunderstood product areas
03

Field note

Product Understanding

Building the resource required breaking the product into individual systems and understanding how those systems related to one another.

  • The disposable-camera-inspired capture experience
  • Journals and sharing
  • Social functionality and account systems
  • Platform availability
  • Privacy-related functionality