6 ms·
Building A Paid App For Firefox OS
- tdoggette 14y agoFinally, more app support for my WebOS devices! That wasn't sarcasm, I'm legitimately excited.
- davisr 14y agoI feel like Enyo, and WebOS itself, are really under-appreciated. I've built a few apps with Enyo, and it's an absolute treat to use. Plus, WebOS is still here -- I almost feel like people are actively ignoring it: trying to sweep it under the rug whenever its mentioned. Truthfully, I'll be sad if Firefox OS gains traction, because WebOS did all of this years ago.
- kumar303 14y agoWell, WebOS did it in secret and built their own walled garden of "web" APIs, sadly. That may or may not be why it never got traction. Either way, if you built a WebOS app then it won't run anywhere else today. With Firefox OS, Mozilla at least has used standard HTML5 everywhere that it made sense to. Granted, WebOS began its design a long time ago in web years.
- davisr 14y ago> Either way, if you built a WebOS app then it won't run anywhere else today. That's not very true. Any HTML5/JS app built for WebOS 3.0+ (when Mojo was depreciated, and Enyo brought in) can run in any browser; if it uses WebOS-specific API calls (most often used for notifications), then it can be wrapped in PhoneGap/Cordova and compiled for nearly any OS.
- kumar303 14y agoCorrect. Now you have a PhoneGab app not a WebOS app :)
- kibwen 14y agoAn interesting link buried in the article: http://www.macworld.com/article/1167677/hacker_exploits_ios_flaw_for_free_in_app_purchases.html http://www.macworld.com/article/1167677/hacker_exploits_ios_... Does anyone know if Apple has addressed this yet? In any case, it will be interesting to see if Mozilla can pull this off. When I download an app, isn't it just Javascript? What's to stop me from just diving into the app's source and putting in `function is_this_a_valid_app() { return "yep"; }` ?
- dubcanada 14y agoApple has fixed "exploits" for iOS free stuff every single version they've released. If Mozilla becomes big the same thing will happen, and more of it. Apple stuff is compiled and at least sort of encrypted. Mozilla stuff is pretty much free game.
- chrismorgan 14y agoCounterpoint (with no particular value): encryption standards are publicly visible; does that make them less secure than proprietary and concealed encryption techniques?
- dubcanada 14y agoI would have to say yes. It's a lot easier to break something that is has the code/methods available then play the hex guessing game. But having an application which is 100% HTML/JS/CSS/Interest other scripting language here. Without any ability to opcache or byte code it and encrypt it. It's not going to take much to crack it. If they somehow found a way to compress+encrypt the HTML/JS they may be able to make it at least a little bit more challenging. But that would take a lot of effort.
- chrismorgan 14y agoThe likes of Java can be decompiled just as successfully as JavaScript. Minification and obfuscation are quite common for web apps already. It's done for current phone apps, and it will be done for the new breed of web apps in just the same way.
- pnathan 14y agoThis is pretty exciting. Being able to have an open marketplace without lockdown is... erm... well. It's a refreshing change from the iOS land and I hope to see more in this direction. At any rate, I am starting up a project that I am hoping to sell on the FF Marketplace. It's going to be a trip (never done app development before!).
- Xuzz 14y agoCounterpoint: as a developer, this looks awful. For iOS: write an app, set a price, release it. For at least 90+% of potential customers, they have to pay for it. Piracy requires modifying the device in a way that Apple blocks. For Android: write an app, set a price, release it. Anyone can easily pirate it, but it's still easiest to buy it instead. For Firefox OS: write an app, set a price... then write a web service to do receipt checking? Integrate a library to verify purchases? That's a lot of critical code I now have to maintain, and is easy to get wrong. And my app now depends on having a server available (either mine or, it seems, a third party) to verify. And, of course, it's all JavaScript: patching it out is trivial for piracy. I guess it's more "open" or something, but it just seems like more work for the same result.
- pnathan 14y agoMy tentative design for the FFOS app I'm working on is to have only the rendering code delivered; the rest is requests out to my web server, which then frontends all the interesting stuff. In other words, it's going to effectively be a web page with some strange Javascript.
- dubcanada 14y agoThat's an interesting solution. I wonder how delivering an entire application on launch will affect load times, speed, bandwidth usage, etc.
- pnathan 14y agoHonestly, I don't think it's going to be a problem... the magic is all going to happen on the backend: the frontend is going to be (relatively) simple code. Essentially just enough to call out to the backend and render the results. The entire thingie is going to be simple. I'm not sure how Mozilla is going to handle users, etc, and how I can get that information transferred into my system so that users can get into their account from a regular web browser as well as the web app from their device. I need to figure that out, but I'm not there yet. The sales & user accounting systems are probably going to be 3-5x more troublesome than the actual program.
- slajax 14y agoI definitely appreciate the portability and open standards that seem to be at the core of this product. My startup also runs an app store like product and we decided to focus mostly on web for these same reasons. Portability and open standards are amazing assets that we are not willing to give up and I'm REALLY interested in the process and approach Mozilla is taking to use the same benefits in the mobile market. Mozilla is on the comeback! Watch out tech giants!
- slajax 14y agoI definitely appreciate the portability and open standards that seem to be at the core of this product. My startup also runs an app store like product and we decided to focus mostly on web for these same reasons. Portability and open standards are amazing assets that we are not willing to give up and I'm REALLY interested in the process and approach Mozilla is taking to use the same benefits in the mobile market. Mozilla is on the comeback! Watch out tech giants!
- small_timer 14y agoI want to like Mozilla, really, but why do they seem unable to put out a press release that doesn't contain gratuitous lies or misinformation? (The last Mozilla PR release I read was also misleading: http://news.ycombinator.com/item?id=5128924 http://news.ycombinator.com/item?id=5128924 ). there is a key difference: it does not lock you into Mozilla or lock you into your Firefox OS phone How is this true in any meaningful way? I look down this list of APIs: https://wiki.mozilla.org/WebAPI https://wiki.mozilla.org/WebAPI and I see many many things that are FirefoxOS only, and are not planned to be made available for other platforms. If they want to say that FirefoxOS can display 'standards compliant' web pages then yes, great, but so can every other OS to some degree (web 'standards' are a moving target and Chrome and Safari have broadly comparable standards compliance). If FirefoxOS is to be truly standards compliant that means it will be unable to do a single thing that other platforms can't also do in their respective standards compliant web browsers (and if no other browser implements it then it's not much of a standard). So where is the additional value from FirefoxOS? It's just an OS that is by definition less functional than every other OS. Before anybody chimes in pointing out all the misleading PR from Apple and Google and Microsoft, yes I'm aware of that, but they are for profit companies and don't claim to be working for the betterment of mankind. If to compete with them you also have to coat everything in a glaze of PR bullshit then how are you any better than them, other than that your bullshit has a slightly different consistency that makes it easier to swallow for some people.
- kumar303 14y agoI think it's a fair argument to say that one is locked into Mozilla today with our receipt protocol. However, we've designed it from the ground up to work in a decentralized manner so that other marketplaces can participate. This is the exact opposite of iOS (and to an extend, Android) where the business model relies on some premise that the customer will be locked into the platform at the minute she makes a purchase. The point of this article was to start getting others to help us make it work for them. There is a chicken/egg problem so someone has to start somewhere. Compare this to Chrome OS; they have not made an effort at creating a decentralized receipt format. To validate a paid app your only option is to talk to Google's web service. https://developers.google.com/chrome/web-store/docs/check_for_payment https://developers.google.com/chrome/web-store/docs/check_fo...
- thecombjelly 14y agoI think the open web-applied to smartphones-will be what the entire smartphone market eventually arrives at. Mozilla is playing the long game and doing a lot of extra work and will go through a lot of issues that they wouldn't if they made another walled garden OS and marketplace. One of the reasons that the web is so popular for developing apps is its openness and prevalence. The more momentum firefox OS builds, the more pressure will be put on other phone OS ecosystems to follow suit, especially if you can use firefox within other ecosystems and it integrates well with their marketplace and apis. When that happens, it will be increasingly hard to justify creating a device specific app when you can cover every device with one webapp. This will be an exciting project to watch.
- brianbreslin 14y agoHow hard is it to transition an add on for Firefox to an app for Firefox os?