0
Completed
Browser support
Your support for only Chrome is a bit puzzling and a kick in the teeth for Apple who have always championed the cause for HTML5. Not only that, but Safari is a superior browser to Chrome in all respects as far as I can see. Although I do use Chrome when Flash is required, to now find I cannot use Safari (the browser of my choice) because of your apparently misguided refusal to ensure compatibility is seriously off putting. Makes me want to look for an alternative data modelling solution.
Answer
And the kicker is that when I then switched to Chrome on the iPad I'm using and tried again, I received the exact same message saying that I was using the wrong browser and only Chrome is supported.
So looks like you couldn't even be bothered to provide compatibility with the iOS version of Chrome and since the ability to switch between the Mac and iPad to work on the same design is the prime reason for trying Vertabelo.... Well, need I say more :-(
So looks like you couldn't even be bothered to provide compatibility with the iOS version of Chrome and since the ability to switch between the Mac and iPad to work on the same design is the prime reason for trying Vertabelo.... Well, need I say more :-(
No response?
No-one cares?
Google Chrome says I need to use Google Chrome. Isn't that worthy of some comment?
No-one cares?
Google Chrome says I need to use Google Chrome. Isn't that worthy of some comment?
First of all, the Google Chrome for iPad doesn't use the same content rendering engine as the desktop version. It uses Apple's UIWebView. You can read more about it here: https://developer.chrome.com/multidevice/ios/overview
This is the cause of the message you're complaining about.
Secondly, Vertabelo won't work on touch devices. Our priority is to provide the best user experience for desktop users - this is a business decision. We have already considered the support for touch devices, but it definately won't happen within nearest few months.
Regarding Safari support - yes, we're quite close to enabling "beta" access for Safari users. Believe me, lack of this support so far isn't dictated by our hatred to Apple (which isn't true) or a will to "kick in the teeth for Apple". It's just a matter of time in constantly developed and still quite young product.
This is the cause of the message you're complaining about.
Secondly, Vertabelo won't work on touch devices. Our priority is to provide the best user experience for desktop users - this is a business decision. We have already considered the support for touch devices, but it definately won't happen within nearest few months.
Regarding Safari support - yes, we're quite close to enabling "beta" access for Safari users. Believe me, lack of this support so far isn't dictated by our hatred to Apple (which isn't true) or a will to "kick in the teeth for Apple". It's just a matter of time in constantly developed and still quite young product.
Thanks for the response. I look forward to Safari compatibility.
As for touch devices, why not? Not perhaps in isolation as I quite understand the importance of larger screen etc, but the ability to log in and look at the model and make small adjustments from such a mobile device would be extremely useful and I would have thought a fundamental reason to choose a web based system.
Why wouldn't it work with a touch device? Fingers are clumsy for intricate work I agree, but use of a stylus of some sort usually fixes that. I still think being able to edit a diagram on the iPad would be invaluable.
As for touch devices, why not? Not perhaps in isolation as I quite understand the importance of larger screen etc, but the ability to log in and look at the model and make small adjustments from such a mobile device would be extremely useful and I would have thought a fundamental reason to choose a web based system.
Why wouldn't it work with a touch device? Fingers are clumsy for intricate work I agree, but use of a stylus of some sort usually fixes that. I still think being able to edit a diagram on the iPad would be invaluable.
We're not saying "no" for touch devices. We also see some advantages in accessing DB modeler from a mobile dev. They just aren't that high on our priorities list. As I wrote in my previous comment, some moves towards mobiles may happen somewhere closer 2015, but we won't forget about this.
Answer
Completed
Vertabelo now supports Safari. It's marked as "beta support", but should be fully functional. In case of any bugs or other problems occuring under Safari, please report them in separate threads.
Enjoy Vertabelo in Safari!
Enjoy Vertabelo in Safari!
Customer support service by UserEcho
Enjoy Vertabelo in Safari!