Earlier quoted context omitted.
It's a bit like asking which power company has pretty technicians.
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?
Hyperview – Native mobile apps, as easy as creating a website
71–80 of 150 posts
Re: Hyperview – Native mobile apps, as easy as creating a website
#72"Serve your app as XML" As someone who started his professional career in 2005: All the old is new again.
Re: Hyperview – Native mobile apps, as easy as creating a website
#73"Serve your app as XML" As someone who started his professional career in 2005: All the old is new again.
Re: Hyperview – Native mobile apps, as easy as creating a website
#74Earlier quoted context omitted.
Server components + RN + Expo.... Could it get any more pointlessly complicated?
Just because there are multiple technologies does not make it complicated per se. Indeed, something could evolve to a simpler model, which it seems RSC on RN is.
All these companies have given up on the gold rush long ago and are just slinging fancy shovels.
Re: Hyperview – Native mobile apps, as easy as creating a website
#75I have a reasonable amount of experience doing both, and my opinion is that development tools aren't really the problem. The biggest pain point is the platform specific deployment and maintenance requirements (including legal and technical documentation) that will be needed regardless of what technology you use to actually build the product. Because of this I always advise clients that they don't really need a mobile app. Just build it on the web.
If you absolutely must have a mobile app, you need to fully commit and hire an internal development team and be prepared to keep paying them as long as the app is going to be in use.
Re: Hyperview – Native mobile apps, as easy as creating a website
#76Earlier quoted context omitted.
It's not like you can choose in the West either, either :). Number one goal of any software service today is to make its offering exclusive in some way - exclusive content, exclusive deals, exclusive integrations, exclusive set of participants (network effects), going super-broad super fast because infinite VC money lets you keep operating at a loss indefinitely, etc.
You're making it sound as if the difference in choice between China and western countries is negligible. Surely that's not the case? If every VC company tries to pull you into their walled garden, I can still choose from among a variety of said walled gardens. I could be wrong of course, since I don't know how many AliPay and WeChat competitors there are.
Re: Hyperview – Native mobile apps, as easy as creating a website
#77Re: Hyperview – Native mobile apps, as easy as creating a website
#78Earlier quoted context omitted.
And XML is essentially lobotomized and extra verbose Lisp S-expressions, going back to the 1960’s
don't talk about my thesis, written in LaTeX, like that... /j
PS won on human readability and editability but lost on portability to Adobe's own internal competitor, PDF, and because it fought and lost to (La)TeX -> PDF & (La)TeX -> DVI -> PS.
PS: I once printed out and bound the PDF 1.3 spec[0] on 24 lbs. bleached dead trees on an HP LaserJet IIIP with over a million page count. Some of the nuclear engineers and scientists an office containing every week.
0. https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandard...
Re: Hyperview – Native mobile apps, as easy as creating a website
#79Re: Hyperview – Native mobile apps, as easy as creating a website
#80This strikes me as odd - I have a much easier time making a well-functioning native app (iOS or Android) than the equivalent website. That's not typically a checkmark in the web column for web vs app pros and cons.
Unless we're including distribution when we say "creating".