Laura

Big hiya to any makers who build in public. How often do you update your early adopters on your product development? What kinda things do you share with them? What goes down well?

So much energy goes into getting people to find and download your app... ... but there's so little discussion about how you encourage - or even measure - a user's SECOND visit but it's just as important as the first. Do you have any advice on how to manage this critical interaction? For instance, with an app these days, if you ask for Push Notification permissions or even email notifications too early it can really put people off... but without it, it's all too easy for people to forget your app (wasting all of the acquisition cost and effort). What's the best way you've to make a user remember your app, 24h after they've installed it?

Being open about business is quite a new kick for me... ([my background](https://blog.usejournal.com/clos...) didn't allow sharing). Now we're building in public we're; * Sharing our live MRR, MAU etc. * Sharing our webstats