Vivaldi for iOS
-
@altcode large parts of browser infrastructure (session context, local storage, site features, cache, keyboard/mouse input) are reused as well.
Sometimes causing problems with special user input (gestures/shortcuts) and limits to features (private tab). -
I think the answer is that it will not happen.
@Ayespy said in Vivaldi for IOS/Android.:
You can't make a browser for IOS period, unless you build it on Apple's version of WebKit - which would mean starting over altogether. The Android version has been started. But never say never. It only took Opera something like 9 years to build a browser that Apple would accept into the Apple Store.
If someone from the Vivaldi Team thinks it could happen one day, no doubt they will remove the "Will not do" tag, but I would not like anyone to have their hopes raised.
Never say "never," but I think for now, one should assume that it will never happen.
-
@Ayespy said in Vivaldi for IOS/Android.:
It only took Opera something like 9 years to build a browser that Apple would accept into the Apple Store.
A few things that I find wrong with that statement:
- The iPhone/iOS was not unveiled until 2007.
- The iOS app store was not launched until 2008, so third party apps were not possible before hand.
- Opera released a browser for iOS in 2010, so in truth, it only took Opera 2 years to build and release a browser for iOS once they were able to.
@pesala said in Mobile Vivaldi for iOS:
If someone from the Vivaldi Team thinks it could happen one day, no doubt they will remove the "Will not do" tag, but I would not like anyone to have their hopes raised.
Never say "never," but I think for now, one should assume that it will never happen.They have said countless times on Twitter that iOS is not a priority, it is a long-term project, and that it is more tricky. Notice how they've never that it will never happen.
-
@altcode said in Mobile Vivaldi for iOS:
Opera released a browser for iOS in 2010, so in truth, it only took Opera 2 years to build and release a browser for iOS once they were able to.
You are assuming that they did not even start building it until the iOS app store opened. That is like saying they did not start working on Vivaldi Mobile until they opened this feature request category for Mobile.
On Wikipedia it says:
A project to port Opera to mobile device platforms was started in 1998. Opera 4.0, released in 2000, included a new cross-platform core that facilitated creation of editions of Opera for multiple operating systems and platforms.
I removed the tag in the light of the comments on Twitter.
-
@pesala said in Mobile Vivaldi for iOS:
You are assuming that they did not even start building it until the iOS app store opened.
I am. After all, no one other than Apple could develop an app for iOS before 2008; there was no tools to do so, let alone a platform to release and install apps in iOS.
Furthermore, I found an old interview with Jon on Tetzchner from the NYTimes that states that Opera started development as far as 2008, but stopped due to old restrictions on iOS: https://bits.blogs.nytimes.com/2008/11/03/why-you-will-not-see-opera-on-your-iphone/
On the article it says:
He replied that in fact some Opera engineers had started developing an iPhone version, but the company didn’t pursue it because Apple doesn’t allow products on the iPhone that compete with its own software — in this case, the Safari browser.
-
I do not use an iphone but do have a first gen iPod and and an iPad2.
Only Opera that works on them is OperaMini. They were working on something new but it came out (I couldn't get it) then fizzled away into the ether.
Whether or not Vivaldi wants to get into that environment is another question.
As for Android, they have repeatedly said one will be developed. -
@pesala said in Mobile Vivaldi for iOS:
I think the answer is that it will not happen.
Oh man
Well, thanks for all the answers on this thread everyone, having Vivaldi on iOS seems like something complicated, as they will have to redo everything, because Chromium is not available in the App Store. I realize this now, and I want to thank everyone for telling their thoughts. For now (And the next 10-20 years), I will have to use Opera Mini. -
Hey,
With more and more companies developing full-scale versions of their native desktop app for iPad (Ex: Photoshop), I would love to see Vivaldi do the same.
If you agree with me that the time is right, upvote this post to show the developers that this is something that we want.
-
@bendik Merged with existing feature request.
-
So reading this thread, it seems that Vivaldi will live in the future only at the Chromebook (or whatever google will evolve with Fuschia) enviroments, when x86 era starts fading out of the broad user market.
-
@xelarjona I don't understand why you would think that. Apple refuses to accept certain formats. Why does that mean Vivaldi would only be on Chromebook? The two data do not relate.
-
I understand Vivaldi on iOS will not be anywhere near the power of its desktop version. That said, while I did consider switching to Vivaldi on macOS it's an absolute necessity for me to be able to see what tabs I have open in desktop Vivaldi to read them on my iPhone when I'm on the move. This ability is so important for me (& I assume many others) that I prefer to use a less powerful desktop browser if I can't get the feature in the more powerful one. Chrome, Firefox, Opera all support syncing desktop tabs with iOS.
The other direction is simpler as with Handoff it's easy to open a page from iOS on a default browser on macOS.
-
@m_gol It's not gonna happen in the next couple of years. So what you are saying is you won't use Vivaldi until this is done. If you really like Vivaldi, I'd look into alternative solutions. You could for example write an apple script to open all open tabs from Vivaldi in Safari on execution. Safari should then have the ability to let you access those tabs on iphone. The apple script execution could be triggered by an application like Quicksilver, to make it fast and efficient.
-
@luetage The same problem exists for Android at the moment, therefore I took a look at it. I found a working script for this on superuser and pretty much used it 1:1 (source). This will open all current Vivaldi tabs in Firefox Developer Edition browser (which I have synced with Firefox for Android).
tell application "FirefoxDeveloperEdition" activate delay 3 set newTabURLs to takeVivaldiTabURLs() of me repeat with tabURL in newTabURLs open location tabURL delay 1 end repeat end tell on takeVivaldiTabURLs() set tabURLs to {} tell application "Vivaldi" repeat with w in windows if title of w is not "" then repeat with t in tabs of w set tabURL to URL of t set the end of tabURLs to tabURL end repeat end if end repeat return tabURLs end tell end takeVivaldiTabURLs
I made a shortcut for this script with Quicksilver and now it activates when pressing
Hyper-T
with Vivaldi open. Works pretty well. I guess there could be problems, if the other browser updates on restart, but then you just run the script again… -
I have been following Vivaldi for a while now, and have held off on switching due to one issue. No iOS app. I like being able to sync my open tabs.
I want to switch to Vivaldi, and id like to go ahead and do it now despite it not having an iOS app. But what I would like to know is if an iOS app is even being worked on? I don't want to switch only to find out that an iOS app is never coming. So im not asking about time lines, or release dates, im just asking is it being worked on?
-
@relink It's not being worked on, but it's been hinted at that one could come. Android version will come first.
-
@relink There has been sincere discussion behind the scenes whether it's practical to make Vivalid for iOS at this stage. An idea how it could be accomplished has been arrived at and agreed on. No actual development efforts are underway yet.
-
If it’s atleast being seriously discussed then I may go ahead and see if I can develop a work flow that would allow me to use Vivaldi on the desktop and another browser on my phone and tablet.
small rant
But I sincerely hope that the iOS app gets bumped up on the priority list. Mozilla tried sticking to their guns on the same issue at a time when Chrome was gaining speed and ultimately Mozilla ended up missing -probably- their last chance to gain ground over Google.People desperately want an alternative to Chrome and Google in general, but we also have lives and need to get things done. Unfortunately convenience often wins.
There is a moral argument to be made against Apples policy, however you aren’t hurting Apple, your hurting users, and potential users. Apple could care less, and it’s unlikely they will be changing their policy any time soon. But your users do care.
-
@relink It has nothing to do with moral arguments. It has everything to do with Apple pro-actively excluding browsers that don't switch to their engine, with all of the "start-all-over-again" work that entails. You literally can't put your browser on iOS unless you start from the beginning and build an entirely new one on the Apple engine.
-
I read the response to to hope that Vivaldi would come to iOS, I too hope it will happen so fingers crossed.