Mobile Browser Version

[SecretKnight]

Yes.... I want to use Mobile Vivaldi......

[SharpSA]

Yes! I waiting for Vivaldi for Android version!

[MattSolo45]

This post is deleted!

[Catweazle]

Yes, an Android version is needed, but I prefer to have some laziness, than to fight with a version full of bugs.
Haste is the number one enemy for developers.

[MattSolo45]

This post is deleted!

[Catweazle]

@MattSolo45
Of course it can be done, sure there are also plenty of users willing to use a preview as a "beta tester", but a smartphone of many, many users have only a limited amount of space and require a browser stable.
It is not the same as in PC version.

[Ayespy]

@MattSolo45 With unlimited development resources, one might try this. With only one or two developers assigned to the project, however, ten thousand new bug reports would not be particularly helpful.

[Catweazle]

@Ayespy said in Mobile Browser Version:

@MattSolo45 With unlimited development resources, one might try this. With only one or two developers assigned to the project, however, ten thousand new bug reports would not be particularly helpful.

True, Vivaldi only has a small team, about 40 employees, I think.

[MattSolo45]

@Catweazle @Ayespy I didn't want to sound like I'm not aware of the size of Vivaldi's band, but rather I meant the promises and declarations that were not fulfilled, and in this case, once there were some promises, then silence and so on and so forth. Instead of tweeting the user's answers to questions about this type of 2019, we are getting closer and closer, just around the corner, which we are reading this year practically from the very beginning, no matter what we say about that year. The user would at least like to see or read what the developers are working on rather than tactics based on these promises and silence, because in my opinion it is more rejecting than encouraging the users of Vivaldi than encouraging them. So either I'm thinking wrong or Vivaldi has to change something in advertising itself.

[Catweazle]

@MattSolo45 said in Mobile Browser Version:

@Catweazle @Ayespy I didn't want to sound like I'm not aware of the size of Vivaldi's band, but rather I meant the promises and declarations that were not fulfilled, and in this case, once there were some promises, then silence and so on and so forth. Instead of tweeting the user's answers to questions about this type of 2019, we are getting closer and closer, just around the corner, which we are reading this year practically from the very beginning, no matter what we say about that year. The user would at least like to see or read what the developers are working on rather than tactics based on these promises and silence, because in my opinion it is more rejecting than encouraging the users of Vivaldi than encouraging them. So either I'm thinking wrong or Vivaldi has to change something in advertising itself.

I understand you, but
1 - Vivaldi is still a youngster
2 - It has more built-in functions than any other
3 - It is, although there is no point of comparison in number of users with the other competitors, it is named at the same height as the big ones in the specialized press. This thanks to the dark eyecircles of the developers, which also have to deal with the suggestions of users who want even more functionality and their reported bugs

At least I am not able to hurry them with the great work they are doing.
The version for Android (iPhone?) will come and I hope it is also a prominent mobilbrowser and not one as there are already a lot in the store.

[Pesala]

@MattSolo45 said in Mobile Browser Version:

I meant the promises and declarations that were not fulfilled

When and by whom were such promises and declaration made? Do you have a link? What exactly was said?

I don't follow Twitter or other social media platforms, but this was said by Jon (JvT) back in March 2017.

RP: So we talked about the desktop. Do you not have a mobile browser? How is that?
JvT: It’s just been taking time. We started on Android at the same as we started with desktop and then we found that our solution for doing the desktop browser – including solutions for the extensions and the like – did not really lend itself well to the mobile browser.
So, from that perspective, it actually delayed our progress a little bit. But the mobile browser is in the works and it will be coming out there. It just takes a little bit of time.

[Ayespy]

@MattSolo45 I'm unaware of promises and declarations unfulfilled. Perhaps you could be specific. Mail was anticipated to come out sooner than it has. That's about it. Everything else is, "We'll do it as soon as we're able."

If my math is any good, there are between 20 and 30 developers, of whom I think 2 are working on mobile. At present, they are getting adequate feedback from the 70 or 80 testers that have mobile installed. Obviously, feedback will mushroom upon release. At that point, I predict the loudest outcry concerning mobile will be from users whose pet bug or feature does not have first priority.

I'm finding that mobile works better than any other browser on my phone, with the exception of a couple of visual annoyances that would, all by themselves, block release. I can't tell what level of development the Team is shooting for in order to be comfortable with release. I do know that it's a VERY high priority, though.

[Pesala]

@MattSolo45 I suggest listening to the full interview of Jon by Ayespy that happened in February 2018.

The forum thread is: Ask me anything: Jon von Tetzchner

[MattSolo45]

I agree that I may be partially wrong, but in my opinion there may also be some generalizations or giving hope in the style of

We are working on it, everything goes forward, but I wouldn't like to make any official declarations here. I can say that it will be ready when it is ready. We are aiming for January next year.

(interview with Mr. Jon for PClab.pl 18.10.17)

and despite doubts, it was assumed that the band aimed at such a release date, but it is known that there may have been complications or changes that prevented the release. But not one person, reading or listening to such an interview, can assume that Vivaldi mobile (taking information from the interview) can be released in January 2018 so it waits and then it turns out that it is not released and the user probably waits until the next interview with Mr. Jon where there will be further questions and answers about this version of Vivaldi. So I can say that I am also right. As for the team responsible for Vivaldi Mobile, I would like to congratulate them on their perseverance in this hard work and I would like me to work on such a project, but despite the small number of Vivaldi's team I would like more people to work on it, because all users respect your time and peace of mind, but the user will also not wait for an unknown amount of time and will choose a browser that provides him with everything he needs for normal work.

[Deniel]

The issue here is lack of communication and lack of plan.
You can't just say once a year for 3 and a half year we are working on it it will be soon out, it passes 3 and a half years since announcement and it can pass next 3 and a half years till release or may even never release, witch in my opinion is ok but than people should not be a gray at others who want some answer.

I like Vivaldi desktop but I just can't switch to it till mobile is out :/.

[Ayespy]

@Deniel We understand. But this is how Jon has managed his businesses for 25 years or more, and it works for him and his users. There is a plan. But it is not tied to a clock or a calendar. It is tied to a sequence of actions and the realization of progress.

I get the anxiety and disappointment. Sooner or later, though, the team always delivers. And in the meantime, there aren't a lot of false and missed announcements that something will be done on this and this date, and no time and grief spent explaining how or why a deadline was missed. We who have been enjoying what his teams produce since the late 90's are on board with the projected release date always being "when it's ready."

I'm sure you run your businesses differently, and that's your choice. But this works for the world of Vivaldi.

[MattSolo45]

Maybe it's a stupid thought, but I have a question whether the Vivaldi version for Windows phone was created ? And if so, I know perfectly well that the mobile system from Microsoft is already dead, but if it could be released in a form similar to Vivaldi's version 1.0 for Windows XP and Vista ? It would be a nice gesture for some users, but this year they will say goodbye to their favorite mobile platform and release it at least in a preview version with some features (if the port for this system was created). In my eyes it wouldn't be a waste of time (because some of us are waiting for Vivaldi mobile from 2017 anyway ), but finishing the project and, as I wrote earlier, a nice gesture for users who wanted to have vivaldi mobile on their phones.

[Ayespy]

@MattSolo45 To my knowledge, no Windows phone version was created. I'm not sure it would actually be possible.

Only Android is being worked on at the moment, about 10% of the team is dedicated to it I believe, and there simply are no resources to start on another platform as far as I can tell. It would seem when Android is essentially stable, the next project (which will be likely to take longer) will probably be iOS (which could require some new hires). By the time that is done, I wonder if there will still be any support at all for Windows phone. Certainly, I know that the only Windows phone I possess (Blackjack II) is about 15 years old, and stopped being supported long, long ago. If the work of two people can be dedicated to the support of a million users, or a hundred thousand users, I wonder if it would be sensible to dedicate that same work to support for fifty users.

To be sure, gestures are nice. I think it also makes sense to consider the economy of the gesture.

A complicating aspect to consider when thinking of such a project, is that Windows phones can only download apps from the Windows store, Vivaldi is based on Chromium - and there is no Chrome or Chromium for Windows phone. It was never adapted to that system. So...

[Catweazle]

In the background is a shame that Windowsphone has ceased to exist. In my opinion it was an excellent and safe phoneOS, but it is true that it is a somewhat useless effort to create a product for an OS that no longer exists, especially for a team with limited resources.

[Ayespy]

@Catweazle And especially when there's no Chromium engine for Windows phone.