3 ms·

There is no such thing like one codebase for all your devices. Sure you can share code but if you want to develop a great app you have to tweak it considerable

There is no such thing like one codebase for all your devices. Sure you can share code but if you want to develop a great app you have to tweak it considerable for each device. The fact that I have to write Javascript again puts me off entirely. Unless I can compile swift to wasm and run it on the web I have no plan to return to the "web development". Native apps work best for mobile users now anyway. I use the browser only for news and search though, so if you have a "website"/blog html still makes sense(regardless of the "progresive" features).

meesterdude 9y ago
> There is no such thing like one codebase for all your devices Basecamp reuses a lot of their rails code when rendering across mobile, web and desktop. They pepper in JS/CSS to suit device specifics, but otherwise everything is the same.
- redial 9y ago
  You forgot to keep reading before agreeing with him/her. > Sure you can share code but if you want to develop a great app you have to tweak it considerable for each device.
  - meesterdude 9y ago
    I read the comment in full before replying. I do not feel the tweaking required per-device with rails is "considerable"; in the same way it would be with android vs iOS with ionic, for example.
0x445442 9y ago
Yeah, I've spent the last year working on a (functionally simple) SPA... I won't mention the framework used because I think it's irrelevant but the experience has only confirmed the position I've maintained for years; in general, web apps are broken. The browser was designed to display hyperlinked text and to support a limited set of actions on form data. IMHO, the main reason the whole web app craze took off was because serving the apps from centralized servers solved a number of the issues around application distribution and updates. This was a big problem at the time but it's ironic that shortly afterward mom, pop, buddy and sis became very comfortable downloading and installing things like iTunes and (even more ironically) browsers.
- pjmlp 9y ago
  4 years ago I returned to native development, only doing Web stuff when I can't avoid it, it has been a pleasure.

meesterdude 9y ago

> There is no such thing like one codebase for all your devices Basecamp reuses a lot of their rails code when rendering across mobile, web and desktop. They pepper in JS/CSS to suit device specifics, but otherwise everything is the same.

redial 9y ago
You forgot to keep reading before agreeing with him/her. > Sure you can share code but if you want to develop a great app you have to tweak it considerable for each device.
- meesterdude 9y ago
  I read the comment in full before replying. I do not feel the tweaking required per-device with rails is "considerable"; in the same way it would be with android vs iOS with ionic, for example.

0x445442 9y ago

Yeah, I've spent the last year working on a (functionally simple) SPA... I won't mention the framework used because I think it's irrelevant but the experience has only confirmed the position I've maintained for years; in general, web apps are broken. The browser was designed to display hyperlinked text and to support a limited set of actions on form data. IMHO, the main reason the whole web app craze took off was because serving the apps from centralized servers solved a number of the issues around application distribution and updates. This was a big problem at the time but it's ironic that shortly afterward mom, pop, buddy and sis became very comfortable downloading and installing things like iTunes and (even more ironically) browsers.

pjmlp 9y ago
4 years ago I returned to native development, only doing Web stuff when I can't avoid it, it has been a pleasure.