dom pfp
dom
@dhof
let's say you're building something that is likely a consumer thing one day but will be a developer thing for quite some time before that what is your rollout strategy?
18 replies
1 recast
1 reaction
Pete Horne pfp
Pete Horne
@horneps
My experience of that is that devs are a tough market that require you to focus on them and not the end goal. If it’s an innovative tool, use it to roll out milestones showing the path to the end for the end user. Devs are nowhere as thankful as consumer customers. They’re fickle and demanding and critical. Like me
0 reply
0 recast
0 reaction
fredwilson pfp
fredwilson
@fredwilson.eth
Get as many developers building on it as possible. Good things will follow.
1 reply
0 recast
1 reaction
Ben 🟪 pfp
Ben 🟪
@benersing
@perl growth strategy
0 reply
0 recast
0 reaction
Elie pfp
Elie
@elie
What are you building?
0 reply
0 recast
0 reaction
tani ↑ pfp
tani ↑
@tanishq
Aligning developer incentives: either Satisfaction (Mission alignment) or Reward (Monetary alignment)
0 reply
0 recast
0 reaction
Jordan Kutzer pfp
Jordan Kutzer
@jk
We are building a consumer game, but some of our earliest users are developers who want to build within our game. We didn’t expect this. Paying close attention to all comments here 🙏
0 reply
0 recast
0 reaction
markus - ethOS - e/acc-d pfp
markus - ethOS - e/acc-d
@markus
Make it as easy as possible for devs to play with it and understand the value behind it.
0 reply
0 recast
0 reaction
Brunny.eth pfp
Brunny.eth
@brunny
Build it for the devs, ‘sell’ to the devs
0 reply
0 recast
0 reaction
Joey Roth | Dyad pfp
Joey Roth | Dyad
@joeyroth
permissionlessly composable layers that are decentralization-optimized at the bottom and ux optimized towards the top
0 reply
0 recast
0 reaction
yandere pfp
yandere
@xx
hackathon; airdrop to OSS contributors; dev discord
0 reply
0 recast
0 reaction
Benjamin pfp
Benjamin
@benjamin
Focus on your dev community — at some point in time you’ll grow out of it, but let that be a natural pull, rather than a forced transition. We tried to fly too early at Pebble, and realized it a little too late. DM if you want to chat details.
0 reply
0 recast
0 reaction
Adam pfp
Adam
@admlj
build in public, bring consumers along for the ride
2 replies
0 recast
0 reaction
CS pfp
CS
@cs
Depends on if the expected evolution is more on the product or on society
0 reply
0 recast
0 reaction
Geoff pfp
Geoff
@geoff
Why are the devs building on it? There must be some end users somewhere or there wouldn’t be any devs. Focus there and grow.
0 reply
0 recast
0 reaction
rhys pfp
rhys
@rhys
Look at corps with large % of rev. from Disti’s (Adobe, Cisco, MSFT) and appropriate from their Channel Programs for your dev audience. Incentivise and reward. Map and re-map the engagement flywheel including any spinoffs that open up. Then work toward a “sell to, sell with, sell through” GTM model for consumer l
0 reply
0 recast
0 reaction
numan 🎩 pfp
numan 🎩
@numan
Tell people they have been chosen to try a life changing tool
0 reply
0 recast
0 reaction
maciek pfp
maciek
@maciek
My case actually 1. Build the first “toy” product to show what’s possible 2. Open API to spread the cost of infrastructure across many products 3. Develop the final end-user product which requires massive infrastructure
0 reply
0 recast
0 reaction
wutwut pfp
wutwut
@wutwut
Focus on devs, create exclusive invite only cohorts of super excited consumers to test the consumer side early one. Build consumer side in public with them
0 reply
0 recast
0 reaction