Content pfp
Content
@
0 reply
20 recasts
20 reactions

Dan Romero pfp
Dan Romero
@dwr.eth
I’ll repeat this 1000 more times: consumer social apps in 2023 require a mobile-first experience. The last time desktop-first worked was in 2010.
36 replies
69 recasts
290 reactions

Backseats pfp
Backseats
@backseats
98% sure I’m pivoting everything this year from solidity + front end to solidity + mobile
1 reply
0 recast
3 reactions

Dan Romero pfp
Dan Romero
@dwr.eth
lfg
1 reply
0 recast
1 reaction

Backseats pfp
Backseats
@backseats
@nicholas’s great video really pushed me in that direction. Plus I miss swift and JavaScript sucks. Now that apple doesn’t seem to be a blocker anymore, back to Xcode
3 replies
1 recast
4 reactions

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
You could also go the react native route to stay Mobile first but get both Android and iOS + web in one
1 reply
0 recast
0 reaction

Backseats pfp
Backseats
@backseats
I don’t like build once run everywhere, esp on android it can perform differently on different phones depending on the sensors and radios you’re using
1 reply
0 recast
0 reaction

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
So you‘d build two native apps or focus on one?
1 reply
0 recast
0 reaction

Backseats pfp
Backseats
@backseats
Depends where in the product cycle I was. Likely start with iOS because of better security (Secure Enclave, Face ID, fewer devices, 1 manufacturer) then expand to android and have two native apps
1 reply
0 recast
0 reaction

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
sounds like the OG way of doing mobile apps before React Native, Flutter, .NET Maui (formerly Xamarin) back then us iOS peeps had everything first as long as we paid 0.79€ (yep remember these times) for exactly that one native app all devices reason teams then after PMF to android
1 reply
0 recast
0 reaction