Be part of Vivaldi on iOS: Get the preview and give us feedback.
-
Vivaldi on iOS is ready to unveil its first look in its beta. And, we are as excited as you are. Want a chance to try it out? Read on to find out how.
Click here to see the full blog post
-
Congrats to everyone who made this possible!
-
This is huge news for the iOS users out there! Hopefully this helps catapult Vivaldi into more popularity!
-
Is it built on WebKit?
-
@notmalware Yes, because of Apple's rules it would need to be WebKit.
-
@RiveDroite I would never use apple device because of stupid restrictions to developers and users. But I'm still sure Vivaldi would be awesome on iOS!
-
@notmalware to be honest, me either. I used to be an Apple exclusive user, but back in 2013 switched and at this point I don't think I'd go back for the same reasons you listed.
-
@rivedroite: Are you 1000% sure of this? I know we're in the middle of WWDC by now but part of the EU's Digital Markets Act is that Apple would have to comply by 2024 to allow non-webkit browsers or face the consequences.
I'm sorry I don't quite know what the "Ambassador" badge you have exactly entails, I'm not sure if you have inside information from the Vivaldi team?
p.s. Rivendell is best
-
@Favna I am absolutely 100000% sure that the current release of Vivaldi for iOS is using WebKit and that as of this current time Apple doesn't allow any other web engines other than WebKit.
As for Ambassador, I don't have inside information no, but I am pretty up to date with these things
PS. Rivendell is indeed the best! As is all Middle-earth/Arda!
-
That's a verte good new
-
@Favna
Apple insists on only allowing browsers in 'iOS/iPadOS' that use their own proprietary 'Apple-WebKit'.
Not to be confused with the open source 'WebKit' used in Chromium/Vivaldi.They argue 'security'.
They think their 'macOS' is 'insecure' because Vivaldi with the open source 'WebKit' has been around for a long time.
This shows how 'Apple' ticks.
-
@ingolftopf: I am well aware of what Apple currently allows and denies, but that doesn't take away that the EU's Digital Markets Act is a fact that they will be subject to starting 2024. I recommend you read up on what it entails if you're not read up on it. For example this article: https://appleinsider.com/inside/ios-17
-
@Favna
That's why it's all the more incomprehensible why Apple has forced Vivaldi to use 'Apple-WebKit' all this time.I think they will continue to try to get around this.
Apple is doing it like Google.
-
@Favna
You can now use your own signature here in the forum if you wish. -
@Favna I'm going to assume you're here in good faith. The fact of the matter is that Vivaldi for iOS has been in development for a long time. Longer than the EU regulations have been announced. They're a small(ish) team, so since the work had already started using WebKit, it wouldn't make sense to switch for Chromium. Maybe in the future now that Apple is allowing non WebKit for iOS 17 (took Apple long enough!!)
Edit: though I did some searching online and it seems that the non webkit browsers for iOS 17 will only apply for the EU zone, not worldwide. If true, still anti competitive, because how many browsers are going to make two versions - one for EU and one for the rest of the world?
-
that is a big new
-
@ApolloTheLabby said in Be part of Vivaldi on iOS: Get the preview and give us feedback.:
@RiveDroite said in Be part of Vivaldi on iOS: Get the preview and give us feedback.:
@Favna I am absolutely 100000% sure that the current release of Vivaldi for iOS is using WebKit and that as of this current time Apple doesn't allow any other web engines other than WebKit.
As for Ambassador, I don't have inside information no, but I am pretty up to date with these things
PS. Rivendell is indeed the best! As is all Middle-earth/Arda!
Oh, when reading there is an iOS version in development I hoped that it would be after those new rules so there would be another engine. I am currently browsing with Safari on iOS (iPad and iPhone) ad the top right menu is a bit broken in it. So I guess when it is based on WebKit, it will also have those issues.
Too bad it is based on WebKit.
I'm guessing - though of course I don't know - that since Vivaldi has been developed on multiple platforms not based on WebKit... but they have recently had to modify the code to work with WebKit... that it would be quite an easy switch to using the same engine for all Vivaldi versions as soon as that is allowed.
-
My phone is ready
-
Yes, finally Vivaldi for iOS. I don't care that the browser is based on Webkit
-
super pumped! signed up for newsletter. already have TestFlight - send me an invite!