Comment by foxfoxx
3 hours ago
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.
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.