Post by @bradorbradley • Hey

@davidev.lens and I have the same argument every week where I state “Lens is for creators!”, and he says back louder “Lens is for developers!” Of course,

Stats

Comments

Communities seem to have the weakest support in the current Lens landscape. IMO, 2 things need to be built: Scoped delegation (dispatchers as contracts, but users can log into a profile with limited abilities via the contract) Subhandles (subdomains where brands can have separate types of content, but keep the trust of the main handle instead of polluting the namespace)
Working on a companion app for Lens to tackle some of those challenges. Performance: Metrics and KPIs (engagement, following, revenues). Audience: CRM-like following management. Content: Metadata and KPIs per publication. Insights: Comparison between accounts and insights regarding what's working for top accounts. What do you think? Sharing the landing page with a waitlist this week. Auth working properly, working on main layout and profile fetching. I should have an MVP by the end of the week :)
Such an interesting ecosystem. Feels like everything is balanced toward everyone's desires in the social graph, creating incentives for each shift in demand in the graph. Love it
Amazing food for thought! Thanks Bradley
to the moon
LFG
A product which tells creators what type of media types and sub content categories are performing the best across different lens app. Devs assemble!
soon
It's coming.
cool
So early.
1122
nice