6 ms·
At rosaly.com we've built our "app" with something similar we didn't go the PWA way (because of app store), but something quite similar to the article 1. we h
by allan_s 5y ago
At rosaly.com we've built our "app" with something similar
we didn't go the PWA way (because of app store), but something quite similar to the article
1. we have a symfony website with simple web pages but with a "app look" (yes no react , no api, like it's the 2000s all over again)
2. we have a think react native wrapper (at first 17 lines, no it's 90s as we support push notification, hardware back button etc.) that embed a react-native webview
so we have nearly no javascript, just modern css and we pay really attention to performance and it's a dream
1. no javascript removes a lot of hassle
2. no api removes a lot of hassle too
3. html+css and we support all platforms, so a good design and backend engineers is all you need
we're live for a year, have raised money and have customers. We've been through several store update (to keep react native up to date and put some changelog).
I call it "retrogressive-app"
- nathancahill 5y agoIs that small react-native wrapper viewable somewhere? I'd love to do something similar.
- dorianmariefr 5y agoI can share you mine https://gist.github.com/dorianmariefr/e8422538a4eefcc99aa92d91b147be12 https://gist.github.com/dorianmariefr/e8422538a4eefcc99aa92d...
- andai 5y ago2021: Year of PHP in the pocket
- simonbarker87 5y agoSounds great, shame I only speak English so can’t have a proper play with it but this approach sounds delightful. I’ve recently started a project with just html/css and vanilla JS on the front end - no react etc and it’s very nice
- geoka9 5y agoThank you for your post! I'd love to read more about your stack, so of you do a blog post, please let us know :) Would love to see a video of your app in action, too!
- judge2020 5y ago" we pay really attention to performance and it's a dream" Does this include in low-connectivity environments? The biggest advantage of api-driven PWAs is that it supports no-connectivity and low-connectivity nicely, assuming you put effort into enabling it (having an offline cache of data) and having loading indicators visible to the user. With a regular page-load-driven application, if i'm on 1 bar of 4G I might get the TTFB for a page load and then be waiting as page assets slowly load in, staring at a white or half-blank screen the entire time.
- new_stranger 5y agoIronically though, phones usually struggle more with single-page apps / Javascript heavy sites which have all the client-side application logic, 3rd party libraries, and DOM re-renders based on state changes.
- allan_s 5y agoexactly ! most browser will wait for the next to load before unloading the current one so with a little css trick you can do a nice transition between pages While most SPA will put you on a weird state (of course you can handle it nicely too, but it requires effort for something you had for free in the first)
- allan_s 5y agowe certainly can sure improve on that side but currently most of our pages are at most 2 https call 1. html of that page, they never go over 30kb non gzipped, most svg assets are inline, so once you got it, you got it. 2. the tailwind.css file, that is cached after the first page. so even if you feel fancy and you use graphql, you can't do less 1 http call right ?
- bestinterest 5y agoSounds like the conclusion Basecamp came to for their apps. https://m.signalvnoise.com/basecamp-3-for-ios-hybrid-architecture/ https://m.signalvnoise.com/basecamp-3-for-ios-hybrid-archite... Also see https://twitter.com/dhh/status/1254870450464686080?lang=en https://twitter.com/dhh/status/1254870450464686080?lang=en
- achairapart 5y agoLooking at the app reviews looks like it's also a dream for the user (only 5-star ratings!). Kudos to you! Please consider a blog post with more details or even open source some of your stack (especially the react-native bits). Like others users here, I'm also very interested in your "retrogressive" approach!