4 ms·
Yeah I can’t find a reason why but I’m put off and uneasy reading all this for some reason . Also the detail in this “how we built the app” article is basically
by jama211 11mo ago
Yeah I can’t find a reason why but I’m put off and uneasy reading all this for some reason . Also the detail in this “how we built the app” article is basically… too detailed? Like a new developer who comments every line of logic in their code. Perhaps it was also generated with AI with a prompt that was looking at the codebase?
I wish them all the best but perhaps this just isn’t for me.
- MaxLeiter 11mo agoA lot of react native apps do not feel native. Even more are just low quality. Many v0 users were asking us how exactly we did X or Y to make it feel so good, which is what this post is for.
- jama211 11mo agoOk, well good luck
- tennex 11mo agoI like it. This post is the perfect level of detail for people obsessed about UX minutiae. Personally, I'm not a huge Vercel fan (IMO: lots of hype, business model encourages developer ecosystem lock-in), but this post gave me more trust in the design/UX care that goes into their products (which is a core Vercel strength).
- MaxLeiter 11mo agoI am obviously bias as a Vercel employee, but I think we actually do a lot to avoid locking our users in. You can read more about our approach here: https://vercel.com/blog/vercel-the-anti-vendor-lock-in-cloud https://vercel.com/blog/vercel-the-anti-vendor-lock-in-cloud If that doesn't alleviate your concerns or you disagree, I'd love to hear your thoughts about how we can improve
- tacker2000 11mo agoAre you serious? Your whole business model is built on locking in users and then selling them expensive hosting.
- MaxLeiter 11mo agoIf you can point out how we actually lock you in, that would be more constructive than blanket accusations. I recommend reading the linked post
- davidsainez 11mo agoI find the existence of opennext convincing proof of lock-in: https://blog.logrocket.com/opennext-next-js-portability/ https://blog.logrocket.com/opennext-next-js-portability/ Personally, I don’t bother with nextjs at all.
- MaxLeiter 11mo agoI think the fact that OpenNext can exist speaks to the opposite A Next.js project can be deployed to a Docker image very easily [1]. If you want to use a provider that has their own infrastructure setup, then yes you need to do some work (that OpenNext does for you). But that's true of practically any framework deploying to a host that does more than just serve the docker container. [1]: https://nextjs.org/docs/app/getting-started/deploying https://nextjs.org/docs/app/getting-started/deploying
- tacker2000 11mo agoNo sorry, I'm not going to read your PR fluff. You might want to look at the comments in this thread [1], to get a feeling of the "accusations", as you want to call it... I'm not "accusing" anything, I really couldn't care less, I don't use Vercel/Next.js and never will, but maybe you should read the linked thread, too see how people (at least on HN) see your company. [1] https://news.ycombinator.com/item?id=45099922 https://news.ycombinator.com/item?id=45099922
- 11mo ago
- satvikpendem 11mo agoLooks good, I appreciate the level of detail especially as bad UX can cause churn on mobile. Since it's React Native, are there plans for an Android version? I guess you guys wanted to get an iOS version out first instead of releasing both in parallel, for bug testing, improvements etc?
- fernandorojo 11mo agoOverall, our focus right now is iOS, but we want to do Android at some point. Even though we used React Native, we also wrote a good amount of native Swift code under the hood to power native modules.