Didn't find the answer here? Contact us, or check our Blog.
You've started at a great time, there are many options available these days:
You can get any of the prosumer 360 cameras by the likes of Ricoh, Insta360 etc, which are one-shot cameras that do it all for you. If you're after poor quality on the cheap, you can use apps like Google Camera on Android, or Google Streetview on your iPhone or Android. Or you can dive in the professional deep end with a DSLR rig.
Because we can deliver almost everything we want to via a web browser, which -everyone- has on their phones already.
We did have an iPhone app initially, but we scrapped it. We found that trying to get clients to install a custom app was way more hassle than just sending them to a webpage using a browser, which is already on every phone.
If you're doing a demo to a client, or want to show some content to somebody on the spot, getting them to download an app first is a pain. Depending on data plans and download limits, they may not even be able to download a larger sized app unless they're on WiFi!
A large percentage of people will simply move on if they're forced to install an app to do or view something. One less step in getting your content to them means lots more engagement for you.
Finally, people with strict corporate plan phones aren't actually able to install new apps, but they already have a browser, so there's another potential segment that you miss out on. A really big reason: everyone always gets the latest updates and features instantly, on any phone/desktop, without having to keep apps updated!
Most likely the page you've embedded your Snap in is HTTP. SeekBeak uses secure HTTPS only, as there are some features which browsers will soon be allowing only over HTTPS connections, including device motion and fullscreen. The list of 'powerful features' features SeekBeak uses, as they're called by the Google Chrome security team are:
If it's still not working with HTTPS, make sure you're using the preferred SeekBeak script embed code, instead of the iFrame embed code. Certain browsers and operating systems don't allow device motion events across domains. Our script embed has a workaround for this.
iOS 12 implemented an “Opt in” way of allowing access to the phone gyro. We posted a quick video on how to fix this here
iOS 13 completely changed the way that the user can allow browser access to the gyro. SeekBeak handles this natively when using our viewer, and also when using the script embed in other websites, raw iFrame embeds cannot access the gyro.
iOS doesn't support full screen viewing at all. iPadOS has limited support, and you can keep up with changes here.
This is unfortunately out of our hands, and is by design to combat autoplaying ads on websites, and save mobile data.
From Apple: “In Safari on iOS (for all devices, including iPad), where the user may be on a cellular network and be charged per data unit, preload and autoplay are disabled. No data is loaded until the user initiates it.”.
Google has followed suit as well: “Android has disabled autoplay in versions 4.1+.”
Getting peoples GPS coordinates via the browser can involve jumping through a lot of hoops, let's see if these can help you out:
If you're on iOS using Safari, please go to Settings > Privacy > Location Services > Safari and make sure it is set to ON.
If you're using a browser on MacOS, go into System Preferences > Security & Privacy > Privacy, check "Enable Location Services,"and specify your browser as one of the apps that's allowed access.
Turn on Location Services: Settings > Location > "Turn On"
or Chrome > Settings > Site Setting > Location >select "Location access is turned off for this device" > select "On"
Allow us to Collect Location Data: Chrome > Settings > Site Setting > Location > select "On"
Unblock Instructions If Blocked Accidentally: Chrome > Settings > Site Setting > Location > Blocked >select website > Location Access > "Allow"
Turn on Location Services: Settings > Location > select "On"
Allow us to Collect Location Data: Firefox > Page > Edit Site Settings > select "On"
SVG's have a ton of things that can go wrong with them internally. Some browsers handle errors better than others. Try resaving the SVG in a different image editor, or use an online SVG optimizer. If the export is a 'wrapped' jpg/png file, try opening the SVG up in a plain text editor, search for, and change
xlink:href="data:img/
to
xlink:href="data:image/
and then re-upload it. Note the “img” vs “image”.
SeekBeak is compatible with most mobile and desktop based VR headsets, i.e. Google Cardboard, Quest, Vive. For mobile based headsets, simply put the device into the headset and press the VR/XR headset icon in the SeekBeak Navbar. With mobile based headsets, you get full gaze based navigation, and all Hotspot interactivity where applicable.
Headsets using built in browsers like the Oculus Go/Quest/Quest 2 and Vive Focus Plus are supported and have full functionality in normal browsing mode. Their WebXR “Immersive mode” isn't able to display any HTML content however, only 3D graphics, so functionality is currently limited to basic Navigation via Point or Polygon “Jump To Snap” type Hotspots.
Apple has decided that iPhones should not have a full screen API unfortunately, (except for new iPads on iOS 13+, and even then there's an overlay button), and are unable to enter full screen mode from an iFrame.
Just to clarify: This is not just a SeekBeak issue, this is an 'everyone on the internet' issue unfortunately due to Apples decision. This also only applies to Snaps embedded in 3rd party websites, our viewer has no issue with displaying full screen on iPhone.
Some options available are to have a 'view full screen' link somewhere which will load our dedicated viewer in a separate page, or to use CSS/JavaScript to adjust the size of the embed in their website for iPhone users.
For devices that do support full screen, SeekBeak will detect if the device supports the full screen API and will show/hide the full screen button accordingly.
For up to date support on which devices/browsers support full screen from an iFrame, see https://caniuse.com