Slashdot Mirror


Can Web Standards Make Mobile Apps Obsolete? (arstechnica.com)

nerdyalien writes: There's a litany of problems with apps. There is the platform lock-in and the space the apps take up on the device. Updating apps is a pain that users often ignore, leaving broken or vulnerable versions in use long after they've been allegedly patched. Apps are also a lot of work for developers—it's not easy to write native apps to run on both Android and iOS, never mind considering Windows Phone and BlackBerry. What's the alternative? Well, perhaps the best answer is to go back to the future and do what we do on desktop computers: use the Web and the Web browser.

145 of 225 comments (clear)

  1. no by Anonymous Coward · · Score: 5, Insightful

    no

    1. Re:no by Anonymous Coward · · Score: 2, Insightful

      Wrong.

      The correct response is, "LOL! No!"

      You need to get the "LOL!" in there. The question that was asked is so dumb that it deserves laughter as part of the answer.

    2. Re: no by Anonymous Coward · · Score: 1

      Or use a universal language like Java that compiles everywhere. Write once, works everywhere.

    3. Re: no by Anonymous Coward · · Score: 1

      Or Flash. This is 2011, right?

    4. Re: no by Anonymous Coward · · Score: 1

      Flash is way better than Java. Flash is deprecated on browsers due to security problems (same as Java) which is a browser issue. This has nothing to do with the utility and practicality of both languages in other domains. Notably, flash and java are fine for applications.

    5. Re:no by BarbaraHudson · · Score: 2, Insightful

      Close - but the correct answer is to add "So, now you want me to download the UI and all the code necessary to run the app every time I open it, open slower, and use more bandwidth on our crappy data caps instead of just the data? How is this a benefit? We already use ad blockers to keep from wasting bandwidth."

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    6. Re: no by ShieldW0lf · · Score: 3

      Adblockers aren't about bandwidth, they're about keeping people from manipulating us.

      --
      -1 Uncomfortable Truth
    7. Re: no by zaphirplane · · Score: 4, Informative

      You don't know and understand browser caching or do you have a good understanding of the reasons it would not work effectively ?

    8. Re: no by SQLGuru · · Score: 2

      Look into the offline manifest. I've written a Cordova nee PhoneGap app that uses the offline manifest to cache the app and relevant data. You have to be online the first time to download everything, but then it will work just fine in airplane mode. Once a connection is reestablished, it will sync data and even self-update.

      This app won't pass iOS certifcation, but can be sideloaded just fine. And since it's PhoneGap, it works on other platforms, too.

    9. Re: no by SQLGuru · · Score: 2

      And as a follow-up, here's some good info on the Offline Manifest: http://www.html5rocks.com/en/t...

      From the article:

      Using the cache interface gives your application three advantages:

      Offline browsing - users can navigate your full site when they're offline
      Speed - resources come straight from disk, no trip to the network.
      Resilience - if your site goes down for "maintenance" (as in, someone accidentally breaks everything), your users will get the offline experience

    10. Re: no by GuB-42 · · Score: 1

      People manipulate us all the time in the content itself in a manner more insidious than ads. So ad blockers don't keep people from manipulating us either.
      They simply allow us to access the content we actually want without obstruction. If things like overlays or flashing banners didn't exist, ad blockers wouldn't have been so popular.
      Some sites are literally unusable without an ad blocker (ex: overlay with the close button outside the screen), how webmasters think it is a good idea goes beyond me. Not only they hurt themselves, effectively driving out all non-adblock-users but they also hurt all other sites which have a more reasonable policy. Because once the adblocker is installed, it is here to stay. It is also bad for unconditional ad blockers because instead of webmasters just dealing with them like they did years ago, they now implement countermeasures.

    11. Re:no by Keruo · · Score: 2

      Nobody will pay to use a website.

      salesforce.com? Office365? Google apps?
      Plenty of people are willing to pay if your "website" is good enough.

      --
      There are no atheists when recovering from tape backup.
    12. Re: no by LostMyBeaver · · Score: 1

      Java on iPhone or Windows phone?

    13. Re:No by Zontar+The+Mindless · · Score: 1

      Nuke the "mobile" part of the page URL to preserve your login.

      --
      Il n'y a pas de Planet B.
    14. Re: no by Darinbob · · Score: 1

      Ad blockers are about all of it. Privacy, malware prevention, reclaiming bandwidth, and sometimes just to block ads.

    15. Re: no by Darinbob · · Score: 1

      Forth would be best I think.

    16. Re: no by tigersha · · Score: 1

      An all the security holes now also work everywhere. Even in Windows Phone! Great!

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
    17. Re: no by tigersha · · Score: 1

      Java applets in a browser is a load of shite, Java the language is so-so and Java the VM is pretty brilliant. Remember, basically everything in Android runs on Java.

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
    18. Re:no by yes-but-no · · Score: 1

      How else we will harvest all other info about you [like your GPS, microphone input]? If it's an app, we can know everything about you (who knows may even peek inside your digital wallet). It's hard to do with web-only. In fact I read some big online retailers are pushing for app-only purchase and shutting down their web-interface.

    19. Re:no by jeillah · · Score: 1

      A properly designed web app will cache most of the necessary resources so you won't need to download it more than once unless it changes. It can even operate offline in some cases. Web apps can use some of the host devices but not all unless you convert it to a native app using PhoneGap or something similar. They are not as fast on iOS but this is because Apple chooses to make it that way, they want you to have to go through the App Store and pay the Apple tax.

      The word 'properly' is the key here. Most front-end devs can't do anything without heavy frameworks and other libs. Techniques such as Single Page Apps are not very performant, at least not in the early frameworks.

      As the Javascript,HTML5,CSS3 world matures performance and capabilities will improve to the point where you probably won't be able to tell native from web in most cases. However there will always be some apps that can only be native.

    20. Re:no by BarbaraHudson · · Score: 1

      Also, since any web monkey can implement the changes, there's more likely to be more MORONIC changes because the barrier to change is so low. Look all over the web and you'll see why too low a technical knowledge barrier to entry is a bad thing.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    21. Re:no by MoarSauce123 · · Score: 1

      Not only that, having web standards is one thing, but the key piece here is consistent implementation by browser vendors and we are still far away from that. I understand that executing and rendering all the same in a browser would remove the need for various browsers (as if there is such a need!), but given the ways Mozilla, Google, Microsoft and Apple turn, we are heading into the opposite direction. The code pieces could be downloaded once and stored locally. That is already done by browser caching and whatever is in cache is not downloaded again. Any modern platform has a browser, so the suggestion that this is the way to go is not wrong....if browsers would be standards compliant.

  2. No. by Anonymous Coward · · Score: 1

    Next question.

  3. Again and again by Dan+East · · Score: 4, Insightful

    How many times is this going to be rehashed? Wasn't Java going to accomplish this 15 years ago? The web browser has turned into a VM - a very convoluted, inconsistent, difficult to develop for, hodgepodge mess of a VM. We've got WebGL and Web Audio API and all the HTML5 stuff (local storage, canvas rendering, etc, etc), and still it's a pathetic step-child of a "platform" to develop for compared to pretty much any proper platform. If "write once, run everywhere" is what you want, then sure, go for the lowest common denominator (HTML5 "apps") and you will end up with the end result of the lowest common denominator of performance and platform integration.

    --
    Better known as 318230.
    1. Re:Again and again by Lunix+Nutcase · · Score: 1, Funny

      Will it be the same year as the Linux desktop?

    2. Re:Again and again by Drethon · · Score: 1

      More than that for me. Even if it works perfectly, I don't want a game I have to download each time I play it. I want my game stored local.

    3. Re:Again and again by murdocj · · Score: 1

      Maybe the Linux Desktop will be a web app?

    4. Re:Again and again by HornWumpus · · Score: 1

      We can write 6502 assembler with javascript macros for the operations, labels for all the addresses.

      Apple ][ entry points for I/O.

      It will be brilliant.

      Just don't redefine the register variables as real.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    5. Re:Again and again by Anonymous Coward · · Score: 1

      Moreover, this whole attitude of "let's force update apps for vulnerability and features" needs to die. There's a reason people don't upgrade software that sort of works with newer, sort of works differently versions. The newer versions are often shit, with gratuitous new features added, old useful features removed, and huge new dependencies which cause a big mess and loss of productivity. Of course people aren't going to upgrade.

      Web "apps" where the app exists on a single server and is upgraded whenever the owners feel like it are a stupid idea that shouldn't be encouraged. Slashdot is an excellent example of this design, we get beta software shoved down our throats every six months and it literally takes people threatening to leave before the beta plans are abandoned ... for six months.

      Read my lips: there's nothing wrong with ancient software. It works, it's stable, and it lets people get stuff done. Exactly the opposite of the cloud/HTML5/continuous upgrade cycle myth that TFA peddles.

    6. Re:Again and again by AmiMoJo · · Score: 2

      I like the limitations of web browsers. They stop developers being asshats.

      I like apps too. Unlike web apps I can keep using the last good version indefinitely.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    7. Re:Again and again by mikael · · Score: 1

      Every application ends up going that way. New modules are written (20,000+ lines) of code are implemented, tested and integrated. Then they are extended, and extended a bit more with workarounds, refactoring, internal restructuring so that the API calls that were originally large algorithm functions on their own are now reimplemented as a series of calls to an internal state machine functions. But then there's a new desirable feature from customers, so everything moves in a new direction, something new comes along. That requires a certain amount of rejiggery in order to get everything to play nice with each other. Sometimes if the developers are particularly adventurous, there will be a complete rewrite with a "new standard", only to have everything above happen again.

      With web-browsers, these included having 256 color palettes, true-color images, supporting custom TTF fonts, CSS style sheets, PHP, JavaScript, ActiveX, being able to have a virtual canvas that was larger than the display window view, embedding video, encryption with secure sockets, 3D animation with VRML, WebGL, supporting PDF, all the different image file formats (JPG, PNG, TIFF, TGA, BMP), all the different video codecs (MPG, AVI, DIVX). Drop any standard and there will be screaming and wailing from developers in every part of the world. So applications and web-browsers become these massive code-monsters with tentacles of directories that just swallow up every module standard there is.

      This happens to desktop and embedded applications as well, customers want to be able to send email from within an application, integrate training videos with the API, have a console window for settings and diagnostics, run scripts, do photo-realistic rendering of presentation graphs.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    8. Re:Again and again by BarbaraHudson · · Score: 1

      I like the limitations of web browsers. They stop developers being asshats.

      +1 Funny :-)

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    9. Re:Again and again by LostMyBeaver · · Score: 1

      In 1999 while porting the Opera web browser to Linux, I implemented an option to run Opera as a X window manager an spawn apps via a file:// URL and added an tag for parenting native apps in web pages. In short, a web Linux desktop.

    10. Re:Again and again by Xyrus · · Score: 1

      How many times is this going to be rehashed? Wasn't Java going to accomplish this 15 years ago?

      More like 20. It did accomplish it's primary goal, but then people wanted it to do more. But instead of re-architecting/re-implementing to sanely add those new pieces, it got stapled on. And then it grew, and grew, and grew.

      Javascript is even worse. It was never intended to be an application language. It was meant to add little snippets of functionality into web pages. HTML was supposed to be document mark-up. People wanted something that did more. But instead of examining, architecting, etc. a new sane system to encompass those needs, they hacked and built on top of the existing technology. And it grew, and grew, and grew, until it has become thebarely functioning disaster it is today.

      The web browser has turned into a VM - a very convoluted, inconsistent, difficult to develop for, hodgepodge mess of a VM. We've got WebGL and Web Audio API and all the HTML5 stuff (local storage, canvas rendering, etc, etc), and still it's a pathetic step-child of a "platform" to develop for compared to pretty much any proper platform. If "write once, run everywhere" is what you want, then sure, go for the lowest common denominator (HTML5 "apps") and you will end up with the end result of the lowest common denominator of performance and platform integration.

      You won't even end up with that much, as browser differences can take even the most straightforward web application and turn it into a mess of special checks and exceptions.

      Everyone wants web. No one wants to take the time and effort to develop a sane platform. I've been writing software for a long time from systems using custom CPUs to super computing applications to web applications. I can honestly say I would rather write applications in assembler than write applications for the web.

      --
      ~X~
    11. Re:Again and again by doom · · Score: 1

      AmiMoJo wrote:

      I like the limitations of web browsers. They stop developers being asshats. I like apps too. Unlike web apps I can keep using the last good version indefinitely.

      If only we had web developers with some respect for their users, maybe we could find some way to combine the virtues of both.

      Let me file that idea over here with the "sane republicans" project.

    12. Re:Again and again by doom · · Score: 1

      Xyrus wrote:
      Everyone wants web. No one wants to take the time and effort to develop a sane platform. I've been writing software for a long time ...

      And you certainly have the rap down. Question: when do programmers want to throw everything away and re-write it according to their own tastes? Answer: always.

      Question: how do you know when it's really a good idea to throw everything away? Answer: good luck.

    13. Re:Again and again by doom · · Score: 1

      Anoymous trolled:

      All you have to do is invest thousands of man-hours into coding up your own Slashdot alternative, cultivating a community of readers and contributors, and curating all the content yourself. Or pay a team of people to do it for you.

      What's that? You don't want to? Well then maybe you should just shut the fuck up. Slashdot is a privately-operated website that exists solely for the benefit of it's owners, and is theirs to do with as they please, including updating the software every few months.

      The actual issue is hardly the cost of developing the software, (open source software to do this exists, including some versions of the slash code). The trouble is that bit about "cultivating a community", and slashdot, like every web site in existance, babbles incessantly about The Community this, and The Community that.

      You don't "cultivate a community" by telling them to "shut the fuck up". Strangely enough, people who have bought into a "community" like to feel that they're respected and valued, and if not they'll probably go looking for some other community out there.

      (You have to love knee-jerk libertarians, you wind-em up, they spew the same crap... "If you want to protest racist shopping mall security, you should build your own shopping mall first!")

    14. Re: Again and again by MichaelAlexanderSavi · · Score: 1

      One thing I never understood, if the web is that hard to develop for why is it the platform for most desktop software?

  4. Re:so.... Firefox OS? by lseltzer · · Score: 2

    no, that's not what FFOS is. FFOS takes web sites and packages them up as apps that are delivered through a store and they run locally on the device, something like Cordova apps. The story (and I ought to know because I wrote it) discusses actual mobile web sites, e.g.. m.slashdot.org as opposed to a Slashdot app. It's not hard to give the app experience by putting an icon on the screen and running the browser full-screen

  5. No by Anonymous Coward · · Score: 1

    "perhaps the best answer is to go back to the future"

    Oh you mean going back to thick clients on the desktop like we used to? Yeah I'm for that. Going to the web for everything? That was Jobs first idea for the iPhone and quickly saw the draw backs.

  6. Back to the what now? by Mantrid42 · · Score: 1

    Besides email and, well, browsing, there's nothing I do on a web browser. I like having local applications.

    1. Re:Back to the what now? by fluffernutter · · Score: 1, Flamebait

      You use a web browser for email? Web email clients totally suck!

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    2. Re:Back to the what now? by fluffernutter · · Score: 2

      I don't really want to sit here and type through everyghing, but here are a few reasons: for one thing, attachments don't download in the background. You have to click on the link and download the attachment. Google also limits the size of the attachment, and generally speaking the size is limited by web server configuration. Also, you don't really own the emails. I know someone that lost emails from her deceased father because she had waited too long to sign in. There is a lot of lag on webmail clients. Currently gmail will show me around 20 emails and it takes almost a second for the next page to load. I'm an extremely fast reader, and it does slow me down alot when looking for an email because in a native client I can just scroll freely. Generally speaking, pagination sucks and is rampant on the web. There is no 'preview pane' in gmail which also slows me down. There is a preview pane in Zimba which is what my provider uses, but there I can only see around 7 emails on a page and don't get me started on the lag or attachment size limit.

      You're not going to make me go on are you?

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    3. Re:Back to the what now? by fluffernutter · · Score: 2

      Also, once I set up my email in a desktop application, I click the icon and I am there. with gmail I must click on the browser icon, navigate to the page, sign in, blah blah. Gmail doesn't get as much screen space as the native application because it is only allowed the space that the browser allows. this means that screen space is wasted because the browser wants to keep showing me controls like the back button which doesn't really apply to gmail. Also, I can't alt-tab from email to a web page now, I must click on a tab in the browser to switch which is frustrating as well. Drag and drop is handled by javascript and not the native OS, which means that you get interesting quirks whereby the browser decides it wants to select text instead of dragging. If I want to create a folder in gmail, there is no right click context menu so I have to hunt for the button that does that function. That doesn't just pertain to folders, there are a bunch of places I use the context menu.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    4. Re:Back to the what now? by fluffernutter · · Score: 1

      One more thing. When I want to select an entire email in my native application CTRL-A will accomplish that properly. On the other hand in gmail it selects everything in the browser which is a mess.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    5. Re:Back to the what now? by robert.geake · · Score: 1

      Back button.. Something I never though I'd see in a mail client!

    6. Re:Back to the what now? by Zontar+The+Mindless · · Score: 1

      Så... We're right back where we started from--web mail is fine for lolcats, and TOTALLY SUCKS for anything serious.

      --
      Il n'y a pas de Planet B.
    7. Re:Back to the what now? by doom · · Score: 1

      anonymous insincerly guffawed:

      Please inform us on how you think web email clients (Google Inbox/Gmail for instance) "totally suck"

      I don't need to, I've proved it to myself empirically by copping out and switching to gmail several years ago when the situation changed with my old mail server. Since then I've all but given up on email, I went from checking it every twenty minutes to checking it every three days. I've stopped reading the dozen or so technical mailing lists I'm subscribed to. There's something about gmail that makes using email subtly unpleasant and uninteresting: it isn't really *my* problem to figure out what that is, it's my problem to switch to something better.

      If I were going to pick a detail to complain about: the javascript popup window for composing a message. The non-standard behavior of that thing drives me crazy. If only it were a textarea it wouild work with the "It's All Text" firefox plugin, but Google Knows Best, why would I want control over the behavior of my software?

    8. Re:Back to the what now? by doom · · Score: 1

      Actually... the fact that google doesn't break the back button is one of the few things I like about gmail.

      Complaining about the "waste" of screen real estate here seems pretty fucking crazy to me, but then I guess you guys are all "mobile" suckers (hint: don't try to do serious work on a gadget with a screen a few inches wide, with fucked ergonomics that keeps your chin clenched against your chest).

    9. Re:Back to the what now? by doom · · Score: 1

      Also, I can't alt-tab from email to a web page now, I must click on a tab in the browser to switch which is frustrating as well.

      By the way: try Control Next Page. In firefox you can switch between tabs with keyboard commands... provided one of the tabs doesn't steal your keybindings.

    10. Re:Back to the what now? by doom · · Score: 1

      All of those issues might be a concern for you, but I would say that they are on the far margins of typical email use.

      And here we have "designer" excuse number #37: you are an experienced user so you don't count.

      But aren't we all experienced users? Why would your Target Market sit still and let you treat them like drooling morons? (Note: see "adblock").

    11. Re:Back to the what now? by fluffernutter · · Score: 1

      So this means alt-tab to bring up firefox and then control-next page (is that a key?) in Firefox to get to email. I'd rather alt-tab to my native email client and be done.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    12. Re:Back to the what now? by doom · · Score: 1

      Of course, nothing forces you to use browser tabs, you could always keep your webmail in a browser window of its own...

      For what it's worth there are actually multiple different cyclic lists of stuff I juggle using different keyboard commands... just for funsies, these are:

      • application windows (alt-tab)
      • firefox browser tabs (control-next page)
      • emacs buffers (control-x-b)
      • x windows/icewm desktops (control-alt-<number>)
      • the emacs kill-ring (control-y, alt-y)

      The emacs kill-ring is like the "clipboard" except that it can hold multiple pages. Sort of like an actual clipboard.

    13. Re:Back to the what now? by fluffernutter · · Score: 1

      Is this supposed to have something to do with making webmail clients better? Because with all due respect, this is just complicated and none of it helps.

      --
      Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    14. Re:Back to the what now? by doom · · Score: 1

      No it's not about making webmail clients better, it's about ways to deal with the specific objection you raised, presuming you actually want to know how to use your box, and not just play that swiping/zooming game everyone seems to be addicted to these days.

      Let me repeat the first line of the last post:

      Of course, nothing forces you to use browser tabs, you could always keep your webmail in a browser window of its own...

  7. So Steve Jobs was a visionary? by Spy+Handler · · Score: 4, Interesting

    Steve Jobs, 2007: You can build amazing Javascript Web 2.0 apps for the iPhone! We didn't make a SDK because you don't need one.

    Steve Jobs, 2008: Okay here's your SDK

    1. Re: So Steve Jobs was a visionary? by BarbaraHudson · · Score: 1

      Indeed. One (JavaScript) thread should be enough for anyone. Effing web developers.

      It is - anything more than that, you shouldn't be using javascript.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  8. Re:so.... Firefox OS? by Anonymous Coward · · Score: 1

    Its not hard to give the app experience for something like Slashdot. But for something complex - yeah it is and it will still suck compared to the native app version.

    I should know I wrote a highly complex iOS app (nearly single handed) that took a team of web developers to try to match functionality and it still sucks by comparison.

    Sorry but this article reads very naive

    "but in the long term the company may move back to a more portable model. (We also asked Facebook for comment on this story and got no reply.)"

    Yeah Facebook might decide to takeover the moon to - but they haven't made any moves in that direction either. What they have done is began to build a suite of native libraries.

  9. Only when new versions stop breaking their UX by Sowelu · · Score: 3, Insightful

    I hate upgrading my apps. I'm entirely willing to suffer security vulnerabilities and lack of new features in order to keep the user interface I'm used to and that works for me. In the case of Google Maps and Chat and almost everything else Google for example, new versions offer totally different functionality that often doesn't work for my use case anymore. I strongly suspect that there's a LOT of users like me...yeah, security vulns suck, but the time investment to keep everything up to date and relearn infrequently used applications is massive. I'd never get anything done.

    1. Re:Only when new versions stop breaking their UX by Actually,+I+do+RTFA · · Score: 1

      I tend to agree with you. I understrnad why maintaining to UXs sucks though. I don't think I can think of a single UX improvements from updates after Windows95 (except when oither people included it in a competing app and the other one just stole it, therefore using their market power to keep the upstart out and reducing the value of innoveative UX, but that's a different rant.

      --
      Your ad here. Ask me how!
    2. Re:Only when new versions stop breaking their UX by schnell · · Score: 1

      I don't think I can think of a single UX improvements from updates after Windows 95

      Really? How about:

      • Mac OS X "column browser" view in the Finder
      • Android/iOS/Windows tablets with "swipe from below/above" to view key system settings or notifications very easily (or right-side notifications single-click icon on Mac OS X)
      • Windows 8/10 "tiles" or Mac OS X "Launchpad" to put the most frequently used applications front and center for easy access
      • Transparency (all modern OSes) to make background applications/windows partly visible when useful
      • Anti-aliased fonts and vector graphics (all modern OSes) for icons to make desktops usable at any resolution
      • "Dock" icon repositories (all modern OSes) to make the current and most frequently used applications available at one click, not just a la the Win95 task bar
      • System + web search through an integrated one-click desktop search bar (dates back to MacOS 9[!] Sherlock)
      • "Mission Control" on MacOS X to show live previews of all open application windows using a three-finger mouse swipe, not just Alt+Tab style switching

      Look, I agree with you that the advances in desktop OS UIs have been incremental rather than revolutionary since Windows 95, there has been a LOT of good work done there. Try downgrading to Gnome 1.0 and tell me if you see anything missing...

      --
      "95% of all Slashdot .sig quotes are incorrect or completely fabricated." -Benjamin Franklin
    3. Re:Only when new versions stop breaking their UX by doom · · Score: 1

      schnell wrote:

      Look, I agree with you that the advances in desktop OS UIs have been incremental rather than revolutionary since Windows 95, there has been a LOT of good work done there. Try downgrading to Gnome 1.0 and tell me if you see anything missing...

      Dude, I use icewm. I look at gnome whenever I install a new linux, get immediately turned off and go back to running icewm.

      If you want a specific complaint: in icewm, I do alt spacebar, a window control menu pops up, and then I hit a single keystroke to do whatever I want, and there's an underscore in the menu that reminds me which keystroke that is. You can do an alt spacebar in gnome, it pops up a window control menu, and then what? Then I get to cursor around and hit return?

      The trendy kids decided that mousing is all anyone needs, and let support for keyboard alternates rot, so I don't use the software the trendy kids came up with. This has not gotten any better with the succeding waves of trendy kids.

      Caveat: icewm isn't working right on Debian jessie: looks like there's a systemd incompatibility (uh, just killed this thread, didn't I? Sorry). Maybe I need to run Devjuan...

      But the actual question here is not whether any of your UI improvements are worth anything, the question is whether they're so important that they deserve to be blasted to the user in an automatic update.

      What we really need is a distinction between security updates and feature upgrades, which means developers need to support multiple versions, which means we need to be able to write unit tests that work at the level of the user interface...

  10. Yuck! by iamacat · · Score: 2

    No language choices, no reliable offline support (which should include installing app from an sd card if needed), no ability to downgrade the app or delay updates until problems are fixed. Plus massive performance, memory and functionality hit due to inflexibility and targeting lowest common denominator.

  11. Not a chance in hell. by Lumpy · · Score: 1

    I only use apps that will work offline as well as online. If your app is online only then stuff it. I'll just use the mobile web page using jquery instead of buying your lame $1.99 browser wrapper.

    --
    Do not look at laser with remaining good eye.
  12. Re:so.... Firefox OS? by Anonymous Coward · · Score: 1

    The article doesn't actually take into consideration what users want. Most users don't want Web crApps It's just another whine fest about lazy developers.

  13. Re:so.... Firefox OS? by Lunix+Nutcase · · Score: 1

    And frankly your article is poorly written. Things like:

    From the user's standpoint, it would be far better to have access to all those apps through a browser. Most of the reasons are the same as for the developers—nothing to install and automatic updates.

    are silly. Installing an app from Google Play or Apple's app store is trivial and automatic updates have been part of iOS and Android for years now. I've known plenty of people who have never used iOS and only ever dumb phones that have been perfectly capable of installing apps from the App Store and having them be auto-updated.

  14. Please God NO by JustNiz · · Score: 1

    Sorry but apps through browsers totally suck for usability in comparison to local apps.
    Apart from anything else there's the whole complete dependency on being connected thing, then there's all the massive extra lag because every interaction and UI update are now doing GETS/POSTS to a remote backend, Then there's all the unnecessary extra data usage and extra battery usage as a consequence which are both very real factors for mobiles.
    Browser apps are even a bad idea on desktops. We just "upgraded" to Office365 at work. What a complete fucking laggy mess and giant step backwards in productivity and usability that is, mostly because its obviously implemented as some sort of browser-based app now. I'd bet it just because some clueless moron like you at Microsoft thinks "moar web=== kool"

    1. Re:Please God NO by robert.geake · · Score: 2

      I've been building web based software for 15 years and I've always only picked up on new "fad's" IF they actually improved what I was building. It has worked well for some customers but sadly, these days, everyone wants the latests thing even if it doesn't really fit the model or make the application better... There are so many simple tricks one can use to make a web interface easy to use, cross platform and fast (limiting the actual code the browser has to load and render, avoiding JS, jQuery and the like like the plague and such) but everyone want to use Laravel or Angular or jQuery when they don't really need to! The world is making things hard for it's self...

    2. Re:Please God NO by doom · · Score: 1

      Then there's all the unnecessary extra data usage and extra battery usage as a consequence which are both very real factors for mobiles.

      Um... so what you're saying is that mobile devices suck? I have an idea: don't try to use them for serious work, then you'll stop worrying about battery life.

      Someday, computers will advance beyond this era of four inch wide screens, wimpy processors and limited memory, and then we will all wonder about this "bring back the 70s" movement.

  15. Not without a lot of work by PhrostyMcByte · · Score: 1

    The benefit that native apps give is consistency. Unless your app goes out of its way to do something weird (and these definitely do exist), it gets consistency for free! The user learns how to use their environment, and this consistency gives them an anchor point for using your app efficiently.

    Web apps are the wild west with every site behaving differently in all but the basics, and then sometimes even the basics don't quite work. Even those who try to mimic a native app's look and feel never seem to get it right, leading to frustration as you then expect things to work in a specific way.

    Until this can be solved, I don't think web apps are the solution. Even then, web apps tend to use significantly more RAM and CPU, so it's still not going to work where responsiveness has value.

    1. Re:Not without a lot of work by Lunix+Nutcase · · Score: 2

      Web apps are the wild west with every site behaving differently in all but the basics, and then sometimes even the basics don't quite work. Even those who try to mimic a native app's look and feel never seem to get it right, leading to frustration as you then expect things to work in a specific way.

      And if they aren't constantly updated that native look and feel mimicry then fails to keep up with the native platform thus defeating the whole point. For example, I've gone to a number of wordpress sites still using a "native" theme for iOS that hasn't matched the platform since iOS 6.

    2. Re:Not without a lot of work by Lunix+Nutcase · · Score: 1

      Yeah just throw more bloated Javascript frameworks on top! That'll surely solve the problem!

    3. Re:Not without a lot of work by CanadianMacFan · · Score: 1

      And what native app's look do you try and mimic? Is it the iOS one? Android? Blackberry? Windows? And what version of the OS? If you are going to provide a look and feel for all of them then you are giving up one of the major advantages of building a web app. Of course trying to mimic the look and feel of a native app in a web app is much harder than building the native app in the first place. At least from my experience in building iOS applications.

      Having said that I hate the idea of web apps. Like you said they use more resources. Plus I may be in areas where I don't have access to the Internet. There are some places along my bus ride from the suburbs to downtown where my cell signal disappears. Some people don't, or can't afford, data plans. If the developer shuts down I can still run a native app but I lose access to a web app (along with my data). It shows my age but I hate the philosophy of trying to exactly place elements in HTML as if it is a high end design tool. It was never designed to be that precise. Flexibility in the layout was a feature and so many people are trying to work around it. If you need to precisely lay out your design then use another tool. And you will need to if you are building net apps.

    4. Re:Not without a lot of work by robert.geake · · Score: 1

      Why are people in the tech industry so scared of taking a step backwards?

    5. Re:Not without a lot of work by Lunix+Nutcase · · Score: 1

      Yes, because nothing says "not reinventing the wheel" like dozens of Javascript frameworks.

    6. Re: Not without a lot of work by MichaelAlexanderSavi · · Score: 1

      Offline isn't much of an asset since most popular apps function as clients to Internet services like Facebook & Amazon.

  16. Better Web Standards Needed by nateman1352 · · Score: 5, Insightful

    I don't know about everyone else, but IMHO the web browser is THE WORST platform to code for in existence. It amazes and depresses me how little has changed about client side web programming since IE4. Instead we have created these huge frameworks to try to hide the suck under an enormous pile of middleware. But still we are doing this fundamentally broken thing of shoehorning a language intended to describe formatted text documents (HTML) to instead describe a GUI for an application. This reminds me of IE4 and its web page dialogs.

    If we truly are serious about having the web be an application platform then a new markup intended to describe cross platform application GUIs and a standard bytecode for the web is needed. Asm.js and enscripten or PNaCl both could be our new standard bytecode, both have pros and cons that I won't rehash. Honestly I'm not a huge fan of either one. But no one is trying to address the fact that HTML's layout system is designed for documents... Not for GUIs. We really need something like XUL or XAML made in to a web standard. I don't care about the politics of what language/tool we choose as long as its a good one thats open for all. I'm sick of the holy wars over tools and languages. That said JavaScript is garbage just like HTML and CSS for actual development and needs to be replaced with a sane language.

    1. Re:Better Web Standards Needed by CanadianMacFan · · Score: 1

      Maybe how about stop using a web browser to run net apps? They were never designed to a lot of what they are currently doing and it's amazing that they work as well as they do. It depresses me that web designers are still trying to force browsers to show pages exactly the same in every browser on all computers. Even more depressing are the ones that haven't clued in that your screen size isn't the size of your window.

      Using your web browser to run net apps is like using your word processor to edit your images. It's the wrong tool for the job. Adding another web standard for the browsers to follow isn't going to help the situation. HTML and CSS just need to go back to suggesting how a document is to be presented and have all of the extra add-ons taken out.

    2. Re:Better Web Standards Needed by mikael · · Score: 1

      Too late now ... *everything* uses HTML webpages to manage control systems. Your wifi router will have configuration, diagnostic, security and login windows accessible only through a webpage. The same is happening with corporations. Even software development houses automatically generate HTML pages to indicate the state of all projects.

        For corporate applications, it's absolutely critical that something looks exactly the same on all browsers. That's the only way the training and help manuals can remain accurate.

      Let's say we were to build everything from scratch. First need would be to have a scripting language to create page layouts with forms, be able to add pictures and embed video. That scripting language would need to be able to reuse the style of different webpages, allow the use of discussion forums, being able to add comments, maintain wikis.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    3. Re:Better Web Standards Needed by BitZtream · · Score: 1

      I don't know about everyone else, but IMHO the web browser is THE WORST platform to code for in existence.

      You don't do anything other than websites, do you?

      With web browsers your problems are 2 things, shitty language (javascript) and different browsers. In modern terms, you have fewer browsers than you have OSes, so if you want cross platform support the browser is your path of LEAST resistence. If you support webkit, you immediately get the majority of the internet across all platforms, and you'll get close enough out of the box for anyone who uses firefox. You can ignore firefox users up front because they use a shitty browser and complain all the time about anything and everything anyway. The only other browser worth mentioning is Edge since its the direction Microsoft is moving in. In my line of site on my desk right now, I can see 5 different devices that have webkit based browsers, one that runs Edge, no firefox and no IE, certainly nothing like Opera or more obscure than that. But from an OS perspective, that covers OS X, Windows, FreeBSD, Linux and Solaris.

      So for web dev, you essentially support webkit and edge and you get the entire planet, with a few outliers that don't matter anyway because they're doing something obscure.

      For real developers that want to do cross platform, its ridiculously more complicated with completely different APIs in a lot of cases ... and you're bitching about some minor implementation differences in a pretty well recognized standard? bwhahahahaha FFS there are more Windows variations than there are browsers to choose from, and I'm ignore the 100 different Linux distros that all have minor differences (wouldn't be a different distro if it didn't, would it?)

      It amazes and depresses me how little has changed about client side web programming since IE4

      Hate to break it to you, but programming hasn't really changed in the last 30 years that I've been doing it. New languages and frameworks, sure, but they aren't actually doing anything new, just more of the same thing they've always done, and faster. If you're expecting the world to change you're going to be disappointed because there is no reason for massive change, what we have works well and fits the way humans work well. You're not doing anything today that you weren't doing in IE4, you're just doing MORE of the same shit and applying it differently. Its easier now to do the same things as before, but its still the same crap. Web pages today are really the same as they were 20 years ago, except now thanks to javascript and flash they have a shitton of advertising that yells and blinks at you.

      You sound extremely inexperienced.

      But still we are doing this fundamentally broken thing of shoehorning a language intended to describe formatted text documents (HTML) to instead describe a GUI for an application

      Stop making shitty web pages. Thats not the fault of the language, thats the fault of the devs using the language or document format. HTML isn't intended for 'applications', and that is dumb, thats why I don't do that. Problem solved. A little interactivity and help on a web form is delightful though.

      If we truly are serious about having the web be an application platform then a new markup intended to describe cross platform application GUIs and a standard bytecode for the web is needed.

      If anyone wanted a 'one size fits all approach' we would have switched to Java 10 years ago since it does exactly what you're talking about. Thats not what people actually want.

      Asm.js and enscripten or PNaCl both could be our new standard bytecode, both have pros and cons that I won't rehash.

      Oh, you're one of those morons who thinks using a compiler from one language to compile code to another language and then interpret it with a JIT is a good idea. Sorry, you're just an idiot. You've utterly

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    4. Re:Better Web Standards Needed by doom · · Score: 1

      CanadianMacFan wrote:

      Using your web browser to run net apps is like using your word processor to edit your images.

      Hey. Emacs and the xpm format are all anyone needs.

    5. Re:Better Web Standards Needed by doom · · Score: 1

      Yeah, that's pretty much it: the web is the worst platform ever except for all those other platforms.

    6. Re:Better Web Standards Needed by doom · · Score: 1

      Hey, Javascript is a great language. One of these days it'll even support unicode correctly. But it's not like anyone actually uses unicode on the web, right?

  17. Pain? Really? by JustNiz · · Score: 1

    >> Updating apps is a pain that users often ignore,

    Dude enough with the unrealistic strawman.
    On Android, OSX, Windows and Linux at least, you can set updates to happen completely automatically, or at worst you just have to hit OK to authorize the available update its notifying you about. How is that really a pain?

    1. Re:Pain? Really? by Dynedain · · Score: 1

      It's not a strawman. I have several apps on my phone that haven't updated even though I turn on auto-updates and hit OK because of stupid restrictions on things like maximum app size over wifi (I have unlimited data so it doesn't matter). I also almost got screwed the last time I flew as the app I was using for my ride from the airport to home failed and disappeared from my launcher, and my phone was almost dead. Turns out there was a required update for it to work that was issued while I was *in-flight* and the app store didn't auto-update. I had used the app successfully 6 hours earlier on my way to the airport. Luckily I was able to delete and reinstall the app, and still book my ride before my battery drained.

      --
      I'm out of my mind right now, but feel free to leave a message.....
    2. Re:Pain? Really? by drinkypoo · · Score: 1

      Turns out there was a required update for it to work that was issued while I was *in-flight* and the app store didn't auto-update.

      This is why professionals turn off auto-update; professionals are assumed to be able to run the updates themselves, and software on any platform is subject to regressions, feature removal, and the like with new versions. Try being more professional.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Pain? Really? by Dynedain · · Score: 1

      Um - you missed what I said. The app stopped working because the app servers wouldn't work with an older version of the client app, and the updated client was pushed out to the app store while I was in-flight.

      Turning off auto-update altogether would have guaranteed the app didn't work either. My point was that turning on auto-update isn't the panacea the grandparent post was claiming.

      A web app would have been perfectly suitable here (initial payload for UI is trivial in this app as most of UI is real-time mapping which is downloaded on-demand anyways) and wouldn't have crapped out in the same way due to out-of-sync client installations.

      Try being more professional in your comprehension and conversation skills.

      --
      I'm out of my mind right now, but feel free to leave a message.....
    4. Re:Pain? Really? by JustNiz · · Score: 1

      This sounds like you're really struggling to find a particular rare interdependent sequence of events (on plane/low battery/previous version of app immediately not supported/app size limit in place and update just too big) just to defend your point.
      Tha flat batterry is all on you. Be better prepared next time. As is the app size limit because at least on android its off by default so you must have set it at some point.
      I will not say that no developers ever break immediately previous versions from running as soon as an update comes out, but its a fucking stupid thing to do so seems unlikely someone with a professional app woud do that. and if in this case its true, I for one would stop using that app since clearly the developer is clueless.
      I also dont believe that if you had enough power to run a web app, you couldn't also have done an update when you got on the ground.
      Even assuming you actually did encounter a rare confluence of several events where the current approach could be better otherwise, using that as sufficient argument that all apps would be better off as a web-type interface makes no sense.

    5. Re:Pain? Really? by Dynedain · · Score: 1

      1. Yes, low battery is my fault - but I wasn't anticipating spending 20m on my phone in active data modes troubleshooting an app at midnight. Other users would likely not have identified the problem and been able to fix it. I can think of a lot of other scenarios where a developer cuts off access to an old version of an app leaving users stuck (not supporting older OS versions is another good example).
      2. App size limit on iOS is imposed by Apple because AT&T and Verizon demanded it - nothing I can do about that if I want to stick with iOS.
      3. I have no idea how many versions back my copy of the app was - nor do I have a way of knowing. But a webapp (which would have been completely suitable for this use) would not have had a versioning cutoff issue like this.
      4. The risk of running out of power was do to wasting time troubleshooting and downloading a new version of the app. Had the app been working I would have been able to use it within my remaining battery life without cause for concern.
      5. I'm not arguing that all apps should be webapps. I'm countering the gp's claim that auto-updates for apps are a panacea.

      --
      I'm out of my mind right now, but feel free to leave a message.....
  18. Re: so.... Firefox OS? by Anonymous Coward · · Score: 1

    Wrong.

    I'm tired of downloading app after app when nearly all would work just fine in my web browser, especially when most of are random sites I've visited for the first time and they are pushing their app on me? No way Jose.

  19. Re:so.... Firefox OS? by binarylarry · · Score: 2, Interesting

    Apple tried it and failed.
    Firefox tried and LOL failed.
    Google tried it and is failing (how many chromebook users do you know?)

    Nope, no one wants HTML, CSS and Javascript shitapps.

    --
    Mod me down, my New Earth Global Warmingist friends!
  20. Betteridge's law by daq+man · · Score: 1

    No

  21. Re: so.... Firefox OS? by Lunix+Nutcase · · Score: 1

    And yet I've never heard the average person ever talk about wanting web apps. 99.9% of the time it's from developers or tech bloggers.

  22. Yes the answer is No. by goombah99 · · Score: 1

    Sonny, when netscape navigator was the bomb, and java and javascript were plugins, every one said the same thing then too. This will replace the file system and the applications. Java promised to run on all architectures. But it actually became write once, crash everywhere.

    --
    Some drink at the fountain of knowledge. Others just gargle.
  23. O RLY? by Gravis+Zero · · Score: 5, Informative

    it's not easy to write native apps to run on both Android and iOS, never mind considering Windows Phone and BlackBerry

    apparently you haven't heard of Qt because it supports all of those platforms.

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:O RLY? by wvmarle · · Score: 1

      Even if the UI part is the same, that still leaves you with the programming language itself (Java with specific Android extensions for Android, Obj C or some others for iOS, etc), the platform-specific libraries (you won't be able to use the exact same code that accesses the GPS in Android on iOS), the database system used, and there will be other fundamental differences as well.

      So even with QT you're still probably best off to just write a separate app for each platform.

    2. Re:O RLY? by BitZtream · · Score: 1

      Poorly, sure. Qt fanboys think its awesome, anyone with experience elsewhere, not so much

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  24. Especially in mobile. by goombah99 · · Score: 2

    in mobile battery life matters. That not only means efficient code, it also means code that plays nice with the OS to properly minimize mobile resources including memory and keeping apps in main memory. The reason apple iphones get away with smaller batteries and smaller memory sizes is that code bloat of java (dalvek).

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:Especially in mobile. by tigersha · · Score: 1

      This. This. This.

      This is also why native apps are harder to write than webapps.

      --
      The dangers of excessive individualism are nothing compared to the oppressiveness of excessive collectivism
    2. Re:Especially in mobile. by Zorpheus · · Score: 1

      The reason apple iphones get away with smaller batteries and smaller memory sizes is that code bloat of java (dalvek).

      The smaller battery drain is also true for Windows Phone.

  25. Re:so.... Firefox OS? by ganjadude · · Score: 2

    actually that is how iphone was before user generated apps. then they saw what was happening in android land and decided that it made more sense

    --
    have you seen my sig? there are many others like it but none that are the same
  26. Re: so.... Firefox OS? by stoborrobots · · Score: 4, Insightful

    But similarly, you haven't heard the average person talking about wanting native apps either.

    Developers and tech bloggers haven't realised that they need to balance conflicting desires (universal availability and version uniformity vs offline access and access to local hardware/services/data) which would induce preferences either way. What you are seeing is the tech community noticing the features they are missing, building them, and throwing away the features they already have in the process, then repeating again in the other direction.

    The average person has no idea about any of this, and doesn't care as long as they can still send selfies and cat emojis to their friends. If a native app allows them to do it, they will use that; if a web app does, then that's where they will go. As long as they can click an icon and send the picture, it's good enough for them.

  27. Re:so.... Firefox OS? by BarbaraHudson · · Score: 1

    The slashdot mobile web site sucks in comparison to apps like simply slashdot in terms of performance and NOT COVERING BUTTONS WITH CRAP! Plus, the slashdot mobile web site doesn't use the phone's back button correctly, because it IS just a dumb web app. Post a comment, then hit the back button after your comment is displayed, and look - you're back at the post comment screen. Bad functionality. But that's the way web browsers work (unlike real apps).

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  28. Re:so.... Firefox OS? by BarbaraHudson · · Score: 1

    Have you even tried the mobile site on a smartphone?

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  29. Should I move to the cloud? by Zero__Kelvin · · Score: 1
    This is essentially the following question: Does it make sense to move your apps to the cloud?

    The idea is not very good for a desktop with a reliable internet connection, but it becomes ridiculous if you look at it in terms of mobile systems. An internet connection is not guaranteed. If I am out of signal range with no WiFi the last thing I want is to have a device that can't run my applications. That goes double if I'm lost in the woods and need a compass app or I'm looking to tune my guitar, for example.

    "Updating apps is a pain that users often ignore, leaving broken or vulnerable versions in use long after they've been allegedly patched. "

    Fundamentally,you can achieve the same advantages by just setting the OS such that new updates get automatically pushed to your device.

    "There is the platform lock-in and the space the apps take up on the device."

    It is 2016 on Friday. If you are running out of space on your phone you're doing it wrong. Get a friggin device with decent storage and add a large uSD Card. Problem solved.

    " Well, perhaps the best answer is to go back to the future and do what we do on desktop computers"

    What a ridiculous thing to say. Desktops don't rely on a web browser for all their apps, or even a significant portion thereof. Do you know how many "apps" (i.e. programs) are on a Linux system, or even a Windows one for that matter. For Linux the count is literally in the thousands. Even if you are using 100 Web Based programs (and who is doing that), you are still looking at an order of magnitude more local applications.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    1. Re:Should I move to the cloud? by tipo159 · · Score: 1

      If I am out of signal range with no WiFi the last thing I want is to have a device that can't run my applications. That goes double if I'm lost in the woods and need a compass app or I'm looking to tune my guitar, for example.

      Exactly.

      As it is, too many apps depend on being connected to the network to perform basic functionality. It seems like the folks who design this stuff spend their lives in Cupertino or Mountain View or SF and don't get to places even a short distance from where they live and encounter places with poor connectivity.

      I live about 10 miles from downtown Seattle and there are plenty of places between here and there (including places where people live) with no cellular data coverage (or so spotty to be unusable). I have been in towns and on roads not far from my house and been surprised to find no connectivity so Apple Maps or Google Maps were useless in helping me figure out where to turn to get back to civilization (versus going deeper into nowhere). An hour west of my house, my phone has no service at all until I almost reach the Pacific Ocean.

      The cellular data coverage in the US is not yet complete enough for web apps to work here.

  30. Re:so.... Firefox OS? by BarbaraHudson · · Score: 1

    It also ignores that fact that you have to download all the code and ui resources every time you "load" a web app. Moronic article.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  31. Re:Apps are just browsers in many cases by BarbaraHudson · · Score: 1

    So does dragging the URL onto the phone's home screen.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  32. Re:so.... Firefox OS? by Lunix+Nutcase · · Score: 1

    That's sort of impossible since the iPhone SDK predates the first commercially-released Android phone, the HTC Dream, by 8 months.

  33. Re: so.... Firefox OS? by art123 · · Score: 1

    App stores are popular because iOS and Android mobile browsers suck and a typical rich web app/site (like your average bank or Google Docs / Microsoft Office) won't run correctly. Maybe phones with 3GB+ RAM will change this.

  34. Re:Apps are just browsers in many cases by BarbaraHudson · · Score: 1

    You can drag one atop the other and they will appear like they were in a folder when you touch the icon.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  35. Cellular Service Isn't Everywhere by JimMcc · · Score: 1

    Believe it or not, cellular service isn't as ubiquitous as people think it is. There are still significant areas of the country without adequate cellular coverage. Are you willing to have your "apps" not work because your browser can't connect to the intertubes?

    1. Re: Cellular Service Isn't Everywhere by MichaelAlexanderSavi · · Score: 1

      I don't see how you could get the most popular apps to work without Internet even if they were famous. Amazon, Facebook, YouTube Twitter⦠really the only things that can be done offline are productivity a la Final Cut or Logic and most people don't use those kinds of apps on the phone. Games too, I guess but eh.

  36. Re:so.... Firefox OS? by SQLGuru · · Score: 1

    WebOS is missing from your list..... http://www.openwebosproject.or...
    and their HTML5 framework: http://enyojs.com/

  37. Qt's QML by mx+b · · Score: 1

    But no one is trying to address the fact that HTML's layout system is designed for documents... Not for GUIs. We really need something like XUL or XAML made in to a web standard.

    I have daydreamed a bit about using Qt's QML as a way of transferring GUI information/design for websites, rather than HTML documents. If you're not familiar, QML is a Javascript-syntax (superset?) markup for declarative programming of GUIs, and Qt5 and KDE's Plasma 5 use it extensively. It's Javascript origins mean most people are already familiar with it, and could potentially repurpose/extend existing javascript engines for it rather than throwing it all out. I haven't done major projects with it, but I am a fan of KDE so I'm pretty convinced its powerful enough for general purpose web apps.

    That being said...

    That said JavaScript is garbage just like HTML and CSS for actual development and needs to be replaced with a sane language.

    Javascript is not a great language so there's slight concern of any language based on javascript. But, maybe part of why javascript sucks so much is that HTML and CSS are not really designed to work together with it. A new language/engine designed to work with it, like Qt QML is, might be fine.

  38. Obligatory xkcd by GuB-42 · · Score: 1
  39. Why not? by Tony+Isaac · · Score: 1

    A lot of "native" apps are already just wrappers for Web content. It really is a pain for developers.

    OK, so let's talk about security. If done right, a Web browser could implement the same security scheme (or better) that is now enforced for apps. Desktop browsers have started to do this somewhat, asking you if you want to provide location info, for example. A more comprehensive permissions system could directly port native permissions to Web content.

    Everybody wants you to install their app, for no good reason. If you want to stream your local TV station, they want you to install their app, one for each station. An app for CBS, one for NBC, and so on. Every store wants you to install their app so you can see their hours of operation or apply for a job. LinkedIn, which works perfectly well in a browser, wants you to install an app. Same for Facebook. Next, Slashdot will want you to install an app to read their stories on mobile, and you KNOW they will force you to see their ads.

    And that leads to probably the biggest advantage of browser-based content: you can use an ad-blocker.

  40. Worse than an App by Roger+W+Moore · · Score: 1

    You don't know and understand browser caching or do you have a good understanding of the reasons it would not work effectively ?

    Ok so now, before I want to use the app in offline mode, I have to go to the webpage first and do something to make sure that it downloads and caches all the code and data that the app will need to run offline which will need some special functionality on the website to do reliably so better hope they support it. Then I need to somehow make sure that the browser keeps this information cached and does not delete it from the cache when I download a different page. Finally I'll then need a special URL which goes to the cache without having the browser wait for an internet timeout.

    Exactly how is this better than an app I just download once and click on when I need it? Especially if I have one which exercises the CPU since implementing it s a webpage will kill the performance.

    1. Re:Worse than an App by DarkOx · · Score: 1

      Ok so now, before I want to use the app in offline mode

      I doubt it. Lets face most of what people do on their mobile devices (at least the type that use 'apps') has almost no use whatsoever in an offline context.

      I might want to compose a document in my word processor on my desktop or laptop maybe even just type up a long complex E-mail, I won't ever be doing that on my tablet or phone.

      Honestly about the only thing I see people do offline on tablets and phones is game, and the vendors are doing everything they can to tie even basic single player puzzle games to some kind of network based service.

      Especially if I have one which exercises the CPU since implementing it s a webpage will kill the performance.

      Ah but will it at least on IOS and Android are large large portion of non-game apps are really just thin wrappers around web as it is. Frankly Apps suck and make nosense at all most of the time. Why the hell do I want to go the app store, search for the 'the tire stores app', install it, disable the shitty alerts etc, and then run the app; all so I can browse tires. Which I will do at most about once a year for the two cars I own. It would be way easier to open the browser and go to 'm.[tirestore].com'.

      Every flipping business having their own app which is nothing more than a webpage anyway 90% of the time is aggressively stupid.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
  41. Re:so.... Firefox OS? by Zontar+The+Mindless · · Score: 1

    Speaking of badly-implemented... Guys, if you can't maintain a user session across subdomains, maybe you should skip the subdomains and just let your users stay logged in...? Nobody actually looks at URLs anymore in any event, right?

    ö_Ö

    --
    Il n'y a pas de Planet B.
  42. Re:Apps are just browsers in many cases by Zontar+The+Mindless · · Score: 1

    Then I have a bunch of shit in a folder on my home screen. (I'm looking at you, MS *and* Google.) I don't want that there, either.

    --
    Il n'y a pas de Planet B.
  43. Sigh, this gets trotted out every year by LordWabbit2 · · Score: 1

    Sigh, this gets trotted out every year, usually by a fvcking web developer who couldn't be bothered to learn anything else.
    The reason there are still apps is because they fill a very needed niche. Try write a web app that you can use out in the middle of nowhere without internet access, or worse intermittant or VERY SLOW internet access. Ontop of that the web app has every framework and kludge thrown in to make it look like an app and what you get is a very very frustrated user, who will drop your web offering and go with someone who bothered to write an app.

    --
    There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
  44. Re: so.... Firefox OS? by Slashdot+Junky · · Score: 1

    I bet the mainstream app user is a mindless consumer of bandwagon apps. They install too blindly and, likely, without a true need. I am not in the add-on App camp for the most part. Android gets Firefox. For work, it also gets a vendor's ticket management app. For my, CM Nook, it got Firefox, Pandora, and the Nook Reader. My iPhone 5S has no add-on apps.

    --
    .
    Landfill Mining Co.
    Managing the (Un)natural Resources of Tomorrow
  45. Re:so.... Firefox OS? by johanw · · Score: 1

    They failed too and are already forgotten.

  46. It's likely to happen - how ever strange it seems by Qbertino · · Score: 2

    I call it the first law of IT: Toys win.

    When the PC came out it was a toy. Litterally.
    3 decades later its the only computer architecture worth talking about.
    Why? Its open and there is no single entity controlling it.

    Linux was a toy back then. Now it owns everything in computing that isn't controlled by marketing.
    And it secretly owns those rebranded platforms like android, which is Linux in disguise.

    LAMP is a toy. A toy everyone can use. Now it runs 70% of the web.

    WordPress is a toy. A toy everyone can use and tinker with. It runs 25% of the web.

    Technolog wise the web stack is a silly joke. But it just killed a technology dead that was something like 15-20 years ahead and orders of magnitude less shittier: Flash. Why? Proprietary and controlled by Adobe, a company interested in profit, not technology. If Adobe would've FOSSed Flash at the beginning of the touch revolution, it would've stood a chance. Now it's dead.

    What's remaining of the web is technology that was hip 20 years ago - you know, that time when XML was better than anything else, because at least it was a standard. ... Until HTML came along that is.

    The Web is a toy. But it runs everywhere and my grandma can learn to write for it in 10 minutes. Its a slow-as-hell buggy meta-plattform - but its the only one we've got in a time where fragmentation - especially in the mobile space - is rampant.

    My Website from 15 years ago will still render on todays browsers, even on mobile. On screens and platforms we didn't even dream of back then. Try that with a windows or mac app.

    The Web is a toy that is laughed out of the room, especially here on slashdot. It's laughed out of the room like the PC was in the early 80ies.But
    , as a toy, it's open and everyone can tinker with it. That's why it will win.

    So yes, native mobile apps will most probably become a specialty and web-tech-based apps the norm.
    Toys win.

    --
    We suffer more in our imagination than in reality. - Seneca
  47. Re: so.... Firefox OS? by Lunix+Nutcase · · Score: 1

    Ooooh boy. We got ourselves a genuine Internet Badass here!

  48. Re:so.... Firefox OS? by Lunix+Nutcase · · Score: 1

    And we all know there are no badly-implemented websites. No, they are all well-architected and coded to perfection. *rolls eyes*

  49. Re: so.... Firefox OS? by beelsebob · · Score: 1

    So what you're saying is "you could do all the things you do today, if you bought massively more powerful hardware, because I'm too lazy to write code that runs efficiency"

    The fact is that native code, with manual (or compiler inserted) memory management will always be significantly more efficient than crappy web apps and their interpreted (even JITed), garbage collected mess.

    You shouldn't be saying "Maybe phones with 3GB+ RAM will change this" but instead "Hey, why does my code require 3GB of RAM to run even half reasonably, when that other guy's code runs natively on a device with 1GB of RAM"

  50. Let me know when there are web standards by jtara · · Score: 1

    Now, like Rip Van Winkle, going to sleep for 25 years, let me know how it worked-out when I wake up!

  51. Yes by jellomizer · · Score: 2

    Most mobile apps... Actually most apps, are a basic CRUD based system (Create Read Update Delete). Apps are really only really needed for the following.
    1. Interface Performance Matters: This includes games, graphics edits, sound editing, CAD. This is where the UI will be doing a lot of work to provide a rich experience... Most Apps give you data and sit there awaiting input. Web Standards may be implemented well, however sometimes you just need the low level.

    2. Additional User Input/Output. Needing that new device camera, motion detector, special screen that takes different input Or outputting to a specialized device. Web Standards cannot be adapted to handle new technologies.

    3. Non-Default security. Sometimes those security warnings will get in the way and those apps can bypass them.

    However that is only a small portion of the apps.
    Most mobile apps are just a wrapper to a web site, or send XML, JSON to a server and work just like a browser. So with proper web standards implemented and optimized for the devices they are installed on most of your apps can be useless.

    Web Standards is the reason why we can function very well with Linux, Macs, iOS, Android... Comparing say 20 years ago (1996) where most applications were Installed on the PC, and these apps were for trivial things, that have been moved to web sites. So we can function rather well in 2016 with just an web browser as the only application.

    We would only need applications for high end work.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  52. Re:The Twilight Years of the Web Browser. by doom · · Score: 1

    westlake wrote:
    Platform lock-in is a geek obsession. Everyone else just makes their choice and settles in comfortably.

    Right, just like adblock. Only a real nerd would care about something like adblock right?

    Geeks tend to obsess about problems early, the mugs always try to pretend it doesn't matter until they get fucked over by them.

  53. talk about broken by doom · · Score: 1

    Well, that's about it for me today, but before I run off I'd just like to say how absolutely hilarious it's been chatting about the virtues of the web platform using a web site that's hideously broken. It keeps logging me out, and then when I log back it throws away my context and makes me manually search for where I was again... then I start moving faster to try to post a reply before I get logged out again and I start getting the "Slow Down, Cowboy" message (a blast from the Beebop 90s, that is...).

  54. Same old debate by Desert+Leap · · Score: 1

    The usual X-Windows versus Client-Server architecture we've been debating for years. How smart and how local do you want your UI to be?

  55. Re:so.... Firefox OS? by Nethemas+the+Great · · Score: 1

    The 100% Internet availability requirement makes it a tough sell to many end-users. The PITA of developing on the platform makes it a tough sell to developers but most especially their management. Lack of reasonable access/support to client local assets removes it from consideration for a variety of purposes unless you're willing to sacrifice a clean implementation.

    HTML5 can be reasonably leveraged for some--generally simple--purposes. However, even if it's possible to satisfy the technical requirements for a project with HTML5 kit it's not always the most appropriate choice. Said another way, yes, it is technically possible for master craftsmen using simple hand tools to precisely and accurately work with wood, metal, stone, etc. to produce refined, sophisticated works. Why however would anyone sign up to such a plan when a far more abundant labor pool, with significantly less training can hit a few buttons on a CNC machine to produce equivalent or better works, more consistently and in a fraction of the time? There's a reason for multiple tools in the toolbox, not everything is a nail nor should it be treated as such.

    --
    Two of my imaginary friends reproduced once ... with negative results.
  56. Re: so.... Firefox OS? by Slashdot+Junky · · Score: 1

    Ooooh boy. We got ourselves a genuine Internet Badass here!

    Yep! Life here is pretty good as a genuine Internet bad ass! The hands of people worldwide click and tap uncontrollably just from the fear that I will might engage them! I was an Internet bad ass long before all those mindless bandwagon hoppers started installing apps for everything under the sun on their mobile devices.

    --
    .
    Landfill Mining Co.
    Managing the (Un)natural Resources of Tomorrow
  57. Re:Apps are just browsers in many cases by BarbaraHudson · · Score: 1

    Sure sounds a lot like an app drawer to me.

    Sure sounds like Windows 3.1 Presentation Manager to me.There seems to be not much new under the sun nowadays.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  58. Re:so.... Firefox OS? by BarbaraHudson · · Score: 1

    I DON'T HAVE to download a new version of the app - I can keep the old one just fine. With the web app, every time they change it, you are forced to download new crap, and you run the risk of losing functionality that worked in the previous version because someone had a brain fart or needed to make changes to justify their salary.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  59. Re:Program Manager Barb (progman.exe) by BarbaraHudson · · Score: 1

    You're right- my mistake :-)

    I remember when I saw Windows 95 at one of the previews, and I turned to the guy next to me and said "Didn't they just rip off OS/2 2.1?" Looked pretty much the same to me - and him. Some of my co-workers took the free Win95 and Microsoft Office cds - I didn't because who wants to waste their time on a product that, at the time, wasn't really ready for prime time? Should have taken them and given them to one of my sisters. My mistake.

    And no, haven't seen predestination, though I'm sure it's good. Maybe one day ... and everyone who's logged in knows what way it applies to me - I'm not shy about the whole sex change thing, but thanks for the thought :-) TTYL

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  60. Re:Ready to laugh @ BarbHudson everyone? by BarbaraHudson · · Score: 1

    First, I haven't had mod points in years - not since I took a break because I could no longer see well enough to read or do a lot of other things.

    Second, transsexuality is no longer recognized as a disorder. What IS recognized is the problems caused by society's non-acceptance that lead people to, for example, kill themselves. But that's okay - by your posting, all you're doing is showing that you are out of tune with current thinking, both of the medical community and the larger population. And of course, I wouldn't dream of not allowing you to say it, even if it is wrong.

    Third, you keep referring to May of 2010 (if people follow the links enough) for the whole "posting anonymously" bit. Why is it okay for you to do it and not others? Unlike you, I haven't posted anonymously except for one time, on my phone, when I accidentally did so.

    Fourth, PTSD and the ensuing major depression disorder are nothing to be ashamed of. I admitted to it because I didn't like the way that commenters were piling on attacking the person in an article about their mental problems.

    Obviously, when people like you feel that attacking others based on things they have no control over, there's more need to talk about it. Nobody asks to be a transsexual, nobody asks to have PTSD, nobody asks to have Major Depressive Disorder, just like nobody asked to choose what colour, ethnic group, or parents they could have.

    So consider this post a Public Service Announcement, because there are others out there struggling with the same or similar problems, and all you're doing is making it worse for them, not me. BTW - 4% of the population is diagnosed with a mental illness (temporary or permanent) every year. 25% of the population has at one point or another been mentally ill. Many people don't get treatment because of attitudes like yours - but times are changing. We don't stigmatize people who have juvenile diabetes, a physical illness that nobody asks for, we don't stigmatize rape victims any more, and we shouldn't stigmatize people for mental illnesses either. :-)

    As for hosts, I really don't care any more, and I made my reasons clear why years ago. Jangle bait in front of me all you want, I won't take the hook. It's really a non-issue in 2015.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  61. Re:Barb, read... apk by BarbaraHudson · · Score: 1
    If you go up-thread, you might notice that I was not the one who mentioned APK. I was replying to this post:

    Slashdot is definitely moderated. Not just by users, but by real actual moderators. Lets take a great example: apk. He has a copy-paste "host engine" spambrick that he poops out sometimes dozens of times per thread. But is this promotion really spam? It's topical (he won't post it unless someone is talking about ad blocking or security), it's not commercial (he wants to spread awareness, not sell you something), and he'll absolutely throw down with anyone who wants to debate.

    Yet, his posts are DELETED by the moderators. I don't see anyone too upset about this- he obviously shits on forum etiquette by posting the same general promotion/debate brick of text. But is that really free speech? It's some kind of border. He's not selling penis pills, he's trying to help for real. But if you look up the threads where he debates people now, you'll see most or all of his posts deleted- that means someone had to make the call.

    The poster claimed that your posts are being deleted. I pointed out that they are not (at least i my experience). I am NOT the one who brought you up as an example or dragged you into this argument. So why are you attacking me instead of the original poster? Maybe you're too quick to take offense where obviously none was intended.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  62. Re:Barb you started it w/ me, proof is your words by BarbaraHudson · · Score: 1

    Hey, you were doing it to me, but when I told people to do the same to you .... whah whah whah??? Everyone knows you post pretending to be other ACs. You're still doing it even today. And I only got involved recently in ONE reply that someone had already mentioned your posting habits in.

    So really, how is saying this ...

    And I've been known to change my views or admit I was wrong on-line. It's no big deal - it's just the internet. As an example, we're no longer fighting because there's more to life, he's an okay guy on other topics, and what the heck, if you don't like it, just don't browse at -1 :-)

    .... any sort of insult?

    I did not "drag you into this" or "stab you in the back." I've already said I'm sorry if you took it that way, but I don't see how saying you're an okay guy on other topics is an attack on you.

    Why don't you link to the original post, where I told people to do to you the same thing you were doing to others?

    You claim that I'm damaging your reputation, but if you want to find the real source, you might want to look in the mirror instead of attacking someone who defended you by saying you were an ok guy in other respects, and that if someone doesn't like what you post, they should stop browsing at -1.

    Keep on fighting - all you're doing is proving I was wrong about you being an ok guy in other respects. I still don't get why you're attacking me instead of the post I was replying to.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  63. Re:Prove it Barb... apk by BarbaraHudson · · Score: 1

    Prove it? I can't even prove that it's you who's posting the above. And neither can you. That's the problem with ACs, so please don't be disingenuous.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  64. Re:If you can't back it? Don't speak it... apk by BarbaraHudson · · Score: 1

    Can you prove you made any of the posts you made, including the one I'm replying to? See the problem? :-)

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  65. Article starts out with false assumptions by rhyous · · Score: 1

    This article starts off with false statements such as:

    "There's a litany of problems with apps."

    Is there really? Let's look at the problems this author has mentioned:

    1. There is the platform lock-in

    This doesn't have to be the case anymore. With Xamarin and other tools, there isn't a platform lock-in. You can code once and deploy to iOS, Android, and Windows Phone, OS X, and Windows Desktop.

    2. The space the apps take up on the device.

    This is a short term problem that will be resolved by enhanced hardware. In two or four years, we will likely have phones with close to 1TB.

    3. Updating apps is a pain that users often ignore, leaving broken or vulnerable versions in use long after they've been allegedly patched.

    Really? All my apps auto-update. I get prompted to update ones that require manual updates to re-approve because they are using a new feature. Seems pretty simple to me.

    4. Apps are also a lot of work for developers—it's not easy to write native apps to run on both Android and iOS, never mind considering Windows Phone and BlackBerry.

    Again, not true. Check out Xamarin and similar tools. If you think html5/CSS/JavaScript is easy in comparison to compiled code, you probably don't have enough experience with the many problems due to different browsers and different devices. Even with standards, the way the standards are implemented are often different.

  66. Re: so.... Firefox OS? by MichaelAlexanderSavi · · Score: 1

    Actually, I my brother attends a school where ChromeBooks are mandatory.