3 ms·
Context: My small shop is in the market for mobile app creation, React Native is what we're using atm. I generally dislike signing up for on boarding when I ha
by notheguyouthink 9y ago
Context: My small shop is in the market for mobile app creation, React Native is what we're using atm.
I generally dislike signing up for on boarding when I have no idea how the app achieves it's goals. I browsed the home page with no clear idea on how it creates a native app from some web app. I did not want to go through on boarding (ie, email submission) when the homepage can't even explain how it achieves lofty claims.
Not trying to be harsh, just giving my honest opinion. I called it lofty, because it sounds like you make it easy to convert a web page into a native app. That is.. insanely challenging. I suspect you're using the term "native" very loosely here, and just wrapping my web app with a iOS/etc installer, which is not interesting to me at all.. and quite disingenuous to me. When I hear Native, I want at least the UI components to be running in their native UI framework, providing great FPS and predictable platform specific UX. Because that is my idea of native (not unrealistic imo), it further exacerbates the issue of me feeling like the product is snake oil or trickery.
Again, not calling your product anything - just giving my honest feedback, and what I thought as I read the page.
Best of luck :)