Content
@
1 reply
0 recast
2 reactions
βwoj γ
@woj.eth
this sales shit is easy
33 replies
19 recasts
98 reactions
Seb π©
@sebastian2.eth
When can we get app I'm concerned about the performance of web on .mobile
1 reply
0 recast
1 reaction
βwoj γ
@woj.eth
working on it
2 replies
0 recast
2 reactions
β j4ck π₯Ά icebreaker.xyz β
@j4ck.eth
will you be using https://capacitorjs.com/ ? π
1 reply
0 recast
0 reaction
βwoj γ
@woj.eth
yoooooooooooo didn't even know about it but looks interesting are you using it?
1 reply
0 recast
0 reaction
β j4ck π₯Ά icebreaker.xyz β
@j4ck.eth
weβve been considering it not using it yet lmk if you do end up using it cc @web3pm @tayyab
1 reply
0 recast
1 reaction
βwoj γ
@woj.eth
lmao "you first" energy
1 reply
0 recast
2 reactions
β j4ck π₯Ά icebreaker.xyz β
@j4ck.eth
hey man iβm the designer lol i want it all β resource constraints are real π
2 replies
0 recast
2 reactions
β j4ck π₯Ά icebreaker.xyz β
@j4ck.eth
preaching to the choir here i know π
0 reply
0 recast
2 reactions
Dan | Icebreaker
@web3pm
Yeah frustrating bc we know an icebreaker app will look and feel so great Will boost retention, UX, and let us offer some features like haptics, push notifs, app deep linking, and low/no connectivity functionality But it will slow us down and wonβt give us PMF For that, icebreaker must function as the super tool for aggregating and intelligently traversing all your networks It should be so useful you still use it despite a slightly bad UX An app will be required to scale post PMF, but not before This is our current thinking.* *The exception is if @tayyab can get it working using capacitor this week in <2 hours with minimal code changes
0 reply
0 recast
1 reaction
