Skip to content

Make Storyteller more accessible to non-technical users through demo content

Background

Currently, trying out Storyteller requires either:

  1. Setting up a server (requiring technical knowledge and computational resources)
  2. Manually importing pre-processed files into the mobile app

This creates a significant barrier for non-technical users who might be interested in the application but can't evaluate it easily.

User Story

Suppose there's a couple where the wife is a software engineer and the husband can't use a command line. If the husband reads about Storyteller, he has no way to try it out. And, not having enough information about it, it doesn't rise to the level of urgency/importance where he will bother his wife by asking if she can set up an instance.

Proposed Solution

Create a way for new users to try Storyteller without technical setup. This could be implemented in one of two ways:

Option A: Pre-processed Demo Files

  • Process a few public domain books (e.g., from Librivox/Standard Ebooks)
  • Make the processed files available for direct download
  • Users can import these into the Storyteller app directly
  • Example books could include:
    • "Psmith in the City" by P.G. Wodehouse
    • Other public domain works from Standard Ebooks/Librivox

Option B: Demo Server Instance

  • Set up a public Storyteller instance
  • Pre-load it with a few public domain books
  • Disable book upload functionality
  • Allow users to point their app at this instance
  • Could be hosted on a low-cost VPS

Current Status

  • This is considered a future enhancement
  • Current priority is lower as Storyteller is in beta
  • Higher technical barriers are currently accepted as the software sometimes breaks

Benefits

  1. Lower barrier to entry for non-technical users
  2. Allows immediate testing of the app's core functionality
  3. Better user evaluation process before committing to setup
  4. Pathway to making Storyteller more accessible to a broader audience

Technical Considerations

  • Demo content should use public domain works to avoid copyright issues
  • Processing of books is computationally intensive (CPU: >1 hour, or requires GPU)
  • Current beta status means some instability is expected

Next Steps

  • Decide between Option A (pre-processed files) vs Option B (demo server)
  • Select initial public domain books for demo content
  • Create implementation plan based on chosen approach

References