121–130 of 150 posts
E.g. in the app store you click a button, send a request, receive the response which contains a xml-like structure describing the UI mutation to your action.
iTunes Login
We could not find a user with those credentials.
type stuff.
Earlier quoted context omitted.
this is just not true. even the worst offenders (looking at you, react-router) do not require to "rebuild and relearn everything". What an unnecessary hyperbole.
Maybe not React itself, but the ecosystem as a whole. I can list some of these changes that generated a lot of work from memory: - the move from in-browser JSX compilation to build tools / webpack - the move from class components to functional components and hooks - all the changes related to ES6 classes and modules + build system - server-side components - Flux -> Redux - Redux -> MobX -> Relay -> Redux Toolkit -> C…
Earlier quoted context omitted.
We're in a thread talking about a technology that purports to make creating "native mobile apps, as easy as creating a website"; and the parent claimed that the Alipay/WeChats mini-app stacks are similar. I don't think asking for examples of this resulting in an experience that's pleasant is unreasonable?
I think the point OP is making is that the relative pleasantry of the experience isn't as important for end users as it is for us developers. My anecdotal experience bears that out: I shudder when I see a web-heavy native app, my non-tech friends don't bat an eyelid. People learn UIs, no matter how janky, very quickly if the end goal is important to them.
For practical purposes like buying stuff or accessing information I want practical applications that can be quickly iterated on.
I overlooked it at first even though it’s right there on the landing page but this is ultimately still React Native with all the baggage that entails.
I briefly investigated using React Native on a project. Obscure installation and linking process which no one seems to understand exactly, no SPM support on iOS, incomplete documentation that from the start pushes to adopt yet another layer on top (such as Expo, and I suppose Hyperview is now another option)… It felt like I am adopting some rusty legacy software, and not in a good way (more full of quirks than mature…
That said, RN was a win in the long run. It was a lot less baffling than the notorious Xcode/Swift/ObjC/UIKit ecosystem I'd used for years.
As a reverse-engineer tinkering with iOS this reminded me of some system apps. E.g. in the app store you click a button, send a request, receive the response which contains a xml-like structure describing the UI mutation to your action. iTunes Login We could not find a user with those credentials. type stuff.
Earlier quoted context omitted.
What does this mean? There are plenty of big, native apps using React.
It's "native" in that the wrapper is a native binary, but it's still a webpage.
Earlier quoted context omitted.
Is there a super simple tool for turning statically served websites into PWAs? Last time I looked all of the simple tools had been deprecated in favour of complex tools that do way more than I need. If I had a site in a directory that works fine from >cd MyWebApp >python3 -m http.server I would like a command line tool That worked like >becomepwa MyWebApp Which produced a PWA that downloaded everything on install and…
Three things you need: * Manifest file * HTTPS - for localhost I dont remember the workaround, browsers have made this increasingly more complicated from recent experiences * Service Worker - This is where I said I had maybe 60 lines of JavaScript. If you have these three things, a browser should pick up that your sites a PWA and server running it should be irrelevant... So you MUST have a minimal amount of JavaScrip…
I want the manifest to be automatically generated from whatever is in the directory. The service worker should download everything from the manifest at first launch. I'm ok with a download-on-demand build option, but by default it should grab everything needed. If a user installs something, it should be assumed that they can use it offline.
I feel like the tool should already exist. If it does not yet exist, it seems like there must be a reason for that that I am not aware of.
Earlier quoted context omitted.
It's "native" in that the wrapper is a native binary, but it's still a webpage.
React Native actually constructs a view hierarchy in the platform's UI toolkit, so I'm curious what you mean by "still a webpage"?
Earlier quoted context omitted.
There aren't any, with hyperview you actually own the hypermedia client as well as the server and you can write and cache local data in the form of custom extensions you make to it. I think that needs better documentation though.
So, basically it's like every other non-native development environment for mobile: basically useless when you want to use any feature of the phone. These things always implement the easiest bit of mobile development (the UI) and then make everything else harder, so it's useless for anything non-trivial.
Earlier quoted context omitted.
It's "native" in that the wrapper is a native binary, but it's still a webpage.
React Native actually constructs a view hierarchy in the platform's UI toolkit, so I'm curious what you mean by "still a webpage"?