DEV Community

Cover image for Discuss: What's the #1 headache in portfolio tracking today?
Abba From Pocket Portfolio for Pocket Portfolio

Posted on Edited on Originally published at pocketportfolio.app

Discuss: What's the #1 headache in portfolio tracking today?

Pick one (or add your own in comments):

  • Missing/slow prices
  • CSV hell (every broker is different)
  • Cluttered UIs that hide context
  • No mock-trading / scenario testing
  • Something else?

We'll take the top 2 and ship improvements next sprint — in the open.

Try the app: https://www.pocketportfolio.app/

Roadmap/issues: https://github.com/PocketPortfolio/Financialprofilenetwork

Join Discord: https://discord.gg/Ch9PpjRzwe to help prioritize (weekly votes).

Top comments (2)

Collapse
 
devsamikhan profile image
Sami Ullah Khan •

For me, it's definitely Cluttered UIs that hide context.

As a developer who often works on hardware-constrained machines, I’ve realized that 'bloated' interfaces don't just hide context—they eat up resources and kill the vibe. I’m a big fan of minimalist, mood-based UIs that focus on speed and clarity.

Also, CSV Hell is a close second! Automated API integrations are the way to go. Great to see this being built in the open!

Collapse
 
pocketportfolio profile image
Abba From Pocket Portfolio Pocket Portfolio •

Cluttered UI + context — that’s exactly why we pushed terminal-style density (totals + top holdings visible, not buried in cards). On CSV hell: we agree APIs are nicer when brokers provide them; our bet is an open MIT importer + client-side parse so you’re not waiting on a single aggregator. On constrained machines: aggregation and import run in-browser by design. If you’re up for it, we’d love a screenshot of what “too bloated” looks like on your setup — feeds directly into the next sprint.