Vivaldi for iOS
-
@luetage said in Mobile Vivaldi for iOS:
@altcode Vivaldi's UI on the desktop is based on web technologies (html, js, css), this cannot be moved to mobile afaik. iOS apps are programmed in swift and android apps in java.
Qt apps work fine on Android as well.
-
I have been using Vivaldi on my Mac for the past six months and absolutely love it! However, without a syncing mechanism for bookmarks and tabs I'm leaving the boat, too.
For me, A webkit browser with a vivaldi skin for the sole purpose of syncing would be all I need. In my opinion their first browser wouldn't have to be blink based. I think it is more important to give people a completely functioning package in browser ecosystem before they port over tab stacking (although if they did release an ios browser with real tabs I'd be all over that), color customization, RAZER compatibility, etc.
Syncing is the single most important feature of Vivaldi I need. For the time being I am going to need to go back to Firefox. I'll keep an eye on Vivaldi status and come back when syncing is possible on iOS (If they really don't want to make a browser, at least make an app that will add bookmarks and history to Safari or something else. I'd stick with Vivaldi on desktop then.)
thanks Vivaldi team for all you do, Your browser is my favorite.
-
And here is something for those waiting for Vivaldi Mobile on IOS
Link where I shared:
https://twitter.com/Matti_Tech/status/1143933317831696384?s=19 -
As an early user of Vivaldi (since the beginning i believe) i was wondering at what stage is the developement of Vivaldi for IOS ?
THX
Dan -
@Mirivedan said in Mobile Vivaldi for iOS:
As an early user of Vivaldi (since the beginning i believe) i was wondering at what stage is the developement of Vivaldi for IOS ?
THX
DanConsidering the Android version isn't even an official release yet, not in any predictable time frame. Additionally, Vivaldi does not speculate on future release dates. The Vivaldi team is not large. Without producing a commercial product or pushing more invasive advertising, growth of the team and development of the product can't be done at the same pace as the other browsers backed by MNCs and heavy-handed advertising.
Developing a browser for iOS isn't as straightforward & easy as it is for Android with the code base Vivaldi has. So making an Android browser first was the logical move.
This is the trade-off Vivaldi users are willing to make. Given the limited resources of Vivaldi and their obvious commitment to quality, it takes a good bit of time to create the browser its user base expects. Let's not forget the patience we had to exercise for Vivaldi Android, this beta is barely a month old. Vivaldi rewards our patience with a stable browser that provides a unique level of flexibility & control.
-
@Mirivedan "Stage of development" would not be relevant, so far as I know, to Vivaldi on the iOS platform as yet. Jon has stated definitively that it is planned for the future, but there is absolutely no sign at the present time that any of the 20-30 developers have been peeled off from current projects to begin work on it. A strategy for its development (given that the browser engine code base has to be abandoned and another adopted) has been envisioned as possible, but there is exactly ZERO information available to testers ATM to indicate that a new team has been hired or existing team members have been reassigned, to implement that strategy.
-
@almarma It's almost 2020 ... is iOS made it to the roadmap at least?
Thanks for all the great work you've done so far! :-)) -
@integralsun I cannot imagine there are any spare resources to even think about pre-planning for this yet. Come back in two or three years if you're still using iOS by then.
-
@Pesala Even if @integralsun & @almarma are no longer iOS users in 2-3 years, this question has nearly 6,000 views, so plenty others will be & thus still stands as a legitimate request/inquiry.
Vivaldi's appeal being cross-platform speaks for itself. Why anyone supportive of Vivaldi's increasing success would discourage this demand is simultaneously being clearly unsupportive of future possibilities. -
@ndulgd I am not discouraging this request; just telling it as it is to avoid anyone having unrealistic expectations. I have followed Vivaldi's development from the beginning, especially the feature requests, of which there are currently 2,228.
Every user has his/her favourite things that they would like to see implemented. I know from what Vivaldi team members and insiders (like Ayespy) have said, that this one is not likely to happen any time soon โ there are too many barriers to it being done. I was being conservative in saying โcheck back in two or three years.โ See what Ayespy said above.
See also Mobile Vivaldi for iOS
-
@ndulgd The best way to find out where things currently stand regarding Vivaldi for iOS is to search the Internet for "Jon Vivaldi iOS"
Whenever @jon gets interviewed for an article about Vivaldi on Android, questions about an iOS version ALWAYS come up.... and this recent article is no exception: https://venturebeat.com/2019/09/09/vivaldi-web-browser-finally-arrives-on-mobile/
-
Hi There all
Do you intend to release a VIVALDI version for the Iphone Thanks
-
@JohnWJ6969 It's planned, but due to Apple's restrictive policies, it will not be allowed in the Apple Store unless it is completely re-written to use the Apple browser engine designed for iOS. So It won't be available soon.
-
When, oh when will there be an iOS/iPadOS version? I like the macOS version and have been a registered user with the complimentary email account for years now but because of the way I work I really need a browser I can sync across all my Apple devices. It is the only thing stopping me from making Vivaldi my default browser across all platforms.
-
@Gwen-Dragon said in Vivaldi iOS:
@Annerod A iIOS version is planned.
-
@bonetone I don't think it's particularly harder or easier on either platform. Vivaldi still has to create the UI for both and they already have a base to work from.
-
@poopooracoocoo said in Mobile Vivaldi for iOS:
@bonetone I don't think it's particularly harder or easier on either platform. Vivaldi still has to create the UI for both and they already have a base to work from.
It takes more work to develop a browser for iOS when you're a Chromium-based browser. Every browser has to do a rewrite to use the same engine as Safari, there is no ability to use to the same engine they are using on Android or the desktop. The Vivaldi UI on the desktop makes use of web-based technologies (html, css, js) and this cannot be used on iOS. Nor can the UI work from Android be used on iOS, the Android app is written in Java, while iOS apps are written in swift. They have to do everything over again, from rewriting the UI to even using a different engine. At least on Android, they could reuse some of the work they had done on the desktop.
Thus, it was logical to start with Android as an entry to the mobile browser space. This is the price Apple users pay for living inside the walled garden. There may be some benefits to being inside that wall, but there are also drawbacks.
In Jon's own words:
โThe priority at this time is Android โ we can reuse code on Android and utilize the same code base,โ von Tetzchner continued. โApple does not allow us to use the same code on iOS, so it requires a lot more work to deliver on that platform. We do hope, however, to provide an iOS version sometime in the future. Ideally that would be through Apple allowing us to reuse our code, but we aim to make it happen anyways.โ
https://venturebeat.com/2019/09/09/vivaldi-web-browser-finally-arrives-on-mobile/
-
@bonetone but there are already open source browsers for iOS. I know that the Apple iOS App Store doesn't allow web browsers that use another engine. I'm aware that Vivaldi would have to create a new UI for Android and another new UI for iOS. Chromium already has the UI for both platforms. I'm kind of curious as to what code they are reusing. Were they referring to the UI? Which parts of the UI?
(sorry for the really late reply, i meant to press send but time slipped away)
-
@poopooracoocoo Vivaldi uses no Chrome or Chromium UI code, and patches the Chromium engine to a fair degree.
That said UI code on iOS is completely different from UI code on Windows, Mac and Linux. It's written in a different language altogether. (Swift for iOS, and JS, HTML, etc. for other platforms)
-
@Ayespy ahh. I thought that Vivaldi for Android used Chromium UI code for the bookmarks, history and downloads pages. I also thought that Vivaldi used the grid tab switcher from Chromium. Thank you!