H2S11: How to wrap your WordPress-site into a cross-platform.native-app #

GoNative: Whether you choose to self-publish or have our team publish on your behalf you will need an Apple Developer Account and a Google Play Developer Account. You can apply for both accounts using the links below: Apple Developer Account: https://developer.apple.com/programs/enroll<$99>; Google Play Developer Account: https://play.google.com/apps/publish/signup<$25><80%, 10-8-22>

Hu: When Steve Jobs launched the iPhone app-store, along with the original iPhone, it was not part of his vision #, even, to open up publishing, to the community, and was forced, along, with the recommendation, from his high level technical advisors # He wanted a much smaller set of native apps, built by Apple, exclusively, consisting of staple tools like Notes, Health, iMessage, and News, while other applications, would live inside these apps.

H3S1: The fragmentation of software: 2007-’22:

Hu: The encephalitis<Hopkins a-r>: // add quote

H3S2: The rule of 8 in human depth progression:

Hu: The reason that, throughout history, chess players have been the best programmers, is due to their intuitive understanding of the rule of 8:

⭐ There is no limit to the amount of information, or complexity, that can be contained in a game of chess, or even a move, but this complexity, at no point, overloads our natural limits, because the board itself, is limited by the rule of 8. Analogously, human users will be overloaded, by UX–design, if there are more than 8 significant, interactive elements, on any one screen, or layer. Since iOS allows scrolling, even on the app.icon-screen, many people have upwards of 40 app icons on this layer, and are so overloaded, from this point, that they can hardly open their phone, without a significant | intentional blindness<MIC.ch-42>, that, practically, limits their view to maybe 3 apps, and so, they are less functional, than if 8. Since the intentional blindness occurred at a higher layer, the blindness will be propagated to lower layers, and even in Instagram, with its 3-wide grid, and the fact that only 3 things can be shown in the feed, and the profile has 3 elements, the mental-clog further limits, at every level of depth.

See how WeChat circumvents this issue in<WP.MIC-H2S12>.

H4S1: The rule of 8 in human facial geometry:

Hu: The human face is the oldest | chess board, in that it is capable of a representation of infinite | depth, of emotion, and yet, is structured, to perceived in stepwise–eighths:

H3S3: Tensile expansion by mis-formed expectations #n-p:

<x-ref LDS-Will 8/14/22>: Hu: The misplacement of many web services, such as Meetup, Facebook, and Google, which do not belong in any first | layer of an operating system, as a native | app, injected into the first | layer, has tensile-stretched these applications, via the demands, for instance, of the app.store-owner, who, in some resentment, of their very attempt at presence #, has placed upon it, the demands of a true.first–layer, to which it cannot conform, and therefore, has had to lie, both in terms of what it does, and in terms of what it reaches to do, and this has led to a significant decrease in health in the median health of the US-codebase<Turing>

H3S4: Minimizing language diversity<Babel!> by expanding the applicability of the PHP-layer<Turing>:

H3S5: Building internal.nested-integrations to large.scale-corporate,CMS:

H4S1: Laravel.wrap-as,embed:

Psycho.flim-intro<fcbno><fbno>: @Charlotte O’Connell:

• Back to the React Native vs PHP topic: React Native, as the name “Native” suggests, is still a native mobile app, and this deprives us from using the power of the web browser. Mozilla Firefox, for example, has been in development since 2002, so building an app in a browser, ie a “website”, this is very basic, is building on top of their platform, whereas if you were to build a native app, you’d have to build Mozilla Firefox, and the website. This is why Steve Jobs, in 2007, when the iPhone was first released, forbid people from building custom apps; all the app store would be populated by Apple, and everyone else builds websites. This was his initial vision, and only changed by his counsel later #
• 6:20 PM Modern web browsers have a ton of support for a wide variety of APIs, and many features out of the box. Using a browser, is analogous to using a programming language, in that you get to access much of its built-in functionality, and support. Take a look at the list of web APIs that Firefox supports by default, for instance: https://developer.mozilla.org/en-US/docs/Web/API None of these would be included, by default, in a native app, where you are also the browser, so even if you can get something super simple off the ground initially, at every step of the way, as your functionality gets more advanced, your development time will be 10-100x slower, optimistically, than just building a website. Web APIs | MDNdeveloper.mozilla.org • 1 min read
• 6:22 PM Therefore, the difference between using PHP/Laravel and React Native, which is already a bit more advanced than Swift, for the aforementioned reason of being able to build Android and iOS at the same time, is that with PHP/Laravel, you are simply wrapping your existing website, and giving users a shortcut to it, on their mobile homescreen. The app would still be downloaded from the App Store, in the workflow that users are used to. However, when they launch the app, it goes directly into the browser, ie Safari, and it simply locks the users, to only being able to access your website. However, we can hide the address bar, and keep users logged in via cookies, so it still “feels” like a mobile app, in its immersiveness, but functionality-wise, it would be much closer to using a website in your browser, than using a typical native mobile app.
• 6:26 PM By the way, when I say Laravel, I’m also referring to a framework, that is written in PHP. It’s PHP’s version of React Native, essentially. The difference is that PHP is already the standard for back-end programming, whereas JavaScript is not. JavaScript is designed to be, at most 10% of the code-lines in a web application, and handles certain, very specific, from my experience, browser-server interactions. It was never designed to be a full-on backend, or even front-end, for that matter, language. Probably for some historical reasons, like the fact that it contains the word “Java”, and it’s trendy to be taught at schools, there’s a bunch of computer-science “students” who maybe learned about a semester’s worth of CS, and now try to do everything with JavaScript.
• 6:29 PM In conclusion, when you build with PHP/Laravel, you get 1) a server, that is used, to launch a website, so now your functionality is also available on the web, and a desktop computer, using a browser, as well as from mobile browsers 2) the ability to create a shortcut, I call it a shortcut, but users will experience it as a mobile app, on both Android and iOS, where users can click it, save it anywhere on their homescreen, and launch a browser, that goes directly, and only to, that website. You will not have to build a separate front or back-end for the website and mobile app, and this also improves the experience for the user.
• 6:30 PM This, in terms of 1) development time, 2) scalability, and 3) resulting user experience, is objectively better, but it’s not as “trendy” as JS, although there are just as many real devs, which are rare, working on it, so there will be no lack of good documentation. You might not see as many 500k views videos on YouTube about it, but that’s hardly a metric for evaluating tech. Also, it’ll be around, at the same level of popularity, in 5 years, whereas these JS frameworks tend to come and go like the sand on the shore.

H5S1: Web-embed:

H5S2: Native.app-embed:

References:

https://www.hopkinsmedicine.org/health/conditions-and-diseases/encephalitis

https://www.redhat.com/sysadmin/bits-vs-bytes#:~:text=So%2C%20bits%20and%20bytes%20are,be%20either%200%20or%201.