Opera Mobile for iOS?

  • Does anyone know if Opera are planning to port the new Opera Mobile over to iOS? I know there is Coast already, and I really did try to like it, but I think I prefer the Mobile one (I have an Android phone and an apple tablet).

  • Apple does not allow alternative rendering engines on iOS.

  • I get kind of confused with these all of the different browsers in android. For my android tablet, I'm using Opera 20.0.1396 (which is similar to the desktop Opera), It has the discover feature and the speed dial where you can create folders. I believe that's called, Opera browser for Android," which is different than the Opera Mobile Classic. So when nattrill refers to Opera Mobile, I'm not sure if he's referring to the Opera browser for Android, or the Opera Mobile Classic.

    I also have an IPAD, and have tried the Coast (but it seems slow), and I prefer the Opera browser for Android (version 20.0.1396). Among other things, I can essentially bookmark more through the speed dial (by creating folders), than I can with the Coast, which has limited pages for space. And this Opera browser for Android seems faster than Coast.

    So my question is like nattrills (maybe the same :) . . . Is Opera planning to move Opera browser for Android to the Ipad.

    I'm not sure I understand sgunhouse's comment, that Apple does not allow alternative rendering engines on IOS.

    Now my understanding is that Coast does not use Opera’s server-side rendering service and relies on Apple’s own built-in rendering engine instead." Now the Ipad also has an Opera Mini. I don't know what rendering engine that uses, but I'm assuming it's not the Apple rendering engine (that Coast uses). So doesn't that create a conflict of rendering engines. I think the Opera browser for Android use "Webkit." Aren't Opera Mini and Coast different/alternative rendering engines. I'm not sure I understand the alternative engine that makes Opera for Android not do-able, when Opera has Coast and Opera Mini on the Ipad. Unless the Apple rendering engine for Coast doesn't count as a conflict (Apple always blesses Apple :), and the problem is that Opera browser for android has a different rendering engine than Opera Mini.If that's the conflict, I"d say, drop the Mini, and just go with Opera browser for Android.

  • So my question is like nattrills (maybe the same :) . . . Is Opera planning to move Opera browser for Android to the Ipad.
    I'm not sure I understand sgunhouse's comment, that Apple does not allow alternative rendering engines on IOS.
    Now my understanding is that Coast does not use Opera’s server-side rendering service and relies on Apple’s own built-in rendering engine instead." Now the Ipad also has an Opera Mini. I don't know what rendering engine that uses, but I'm assuming it's not the Apple rendering engine (that Coast uses). So doesn't that create a conflict of rendering engines. I think the Opera browser for Android use "Webkit." Aren't Opera Mini and Coast different/alternative rendering engines. I'm not sure I understand the alternative engine that makes Opera for Android not do-able, when Opera has Coast and Opera Mini on the Ipad. Unless the Apple rendering engine for Coast doesn't count as a conflict (Apple always blesses Apple :), and the problem is that Opera browser for android has a different rendering engine than Opera Mini.If that's the conflict, I"d say, drop the Mini, and just go with Opera browser for Android.

    Opera Mobile Classic uses Opera's old proprietary rendering engine (known as Presto) and hence couldn't be ported at all. Opera Browser for Android uses the same rendering engine and javascript engine as Google Chrome, the engine is known as Blink. While this is related to the Webkit engine used by Safari, I'm not sure how much work it would be to convert it. I don't work for Opera and can only tell you whatever the developers have said publicly.

  • Opera Browser for Android is the closest to the Desktop Opera, so it might make some sense to do something like that with the Ipad, in addition to Coast (since that's a totally different look). Anyway, I just wanted to get a sense of whether there was a problem à la alternative rendering engine, and it sounds like there may not be.

  • Coat is a full browser and uses the existing engine on iPad, rather than being a "thin client" relying on rendering being done on our servers instead of on the device.

    That said, whether there will be a version of Opera Mobile on iOS remains to be seen.

  • @lem729, yes that was what I was asking. 'Opera Mobile for Android' was what I men't by Opera Mobile (the others being Opera Mini and Opera Classic). Hence 'Opera Mobile for iOS', because you wouldn't call it 'Opera Mobile for Android for iOS'... :)

    Anyway, I'm using chrome for the ipad, which I'm pretty sure uses webkit. I think they all use webkit except for Opera Mini, which got an exemption on the basis it was doing server side rendering, so it wasn't technically a 'browser', but an app that linked to Opera's servers.. Something like that anyway.

    As it is, since webkit and blink were until very recently the same thing, and Chrome (for iOS) is using webkit, and Coast is using webkit, I wondered if Opera have plans to port the 'Opera Mobile for Android' user interface to iOS, also using webkit? The answer is probably 'no', but I thought I would ask anyway.

  • It would make sense that they consider it because "Opera browser for android" (what you call, nattrill, "Opera Mobile for Android") is very close to the current Desktop Opera.It might even perhaps help popularize the desktop Opera.

Log in to reply
 

Looks like your connection to Opera forums was lost, please wait while we try to reconnect.