Comment by waterproof
6 hours ago
Love the idea. Thoughts from a UI/UX point of view, on mobile:
* Focus on the policy stuff since that's your differentiator. Put it front and center, currently it's below the "trending news". Nobody needs another trending news feed. I'd cut it entirely.
* Make your differentiator hyper-obvious at a glance on the front page. Right now your above-the-fold is dominated by a wall of AI generated text. It should include a tagline for your site and visuals that people won't get elsewhere.
* Your UI screams "vibe coded" which does not build confidence. Look to other authoritative sites for visual cues - consider a serif for headlines, make your spacing more thoughtful and consistent, reduce or remove your border radius.
Thanks! I'll look into these UX/UI ideas. As for the news, it's front and center because I want Govbase to be a site/app people regularly visit and policy does move slow. Even when a bill is introduced it can take weeks for the actual text content of the bill to show up on congress.gov. Plus on weekends/recess the government doesn't move.
I am planning to bring out more of the impact highlights from the policies to see what's "trending" or what certain reps are working on but just plans for now.
In this case, I'd say only share news where you have some kind of structured regulatory stuff attached to it. Like sure, Trump started a war, that's noteworthy. Follow that up directly with a link out to structured tally of what reps have said, when was the last time a President did something similar, what are the relevant regulations, etc.
Rather than try to compete in the "current events" space you might have more success in more differentiated channels like having people subscribe to issues, subscribe to reps... News should be part of it but you should lead as much as possible with your differentiator. I bet you could sell enterprise level subscriptions for industry-relevant regulatory news.
Why chase engagement? If policy is slow-moving then people can visit weekly. Or make an RSS feed. Unless you're planning to go ad monetized or worse...
There's nuance between wanting to build something people use regularly vs "chasing engagement". Even if he decides to run this as a non-profit, individuals are more likely to donate to something they use regularly and institutions are more likely to fund something with active usage. I would assume that the costs to make all these LLM-API costs are not insignificant. I agree with the previous comment that the policy is the differentiator though and hopefully there's a way to drive usage without devolving into a just another news aggregator.
2 replies →