Earlier quoted context omitted.
> iOS SDK forbids one even to build any other browser legally Really? Can you provide a link? > Are there any alternatives way to build code for iOS? http://iphonedevwiki.net/index.php/Compiling_iOS_application... No restrictions there.
I researched it a while ago, may be the SDK license changed since then. That's what I found then: License: http://www.wired.com/images_blogs/gadgetlab/files/iphone-sdk... Relevant parts (emphasis in italics): ----------------------- 3.3 Program Requirements for Applications Any Application developed using this SDK must comply with these criteria and requirements, as they may be modified by Apple from time to time: ..…
Firefox for iOS on GitHub
61–70 of 145 posts
Re: Firefox for iOS on GitHub
#62It's a bit sad that Firefox is caving in and shipping a browser using WKWebView. The rationale is that by using WKWebView they now get Nitro, and they have to "go where the users are" -- but a few years ago, it was a lot less clear that Android would be more prevalent than iOS. Also, iOS seems like a fairly hostile environment for 3rd-party browsers since it's not possible to change the system browser -- that's proba…
If they use WKWebView I'm not even sure they can implement the features of a plain old browser, never mind include addons/extensions.
Re: Firefox for iOS on GitHub
#63Earlier quoted context omitted.
I researched it a while ago, may be the SDK license changed since then. That's what I found then: License: http://www.wired.com/images_blogs/gadgetlab/files/iphone-sdk... Relevant parts (emphasis in italics): ----------------------- 3.3 Program Requirements for Applications Any Application developed using this SDK must comply with these criteria and requirements, as they may be modified by Apple from time to time: ..…
I think you are splitting hairs. What would be the point of "legally" allowing you to build an app that could not be submitted to the App Store? The only way to distribute it would be to "illegally" jailbroken devices.
Simple, you can use it personally, or for example submit it to Cydia or any other place without Apple's censorship. Just post it as a download after all. There is nothing illegal in distributing for jailbroken devices.
But that's really irrelevant. The license here doesn't even get to that part - it forbids you to build the browser, regardless of any of your further plans how to use or distribute it. It's completely sick.
Re: Firefox for iOS on GitHub
#64That said.. As far as I understand the 'real meat', the engine, is now webkit. Which defeats the process for me. The UI was always what Firefox was lacking in and even the very latest design decisions are - well - not quite my cup of tea at least and potentially questionable.
I would like to understand what Mozilla gains here (if this is mostly a 'skin' around webkit/a web view control) and why iOS users would install it (I'm on Android - dipping my toes into FirefoxOS every couple of weeks).
Edit: Thanks for reminding me of Sync as a great use case for a Firefox browser, even if it's using a different engine.
Re: Firefox for iOS on GitHub
#65I'm glad Firefox is coming back to iOS. I remember they used to have a similar Safari wrapper supporting sync, but they must've gotten rid of it.
It's still a Safari wrapper with sync support. Not sure what they'll call it yet. I really hope they don't just call it Firefox since it definitely isn't.
Re: Firefox for iOS on GitHub
#66Earlier quoted context omitted.
I feel like whenever I read discussions about this on HN it's all about the JS engine. Chrome was on webkit but used V8. And unless something has changed all non-safari browsers and webviews use an inferior JS engine. Edit: (Something has changed, WKWebView now has the Nitro JS Engine, cool beans)
Also, when Chrome was launched, it was the only browser with a multi-process approach to a multi-tab browser world.. Also their approach to threads were right from the beginning, and that converge into a awesome no-lock and no-glitch browsing experience.. After that, every other browser followed them. So, to be fair, Chrome was much more than V8 (which was also a part of its voodoo)
Nope, IE8 was: http://blogs.msdn.com/b/ie/archive/2008/03/11/ie8-and-loosel...
Re: Firefox for iOS on GitHub
#67I'm a Mozilla and Firefox fan, running Aurora on my desktop, tablet, mobile. Love the project and it's the best browser out there for me. That said.. As far as I understand the 'real meat', the engine, is now webkit. Which defeats the process for me. The UI was always what Firefox was lacking in and even the very latest design decisions are - well - not quite my cup of tea at least and potentially questionable. I wou…
Re: Firefox for iOS on GitHub
#68I'm a Mozilla and Firefox fan, running Aurora on my desktop, tablet, mobile. Love the project and it's the best browser out there for me. That said.. As far as I understand the 'real meat', the engine, is now webkit. Which defeats the process for me. The UI was always what Firefox was lacking in and even the very latest design decisions are - well - not quite my cup of tea at least and potentially questionable. I wou…
On iOS you use WebKit or you don't make a browser. They don't have a choice. As for why you would install it, probably sync. If you use Firefox on desktop presumably you can now access your bookmarks, history etc on iOS.
Re: Firefox for iOS on GitHub
#69Re: Firefox for iOS on GitHub
#70I'm a Mozilla and Firefox fan, running Aurora on my desktop, tablet, mobile. Love the project and it's the best browser out there for me. That said.. As far as I understand the 'real meat', the engine, is now webkit. Which defeats the process for me. The UI was always what Firefox was lacking in and even the very latest design decisions are - well - not quite my cup of tea at least and potentially questionable. I wou…