Chip Li李鸿铭

Gainesville, FL

What do people need before AI acts for them? · CiteBar · 2025–2026

Numbers you can trust at a glance

What does a researcher need before handing citation-watching to an app?

My role
Creator, designer, and sole maintainer (101 of 102 commits).
Method
The public issue tracker as a research channel, a review of seven App Store alternatives, and fast releases to test each change.
Key insight
Researchers want this year’s citations and the papers about to move their h-index, not just a total. Any number shown at a glance must never overstate.
Outcome
Three requested features shipped and closed with personal replies, in a design that keeps all data on the user’s Mac.
CiteBar Papers window with starred papers sorted by citations

Problem

Researchers refresh Google Scholar far too often

Citation counts matter for careers, so researchers check them compulsively. CiteBar puts the numbers in the macOS menu bar and notifies only when something changes. The design question: what does someone need to see so they can stop checking?

Feedback

One user, three requests, three releases

  • “Request for option to show current year’s cites rather than total”Shipped in v1.4.8: current-year citations can be the primary number in the menu bar.
  • “Ability to track a particular paper (rather than just a researcher)”The user wanted papers near the margin of affecting an h-index. Shipped in v1.6.1: a Papers window with starring, and progress toward the next h-index (for example 3/6).
  • “Trend count should show correct number of days since baseline”“+X in last 30 days” appeared even with less history. Fixed: new profiles now read “+X in last Y days” until a full window exists.
CiteBar menu bar panel with profiles, current-year citations, and trend labels
The menu bar panel: the number people check, with its time window spelled out.

Issue titles quoted as filed. Each was closed with a personal reply explaining how to use the change.

Try it

Why the honest label matters

Slide the amount of history a profile has, and compare the old label with the new one.

Before

1,204 +12 in last 30 days

Implies 0.4 a day. Overstates how long the trend has run.
After

1,204 +12 in last 4 days

3.0 a day. Says exactly what the data covers.

Principles

Small decisions that earn the hand-off

  • Notify on change onlyNo “nothing changed” alerts. Milestones at 10, 25, 50, 100 and beyond open a shareable card.
  • Be a good citizenRequests are spaced out and back off after errors. Profiles refresh daily by default, never more than every 12 hours.
  • Your data stays yoursStored locally, no accounts, no telemetry; export, import, and optional backup.
  • Explain every numberDay counts on every trend, markers on partial group totals, and explanations on hover.
A CiteBar milestone share card
Milestones open a shareable card instead of another notification.

Impact

Small product, complete loop

CiteBar is small: a few hundred direct downloads, plus people updating in place. Its value here is the loop: a stranger’s request, a reply, a release, and a closed issue.

85GitHub stars
21releases
3 of 3user requests shipped
if I ran it again

Most feedback came from one engaged user, so CiteBar risks being designed for him. Next I would add an opt-in, privacy-preserving way to learn which views people actually use, without breaking the no-telemetry promise.