DemandHunt Demand signals from global communities
EN
Productivity & PKM Stack Exchange · 2026-09-03

Database front-ends only offer one-line rows — useless for managing a song repertoire

数据库前端只给一行列表，曲库管理没法一眼『知道』自己会什么

At a glance · 30-second read
  • WhoStack Exchange · 2026-09-03 · 1 replies
  • The askDatabase front-ends only offer one-line rows — useless for managing a song repertoire
  • The openingA local database front-end with configurable multi-line rows, or a high-density list-view plugin for Airtable/Notion — for repertoires, libraries and collectibles.

What was actually said

“I play guitar at folk clubs and camps. The problem is 'knowing what you know'. Back in the 2000s I came up with a list view with 2 lines per entry in Access 97: title and key on the first line, lyric snippet on the second. Modern database front-ends only give one line.”

— Stack Exchange · 2026-09-03 · softwarerecs.stackexchange.com/questions/95563/datab…

Background and pain

The pain

Generic grid views are too dense: with multiple identifying fields you must open every record, which kills usability at a few hundred rows.

A buildable angle

The opening

A local database front-end with configurable multi-line rows, or a high-density list-view plugin for Airtable/Notion — for repertoires, libraries and collectibles.

How to validate it

  1. Read the whole thread and note the recurring scenarios — repetition is the density of the need.
  2. Search existing tools around "database gui / list view" and check which single step they actually cover.
  3. Put up a one-line landing page, share it back to Stack Exchange, and see whether anyone asks about pricing.

Existing options

AccessAirtable

From the thread · top comments

How about Google Spreadsheet or similar? A cell can have multi-line text. You can set your spreadsheet to be available offline (synchronized when there is Internet). Scrolling when you are busy on stage is OKish. The main problem will be that the keyboard might mistakenly pop up from time to time, and might inadvertently edit things. To solve this, you could have two accounts, one for editing on desktop and one read-only to view when on stage. Or save as PDF before the gig. Would any feature be missing? Disclaimer: I work at Google.

— Nicolas Raoul · ▲ 0
Open the source thread

More threads on this pain

Dev tools & infra (7)

Related opportunities

Open the source thread More in Productivity & PKM Back to library