Filter
-
Content Type
-
Category
Mobile/Wearable
Visual Display
Digital Appliance
Platform
Recommendations
Filter
Develop Smart Signage
apigetting device capabilities using systeminfo api the following keys are available to obtain the device capability information using systeminfo api device capability keys battery camera content api database download api graphics input iotcon push api led location microphone multi-point touch multimedia transcoder network opengl® es platform profile sensor screen shell dynamic box sip speech tv usb vision web service system keys build information model name platform name tizen id the following table lists the keys to check if a device has a battery key type description version http //tizen org/feature/battery boolean the platform returns true for this key, if the device has a battery if it is true, w3c battery status api, battery property in systeminfo api, and power api must be supported 2 3 the following table lists the camera feature keys key type description version http //tizen org/feature/camera boolean the platform returns true for this key, if the device provides any kind of a camera if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/camera back boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a back-facing camera 2 2 1 http //tizen org/feature/camera back flash boolean the platform returns true for this key and the http //tizen org/feature/camera back key, if the device provides a back-facing camera with a flash 2 2 1 http //tizen org/feature/camera front boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a front-facing camera 2 2 1 http //tizen org/feature/camera front flash boolean the platform returns true for this key and the http //tizen org/feature/camera front key, if the device provides a front-facing camera with a flash 2 2 1 the following table lists the keys related to content api features key type description version http //tizen org/feature/content scanning others boolean the platform returns true for this key, if the device supports the media scanning feature for "other"-type files which are not included in the media content types such as "image", "video", "sound" or "music" 4 0 the following table lists the database feature keys key type description version http //tizen org/feature/database encryption boolean the platform returns true for this key, if the device supports database encryption 2 2 1 the following table lists the keys to check if download api is supported on a tizen device key type description version http //tizen org/feature/download boolean the platform returns true for this key, if the device supports download api 2 3 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports all apis which require telephony feature if it is true, "cellular" in downloadnetworktype is supported 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi if it is true, "wifi" in downloadnetworktype is supported 2 2 1 the following table lists the graphics feature keys key type description version http //tizen org/feature/graphics acceleration boolean the platform returns true for this key, if the device supports graphics hardware acceleration 2 2 1 the following table lists the input feature keys key type description version http //tizen org/feature/input keyboard boolean the platform returns true for this key, if the device provides a built-in keyboard supporting any keyboard layout 2 2 1 http //tizen org/feature/input keyboard layout domstring the platform returns the keyboard layout such as qwerty supported by the built-in keyboard for this key and returns true for the http //tizen org/feature/input keyboard key if the device does not provide a built-in keyboard, the platform returns an empty string for this key and returns false for the http //tizen org/feature/input keyboard key 2 2 1 http //tizen org/feature/input rotating_bezel boolean the platform returns true for this key, if the device provides a built-in rotating bezel 2 3 1 the following table lists the keys related to iotcon api features key type description version http //tizen org/feature/iot ocf boolean the platform returns true for this key, if the device supports the iot connectivity if it is true, iotcon api is supported 4 0 the following table lists the led feature key key type description version http //tizen org/feature/led boolean the platform returns true for this key, if the device supports led 2 3 the following table lists the location feature keys key type description version http //tizen org/feature/location boolean the platform returns true for this key, if the device supports location positioning 2 2 1 http //tizen org/feature/location batch boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports gps batch feature 2 3 http //tizen org/feature/location gps boolean the platform returns true and the http //tizen org/feature/location, if the device supports the global positioning system gps 2 2 1 http //tizen org/feature/location wps boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports the wi-fi-based positioning system wps 2 2 1 the following table lists the microphone feature keys key type description version http //tizen org/feature/microphone boolean the platform returns true for this key, if the device supports a microphone if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/media audio_recording boolean the platform returns true for this key, if the device supports to record audio files on a device if it is true, cordova media api is supported 3 0 the following table lists the multi-point touch feature keys key type description version http //tizen org/feature/multi_point_touch pinch_zoom boolean the platform returns true for this key, if the device supports pinch zoom gestures 2 2 1 http //tizen org/feature/multi_point_touch point_count long the platform returns the maximum number of supported multi-touch points for this key the platform returns a value less than 2 for this key, if the device does not support multi-point touch 2 2 1 the following table lists the multimedia transcoder feature key key type description version http //tizen org/feature/multimedia transcoder boolean the platform returns true for this key, if the device supports multimedia transcoder 2 3 the following table lists the network feature keys key type description version http //tizen org/capability/network bluetooth always_on boolean the platform returns true for this key, if the device must always enable bluetooth it means that an application cannot change the bluetooth's state visibility, connectivity, device name 2 3 http //tizen org/feature/network bluetooth boolean the platform returns true for this key, if the device supports bluetooth 2 2 1 http //tizen org/feature/network bluetooth audio call boolean the platform returns true for this key, if the device supports bluetooth handsfree profile hfp 2 3 http //tizen org/feature/network bluetooth audio media boolean the platform returns true for this key, if the device supports bluetooth advanced audio distribute profile a2dp 2 3 http //tizen org/feature/network bluetooth health boolean the platform returns true for this key, if the device supports bluetooth health device profile hdp 2 3 http //tizen org/feature/network bluetooth hid boolean the platform returns true for this key, if the device supports bluetooth human input device hid 2 3 http //tizen org/feature/network bluetooth le boolean the platform returns true for this key, if the device supports bluetooth low energy related methods in bluetooth api 2 3 http //tizen org/feature/network bluetooth opp boolean the platform returns true for this key, if the device supports bluetooth object push profile opp 2 3 http //tizen org/feature/network ethernet boolean the platform returns true for this key, if the device supports ethernet if it is true, "all" in downloadnetworktype and systeminfoethernetnetwork is supported 2 4 http //tizen org/feature/network internet boolean the platform returns true for this key, if the device supports internet 2 3 1 http //tizen org/feature/network net_proxy boolean the platform returns true for this key, if the device supports network proxy for internet connection 3 0 http //tizen org/feature/network nfc boolean the platform returns true for this key, if the device supports near field communication nfc 2 2 1 http //tizen org/feature/network nfc card_emulation boolean the platform returns true for this key, if the device is recognized by the nfc card readers 2 3 http //tizen org/feature/network nfc card_emulation hce boolean the platform returns true for this key, if the device supports nfc host-based card emulation 2 3 1 http //tizen org/feature/network nfc p2p boolean the platform returns true for this key, if the device supports p2p apis which require near field communication nfc 2 3 1 http //tizen org/feature/network nfc reserved_push boolean the platform returns true for this key and the http //tizen org/feature/network nfc key, if the device supports the nfc reserved push feature 2 2 1 http //tizen org/feature/network nfc tag boolean the platform returns true for this key, if the device supports tag apis which require near field communication nfc 2 3 1 http //tizen org/feature/network push boolean the platform returns true for this key, if the device supports push api which requires the ip push service provided by the tizen reference implementation 2 2 1 http //tizen org/feature/network secure_element boolean the platform returns true for this key, if the device supports secure elements 2 2 1 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports the telephony related apis 2 2 1 http //tizen org/feature/network telephony mms boolean the platform returns true for this key and the http //tizen org/feature/network telephony key, if the device supports mms 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi 2 2 1 http //tizen org/feature/network wifi direct boolean the platform returns true for this key and the http //tizen org/feature/network wifi key, if the device supports wi-fi direct™ 2 2 1 the following table lists the opengl® es feature keys key type description version http //tizen org/feature/opengles boolean the platform returns true for this key, if the device supports any opengl® es version and any texture format 2 2 1 http //tizen org/feature/opengles texture_format domstring the supported texture formats for the opengl® es e g "3dc/atc/etc/ptc" the platform returns an empty string for this key if opengl® es or compressed texture formats are not supported 2 3 http //tizen org/feature/opengles texture_format 3dc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the 3dc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format atc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the atc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format etc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the etc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format ptc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the ptc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format pvrtc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the pvrtc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format utc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the utc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles version 1_1 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 1 1 2 2 1 http //tizen org/feature/opengles version 2_0 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 2 0 2 2 1 the following table lists the platform feature keys key type description version http //tizen org/feature/platform core api version domstring the version of the tizen core api in the [major] [minor] format for example, "1 0" represents a web api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen core api, it returns an empty string "" 2 3 http //tizen org/feature/platform core cpu arch domstring the platform returns the cpu architecture e g "armv7", "x86" of a device 2 3 http //tizen org/feature/platform core cpu arch armv6 boolean the platform returns true for this key, if the device runs on the armv6 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch armv7 boolean the platform returns true for this key, if the device runs on the armv7 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch x86 boolean the platform returns true for this key, if the device runs on the x86 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu frequency long the platform returns the frequency at which a core cpu is running unit mhz 2 3 http //tizen org/feature/platform core fpu arch domstring the platform returns the fpu architecture e g "vfpv3", "ssse3" of a device if there is no fpu on a device, it returns an empty string "" 2 3 http //tizen org/feature/platform core fpu arch sse2 boolean the platform returns true for this key, if the device runs on the sse2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch sse3 boolean the platform returns true for this key, if the device runs on the sse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch ssse3 boolean the platform returns true for this key, if the device runs on the ssse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv2 boolean the platform returns true for this key, if the device runs on the vfpv2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv3 boolean the platform returns true for this key, if the device runs on the vfpv3 fpu architecture 2 2 1 http //tizen org/feature/platform native api version domstring the version of the native api in the [major] [minor] format for example, 1 0 represents a native api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen native api, it returns an empty string "" 2 2 1 http //tizen org/feature/platform native osp_compatible boolean the platform returns true for this key, if the device supports the bada compatibility mode 2 2 1 http //tizen org/feature/platform version domstring the version of the platform in the [major] [minor] [patch version] format for example, 1 0 0 represents a platform version where the major version is 1 and the minor and build versions are 0 2 2 1 http //tizen org/feature/platform web api version domstring the version of the web api in the [major] [minor] format for example, 1 0 represents a web api version where the major version is 1 and the minor version is 0 2 2 1 http //tizen org/feature/platform version name domstring the platform return the platform version name e g tizen 2 0 magnolia, tizen 2 1 nectarine 2 3 the following table lists the profile feature keys key type description version http //tizen org/feature/profile systeminfoprofile the platform returns a compliant device profile such as "mobile", "wearable" for this key 2 2 1 the following table lists the sensor feature keys key type description version http //tizen org/feature/sensor accelerometer boolean the platform returns true for this key, if the device supports the acceleration sensor 2 2 1 http //tizen org/feature/sensor accelerometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor accelerometer key, if the device supports the wake-up operation by the acceleration sensor 2 2 1 http //tizen org/feature/sensor activity_recognition boolean the platform returns true for this key, if the device supports activity recognition 2 3 http //tizen org/feature/sensor barometer boolean the platform returns true for this key, if the device supports the barometer pressure sensor 2 2 1 http //tizen org/feature/sensor barometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor barometer key, if the device supports the wake-up operation by the barometer sensor 2 2 1 http //tizen org/feature/sensor gesture_recognition boolean the platform returns true for this key, if the device supports the gesture recognition 2 3 http //tizen org/feature/sensor gravity boolean the platform returns true for this key, if the device supports gravity 2 3 http //tizen org/feature/sensor gyroscope boolean the platform returns true for this key, if the device supports gyroscope 2 2 1 http //tizen org/feature/sensor gyroscope_rotation_vector boolean the platform returns true for this key, if the device supports gyroscope rotation vector 3 0 http //tizen org/feature/sensor gyroscope wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor gyroscope key, if the device supports the wake-up operation by the gyro sensor 2 2 1 http //tizen org/feature/sensor heart_rate_monitor boolean the platform returns true for this key if the device supports hrm 2 3 http //tizen org/feature/sensor heart_rate_monitor led_green boolean the platform returns true for this key if the device supports green light spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_ir boolean the platform returns true for this key if the device supports infrared spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_red boolean the platform returns true for this key if the device supports red light spectrum 2 3 1 http //tizen org/feature/sensor humidity boolean the platform returns true for this key, if the device supports the humidity sensor 2 3 http //tizen org/feature/sensor linear_acceleration boolean the platform returns true for this key, if the device supports the linear acceleration sensor 2 3 http //tizen org/feature/sensor magnetometer boolean the platform returns true for this key, if the device supports the magnetic sensor 2 2 1 http //tizen org/feature/sensor magnetometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor magnetometer key, if the device supports the wake-up operation by the magnetic sensor 2 2 1 http //tizen org/feature/sensor pedometer boolean the platform returns true for this key, if the device supports pedometer 2 3 http //tizen org/feature/sensor photometer boolean the platform returns true for this key, if the device supports the photometer sensor 2 2 1 http //tizen org/feature/sensor photometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor photometer key, if the device supports the wake-up operation by the photo sensor 2 2 1 http //tizen org/feature/sensor proximity boolean the platform returns true for this key, if the device supports the proximity sensor 2 2 1 http //tizen org/feature/sensor proximity wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor proximity key, if the device supports the wake-up operation by the proximity sensor 2 2 1 http //tizen org/feature/sensor rotation_vector boolean the platform returns true for this key, if the device supports the rotation vector sensor 2 3 http //tizen org/feature/sensor sleep_monitor boolean the platform returns true for this key, if the device supports sleep_monitor 3 0 http //tizen org/feature/sensor temperature boolean the platform returns true for this key, if the device supports the temperature sensor 2 3 http //tizen org/feature/sensor tiltmeter boolean the platform returns true for this key, if the device supports the tilt sensor 2 2 1 http //tizen org/feature/sensor tiltmeter wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor tiltmeter key, if the device supports the wake-up operation by the tilt sensor 2 2 1 http //tizen org/feature/sensor ultraviolet boolean the platform returns true for this key if the device supports ultraviolet sensor 2 3 http //tizen org/feature/sensor wrist_up boolean the platform returns true for this key if the device supports wrist_up 2 3 the following table lists the screen feature keys key type description version http //tizen org/feature/screen boolean the platform returns true for this key, if the device has a display screen 2 3 http //tizen org/feature/screen auto_rotation boolean the platform returns true for this key, if the device supports screen auto-rotation 2 2 1 http //tizen org/feature/screen bpp long the platform returns the number of bits per pixel supported by the device for this key the value depends on the screen, and is typically 8, 16, 24, or 32 2 2 1 http //tizen org/feature/screen coordinate_system size large boolean the platform returns true for this key, if the device supports the large screen size for the coordinate system 2 2 1 http //tizen org/feature/screen coordinate_system size normal boolean the platform returns true for this key, if the device supports the normal screen size for the coordinate system 2 2 1 http //tizen org/feature/screen dpi long the platform returns the number of dots per inch supported by the device for this key 2 2 1 http //tizen org/feature/screen height long the platform returns the height of the screen in pixels supported by the device for this key 2 2 1 http //tizen org/feature/screen output hdmi boolean the platform returns true for this key, if the device supports hdmi output 2 2 1 http //tizen org/feature/screen output rca boolean the platform returns true for this key, if the device supports rca output 2 2 1 http //tizen org/feature/screen shape circle boolean the platform returns true for this key, if the device supports a circular shaped screen 2 3 1 http //tizen org/feature/screen shape rectangle boolean the platform returns true for this key, if the device supports a rectangular shaped screen 2 3 1 http //tizen org/feature/screen size all boolean the platform can return true if the device supports any of screen sizes and resolutions if the device has a display screen, it returns true 2 2 1 http //tizen org/feature/screen size large boolean the platform can return true if the device supports the large screen size 2 2 1 http //tizen org/feature/screen size normal boolean the platform can return true the device supports the normal screen size 2 2 1 http //tizen org/feature/screen size normal 240 400 boolean the platform returns true for this key, if the device supports the 240 x 400 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 320 320 boolean the platform returns true for this key, if the device supports the 320 x 320 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 320 480 boolean the platform returns true for this key, if the device supports the 320 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 360 360 boolean the platform returns true for this key, if the device supports the 360 x 360 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 2 http //tizen org/feature/screen size normal 360 480 boolean the platform returns true for this key, if the device supports the 360 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 480 800 boolean the platform returns true for this key, if the device supports the 480 x 800 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 540 960 boolean the platform returns true for this key, if the device supports the 540 x 960 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 600 1024 boolean the platform returns true for this key, if the device supports the 600 x 1024 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 720 1280 boolean the platform returns true for this key, if the device supports the 720 x 1280 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 1080 1920 boolean the platform returns true for this key, if the device supports the 1080 x 1920 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen width long the platform returns the width of the screen in pixels supported by the device for this key 2 2 1 the following table lists the shell dynamic box feature keys key type description version http //tizen org/feature/shell appwidget boolean the platform returns true for this key, if the device supports the widget since 2 3 1, this key indicates only native widget 2 2 1 the following table lists the sip feature keys key type description version http //tizen org/feature/sip voip boolean the platform returns true for this key, if the device supports the voice over internet protocol voip 2 2 1 the following table lists the speech feature keys key type description version http //tizen org/feature/speech recognition boolean the platform returns true for this key, if the device supports speech recognition stt 2 2 1 http //tizen org/feature/speech synthesis boolean the platform returns true for this key, if the device supports speech synthesis tts 2 2 1 http //tizen org/feature/speech control boolean the platform returns true for this key, if the device supports speech control 4 0 the following table lists the tv feature keys key type description version http //tizen org/feature/tv audio boolean the platform returns true for this key, if the device supports control of tv audio if it is true, tvaudiocontrol api is supported 2 3 http //tizen org/feature/tv display boolean the platform returns true for this key, if the device supports getting information about the effects of stereoscopy 3d mode if it is true, tv display control api is supported 2 3 http //tizen org/feature/tv inputdevice boolean the platform returns true for this key, if the device supports receiving key events generated when the user presses a key of an input device for example a tv remote control if it is true, tv input device api is supported 2 3 http //tizen org/feature/tv pip boolean the platform returns true for this key, if the device supports control of tv window e g main window, pip window if it is true, tv window api is supported 2 3 the following table lists the usb feature keys key type description version http //tizen org/feature/usb accessory boolean the platform returns true for this key, if the device supports the usb client or accessory mode 2 2 1 http //tizen org/feature/usb host boolean the platform returns true for this key, if the device supports the usb host mode 2 2 1 the following table lists the vision feature keys key type description version http //tizen org/feature/vision face_recognition boolean the platform returns true for this key, if the device supports face recognition 2 2 1 http //tizen org/feature/vision image_recognition boolean the platform returns true for this key, if the device supports image recognition 2 2 1 http //tizen org/feature/vision qrcode_generation boolean the platform returns true for this key, if the device supports qr code generation 2 2 1 http //tizen org/feature/vision qrcode_recognition boolean the platform returns true for this key, if the device supports qr code recognition 2 2 1 the following table lists the web service model feature keys key type description version http //tizen org/feature/web service boolean the platform returns true for this key, if the device supports the web service model 2 3 the following table lists the build information key key type description version http //tizen org/system/build date domstring the platform returns the build date the format yyyy mm dd 2 3 http //tizen org/system/build string domstring the platform returns the build string including build date and time 2 3 http //tizen org/system/build time domstring the platform returns the build time the format hh mm ss 2 3 http //tizen org/system/manufacturer domstring the platform returns the device manufacturer's name 2 3 http //tizen org/system/build release domstring the platform returns the build version information the build version information is made when the platform image is created 3 0 http //tizen org/system/build type domstring the platform returns the build type, such as "user" or "eng" the build type is made when the platform image is created 3 0 http //tizen org/system/build variant domstring the platform returns the variant release information the variant release information is made when the platform image is created 3 0 http //tizen org/system/build id domstring the platform returns the build id the build id is made when the platform image is created 3 0 the following table lists the model name key key type description version http //tizen org/system/model_name domstring the platform returns the model name 2 3 the following table lists the platform system keys key type description version http //tizen org/system/platform communication_processor domstring the platform returns the device communication processor name 2 3 http //tizen org/system/platform name domstring the platform returns the platform name it must be tizen 2 2 1 http //tizen org/system/platform processor domstring the platform returns the device processor name 2 3 the following table lists the tizen id system key key type description version http //tizen org/system/tizenid domstring the platform returns the tizen id it is a randomly generated value based on the model name 2 3
Learn Developers Podcast
docreservation when it comes to actually trying it out and that i think that's really powerful i think the technology used to build that particular demo you were talking about was google's model viewer project and model viewer is fantastic for stuff like store pages and product views you add the script to your page, and then you use the model view or tag to display a 3d model on the page which is already ready to go for augmented reality so if you couldn't get it 3d model of your product in the gltf model format, then it's ready to go and that's really powerful tony morelan 35 06 what i really enjoyed was the fact that there was nothing to download, i clicked a few buttons, and there was, so i can definitely see the benefit where webex are, there isn't that hurdle that somebody has to go over, which is the whole download installation, just to experience it, what would be the best way for developers to get started with web xr? ada rose cannon 35 26 well, if you depend how quickly you want to get started so if you want to get started, and you just you already have the 3d model, and you want to just be done straight away, model viewer is a great place to start it lets you just with a single html tag and a script tag, you can have a 3d model, augmented reality ready in your browser and in your website so that's really great if you want something that's like still html based, and a great way to start if you're more of a beginner, and a frame is a fantastic place to start i'll be honest, i've been doing graphics development for years and i also still use a frame for almost all my products, just because it's so quick to get started but also lets you dive in deep because a frame is based on the library three j s, which is a javascript 3d library for working on web gl, which has been around for a long time is extremely powerful and so a frame kind of gives you the best of both worlds but if you really want to get stuck in with the javascript and really get in with the nitty gritty, working directly with three js, or with babylon js is a great way to go but if you want more of an of a fully like integrated development environment for this kind of thing, so if you prefer the kind of all in one it solution, then there's actually quite a few solutions here so there's amazon sumerian, there's play canvas, which is a fantastic engine and there's a really new one that seems really powerful wonderland engine and of course, as the old classic unity, which has a unity export for what xr tony morelan 37 07 excellent sounds like there's a lot of great tools for developers to get started with, with web xr kevin, let me ask you, how is samsung internet involved with web xr? kevin picchi 37 18 well, we shipped web xi by default inside of browser and we always make sure to ship the latest modules out so the developers can benefit all the good from the tony morelan 37 32 api and what about samsung phones? how well do they work with webxr? kevin picchi 37 37 all of them are compatible? as long as you have the samsung internet browser installed on your phone? you can experience webex are tony morelan 37 45 excellent in ad, i know that you're working also on web standards can you tell me a little bit about web standards, maybe some of the challenges with that? ada rose cannon 37 54 yeah, so as i mentioned earlier, i'm co-chair of the immersive web groups these are the groups that are working on the standards that get built into web browsers that become the api's developers work with to build these experiences and working on the web standards can be really challenging, because people have high expectations for the privacy you'd get from the web like you don't go to a website and expect them to immediately start spying on you through your camera, or doing anything really super dodgy the web browser is there to protect you and because we're adding new api's to the browser, we can't do anything that's going to breach this expectation of privacy and security and because it's the web, it's also got to work for as many people as possible so accessibility is also an incredibly important task so these are the kinds of constraints you've got to work in but on top of this, as graphics developers, we really want to get people working with the very latest features you can find in immersive hardware and we want people to build the kinds of experiences that rival what you can find on native and so balancing these privacy and security expectations against letting people have the most access to the hardware is a real challenge, because a lot of the hardware to do with immersive hardware, such as augmented reality is to deal with revealing more information about the environment and letting the developers work with it so for example, for something like working out where the user can place 3d models in the environment, the underlying engine actually can fully scan your environment and work out what the exact shape of stuff is and its color but this is a lot of information, which is too much that a lot of experiences don't actually need and so it would very easily let someone write an abusive application without giving too much additional functionality so actually the early versions of real-world sensing in web xr just let you query a single point from a single ray at a time so this lets you do stuff like placing a single object on the floor on the walls but we're not exactly scanner through someone's room and this is the kind of balances we have to make and because we have had developers come back to us and say they do need like higher precision, more wide scope, scan, like room scanning this is the kind of thing where we can build an additional api to, to let developers have this but at the same time, we can warn the users that what the developer is trying to do might potentially be more dangerous just like when a website is trying to turn your camera or microphone on, it will warn you yes, in the same way, if the website is trying to get a 3d scan of your entire apartment, we want to warn you about that, too and so this is the kind of balances we have to make tony morelan 41 04 so i know that is one of the big benefits around samsung internet is all of the privacy that you get when you use samsung internet nice to see how that's carrying over to web xr how stable would you say vr is on web xr? ada rose cannon 41 22 so vr itself is very stable, vr was one of the first parts we completed in in web xr, there's actually been vr in the web for like a long time, there was an old api called web vr, that was deprecated last year, but since then, web xr, we pushed very hard to be able to totally replace web vr with web xr with the same capabilities so what vr is pretty stable, i doubt there'll be any more changes to it at all so if you write something, targeting vr, yeah, lots will probably stay the same ar is a little newer and there are newer api's to help with augmented reality so some of the more hit testing, depth sensing stuff, some of this is like a little newer, there may still be some privacy issues that need to be resolved, which may have some interface changes but generally, these are also getting pretty stable a lot of the stuff that might be arriving in the next couple of months, or have arrived in the last month or so might have a few changes so it's important that developers do continue testing that stuff and do keep an eye out for when the api's do change because occasionally, we will get feedback that some that we've developed has a major security flaw we've missed and we can't just leave that out in the wild, we do have to change the api to fix that issue tony morelan 42 50 so are there any new features that you can share related to web standards ada rose cannon 42 55 so there's new features being developed all the time and the really nice thing about web standards is that the develop totally in the open so if you want to see all the latest work that's going on, you can check out the immersive web github, where you can see all of the issues that are being worked on in real time on web xr and all the related modules there’re a few modules i'm really excited about one, which is still super early days would be some kind of dom layer, api that would let us put dom content into a web xr scene so like html elements, and css, this is like kind of a tricky thing to do and it's something we've wanted for a long time and i'm hoping it won't be too far in the future when we eventually get it so what tony morelan 43 42 it is, is, since i am new to web xr, myself, what is dom content? ada rose cannon 43 47 so dom content is like html and css content so like, the normal stuff you'd see on a website, so like, forms, images, buttons, you know, that kind of thing? links, okay, so is this where if i am in either a vr and ar environment, this is where you can actually have like buttons that are clickable within that space? yeah, exactly so in addition to making your 3d environment where the user can grab stuff and pull stuff, and have 3d models, you can also have part of a web page in the environment and that may sound quite boring, because it's just going to be like a 2d rectangle with content in it this lets you use the heck demand css api's that are already available in browsers to build 2d interfaces in vr and ar as well so for example, if you had html form reimplementing, that whole thing out of rectangles and shape in 3d modeling application is kind of a pain, sure, but just being able to write some html and take advantage of all the really powerful 2d layout capabilities of the web is just a fantastic feature and will let developers make the most out of both 3d and 2d tony morelan 45 03 nice, nice yeah so what are some other technologies that go well with web xr? ada rose cannon 45 08 so the first one that comes to mind is like web rtc so this is what lets you do video sharing and audio sharing over the web tony morelan 45 17 in web rtc stands for real time communication, correct? it does, yes ada rose cannon 45 21 so this lets you, for example, if a means kind of some kind of social vr situation, i could do some kind of cool between me and another person so i can chat with them in an efficient manner that's peer to peer without needing to go up to a central service okay and another thing that's really useful for social vr stuff is websockets so websockets lets you do incredibly high bandwidth, very, very fast data connections between your client and the server so you could have many people in a single room, or with having all their positions and rotations shared over websockets so you can see people moving around and walking around in real time and so using their free web rtc is like the kind of the two things you need to get a really good social web experience tony morelan 46 15 so what about the technology, web audio? how was that working with web xr? ada rose cannon 46 20 so web audio is a really interesting api so web xr doesn't actually bother dealing with any audio stuff out of the box there's not like specific information you need for working with audio but the really powerful thing about web audio is that it has stuff like a 3d panner node with hrtf built in so you can already do 3d audio in the web long before web xr came along, which is incredibly cool so you can have correct 3d audio, using the web audio api using the web and it's something that's like a little tricky to set up there's a really great library by google called the resonance project and it lets you like define the surfaces around you so you can say the floor is hard there's no ceiling is where the walls are, and will correctly work out the echoes and the reverb and so you could have multiple sound sources, that will sound really good and you'll be able to know where they are instinctually? because they're done in 3d wow and this is really powerful tony morelan 47 22 yeah, cuz i could see where if you're like moving throughout that environment, your audio is going to be changing the sound reflection from within the room to be able to experience those changes yeah, that seems really powerful ada rose cannon 47 35 yeah, so you can take the information from web xr, for example, the position of the user's head, and then you feed that into a library like resonance and that will automatically handle the correct sound from the user's perspective, which is pretty amazing tony morelan 47 53 yeah so what about 5g? how is webex r and 5g working together? ada rose cannon 48 00 so 5g is totally amazing and this is definitely kevin's cup of tea so he should answer this one kevin picchi 48 06 so 5g would essentially improve your experience using webex so for example, you could have way bigger models downloaded on your phone with a higher quality, and it would simply load faster you could also imagine having multiplayer experiences and having almost zero lag or latency tony morelan 48 29 now, i know that you're working on 5g tours, what exactly is 5g tours kevin picchi 48 34 so 5g tour is a european project in which samsung participates and we test the 5g performances in different environments, in which the first one is touristic environment where we try to enhance the experience of tourists while they're visiting a city there is another one which is the mobility one, we try to enhance the way people move in the city and we also try to improve and create new experiences in a way that we make the city safer so let's say there is an evacuation, we can provide guides and we basically use 5g in all of those verticals to improve them tony morelan 49 19 so to talk a little bit more about making cities more secure or safer what exactly do you mean by that? kevin picchi 49 24 so we have a use case that we're working on internally to take all of it is making evacuation easier and faster by leveraging 5g, for example, have some sort of augmented reality application lunch instantly on the phone after people in the airport and the application would basically guide the people out of the airports in a safe way so let's say there would be a fire and you would be guided around the fire and in the right direction nice tony morelan 49 55 so can you tell me how is samsung internet involved with the with 5g tours? kevin picchi 49 59 well, it's so we're working on basically three sub projects in the 5g tour, where we take advantage of web technologies so what would those technologies be? we're using web xi web rtc, web sockets, and web each id those are the web api that ada just talked about we're trying to fuse them with 5g to improve those verticals tony morelan 50 25 so tell me a little bit more what is web rtc kevin picchi 50 28 one of the use cases we're working on is making museum experience experienceable by multiple people so the goal of it is having two or three persons in a room in a museum room with a piece of art, and being able to have them both in the room and been like letting them experience the artwork, take a look at the artwork, maybe move things around the room and all that taking advantage of 5g, which reduces latency and people tony morelan 51 01 feel better nice and this is in a vr environment is what you're referring to correct? kevin picchi 51 05 yes tony morelan 51 06 so what about web h id, which i think stands for human interface device? is that correct? kevin picchi 51 12 yes that's kind of like the gamepad api in a way that this api lets us send probe packets to the devices so to put it in a simple way, let's say you'd have a remote controller that is not compatible with the gamepad api, you could use this api to basically send bro comments to a controller and you could have some kind of communication going and we're using that api with the remote controller that we're using in another use case, in which were basically communicating with remote and getting sensors data and we're using them as a controller basically tony morelan 51 59 nice, nice to see the versatility of it is there any news coming out that you can share that's related to webex r and samsung internet? ada rose cannon 52 08 web xr is evolving really quickly the best way to keep up to date with new news and events and all the cool stuff that's happening in web xr is to subscribe to the immersive web weekly newsletter it's a newsletter that comes out on tuesdays and is a really great way to stay up to date with everything that's happening in the immersive web world tony morelan 52 26 nicely and we'll include a link to that newsletter in the in the show notes what advice do you have for developers looking to start building for samsung internet and in webex are? ada rose cannon 52 39 probably my best advice is to find an environment you're happy working with i really like a frame, there's quite a few out there, i have a few getting started guides on a website i maintain called immersive web dot dev so it's a great place to look at the different ways you can try out building web xr there's also some really useful tools out there, such as an emulator that lets you emulate immersive headsets in the web browser so you can test your site without needing to actually put on a headset, which is a really great way just to like experiment with stuff as you're building it and is a tool that i use an awful lot right so that's great to hear tony morelan 53 18 so are there other ways for developers to follow you and learn more about by what you have to offer? kevin picchi 53 23 yes, surely we're mostly active on twitter at samsung internet and you can also find our blog and our samsung internet page on the developer samsung com slash internet website you can also follow us here and i on twitter my ad is kevin peaky p icc h ii ada rose cannon 53 46 and mine is at ada rose cannon tony morelan 53 49 well, even kevin, it was great to have you on the podcast just wanted to say thanks for giving us a little insight into samsung internet and web xr ada rose cannon 53 57 thank you so much for having us it's been really good kevin picchi 53 59 yeah thanks for having us sunny dan appelquist 54 03 yeah, so good to hear about what we're doing with web xr and the immersive web i it's a technology that i think is really game changing, especially in the way that it democratizes xu, democratizes, ar and vr and really brings the value of that technology to more people across different types of handsets different types of devices it's really, it's so important we've talked a lot about different aspects of samsung internet, what would be the best way for developers to even learn more? well, you can first of all, visit us on our homepage, which is developer samsung com/internet or you can just click on samsung internet once you go to developer samsung com there you can read about our latest releases, you can read about the team you can have links to all our social media we are samsung internet on twitter, our dms are open there and now account is managed by our team directly so if you're dm’ing, samsung internet, the entire team here will read it and we will try to get back to you but also, if you have bugs or if you have problems, you can use that as a great channel to reach us or you can just add mention us on twitter, and we'll be happy to have a conversation with you there we're also on linkedin, if you search for us on linkedin, samsung internet, you'll find our linkedin page and we're happy to interact there as well we're on medium if you search for samsung internet, again, that's linked from our page at developer samsung com/internet we blog on medium and we also reflect that blog on developer samsung com so that you can see us everywhere you go hey, dan, it was great to have you on the podcast just wanted to say thanks to you and your team, for all the great and exciting things that are coming with samsung internet thanks for the opportunity and thank you for all the work that you've put in closing 55 59 looking to start creating for samsung download the latest tools to code your next app, or get software for designing apps without coding at all sell your apps to the world on the samsung galaxy store check out developer samsung com today and start your journey with samsung the pow! podcast is brought to you by the samsung developer program and produced by tony morelan
We use cookies to improve your experience on our website and to show you relevant advertising. Manage you settings for our cookies below.
These cookies are essential as they enable you to move around the website. This category cannot be disabled.
These cookies collect information about how you use our website. for example which pages you visit most often. All information these cookies collect is used to improve how the website works.
These cookies allow our website to remember choices you make (such as your user name, language or the region your are in) and tailor the website to provide enhanced features and content for you.
These cookies gather information about your browser habits. They remember that you've visited our website and share this information with other organizations such as advertisers.
You have successfully updated your cookie preferences.