Filter
-
Content Type
-
Category
Mobile/Wearable
Visual Display
Digital Appliance
Platform
Recommendations
Filter
Distribute Galaxy Store
docmarketing resources marketing and monetization are a key part to every developer’s journey this page is designed to help you, the galaxy store seller, to navigate the resources available from the samsung developer program these resources have been created to help you succeed when it’s time to start promoting your new apps, games, themes, and watch faces the blog posts, articles and guides, videos, and downloadable content provide easy-to-follow instructions and access to powerful promotional tools that aid you in achieving your desired goals social promotion social media is the most powerful tool in engaging an audience and attracting new fans learning how to use these tools effectively can be the difference between success and failure, whether you are a new seller or an existing seller social promotion guidelines samsung developer hashtags social media promotion kits discounts and coupons seller portal the samsung seller portal is a powerful tool in helping you assess the health of your apps it’s important that you know the ins and outs of seller portal so that you can start to maximize revenue seller portal user guide galaxy store statistics galaxy store app review gathering feedback from your customers is important to gain insights on how to improve your app an app with strong ratings and reviews may influence more users to download it increase the number of customer reviews for your app galaxy store page views and downloads track page views and downloads using the acquisition reports in galaxy store statistics or third-party attribution platforms user attribution third-party attribution platforms brand being a galaxy store seller not only means you need to stand out in a crowd of millions, but also establish a trusted brand creating a lasting and powerful brand image puts you on the path to success create and manage your seller brands generate a galaxy watch for tizen seller brand page personalize your galaxy themes seller brand page badge bring customers to your app or brand page in one click promote your apps and brand on your website, youtube page, or any of your social media channels galaxy store badge promotion galaxy store badge image and link uses get your own galaxy store badge links manage your galaxy store badges galaxy store badge terms and conditions generate a badge login required galaxy store promotion you have the unique opportunity to promote your apps directly in galaxy store this can be powerful in helping you reach your desired return on investment and can aid in growing your brands galaxy themes promotion galaxy watch for tizen the galaxy store is your best opportunity to make a quick, yet lasting impression on any perspective customer ensuring that your store front has high quality images and relevant information is essential to your long term success how to take a galaxy watch screenshot create eye-catching galaxy store listings with the watch asset creator asset creator add your watch face design or watch app to smart lifestyle photos!
Develop Mobile
docsamsung application management 1 introduction samsung's application management is a solution that helps prevent battery consumption due to unintended background operations of applications this feature limits background activities according to the application usage patterns such as periods of non-activity and background battery consumption, and applies either the sleeping or deep sleeping modes through data analysis based on these patterns 2 purpose this guide introduces sleeping and deep sleeping application features, and how to set exceptions to exempt an application from application control 3 details 1 sleeping applications background applications that have not been used for about 3 days and causing poor system health ex battery consumption will go into the sleeping mode a bucket restriction applies to any sleeping applications, and features such as job, alarm, and foreground-service are restricted you can see the different buckets, and the restriction level for each bucket, at the android reference site restricted bucket application restrictions the user may also turn on the sleeping mode for a specific application menu path 2 deep sleeping applications applications that have not been used for a long period of time currently set to 16 days, but subject to change according to samsung policies will go into the deep sleeping mode deep sleeping applications only become active when the user opens them, and become inactive when they go into the background inactive applications can't perform any activities, including notifications or updates the user may also turn on the deep sleeping mode for a specific application menu path 3 setting exceptions samsung's automatic application control management system places applications to the sleeping or deep sleeping modes according to their usage patterns if there are applications that need to be set aside as exceptions, the user can do so at the following path settings > device care > battery > background usage limits menu path 4 api deeplink api for the sleeping applications, deep sleeping applications, and never sleeping applications screens // launch the detail activity of background usage limits intent intent = new intent ; intent setaction "com samsung android sm action_open_checkable_listactivity" ; intent setpackage "com samsung android lool" ; intent putextra "activity_type", 2 ; // 0 sleeping apps / 1 deep sleeping apps / 2 never sleeping apps startactivity intent ; 5 changes in one ui 6 with android 14 to strengthen the android platform, our collaboration with google has resulted in a unified policy that we expect will create a more consistent and reliable user experience for galaxy users since one ui 6 0, foreground services of apps targeting android 14 will be guaranteed to work as intended so long as they are developed according to android's new foreground service api policy
tutorials health, galaxy watch
blogthis is the final blog in a series to introduce the sample application workout, a tizen example for monitoring health sensors on a wearable device. the first blog, workout -- a tizen sample app for monitoring health sensors, presented the basic features of the application. the second blog, adding distance traveled to the tizen workout sample app, described how distance traveled is calculated. the third blog, adding heart rate summary to the tizen workout app, demonstrated how heart rate data is gathered. this blog describes how the application uses the tizen.wearable.circularui extension of the xamarin.forms framework. this extension provides a set of components customized for the wearable profile that makes development easier and efficient. it provides, among others, a circlelistview component, which is used on the summary view of the application. the list contains elements that differ from each other in terms of appearance. apart from the different contents of the text, they allow you to: use different icon images set different positions of text elements on selected elements use converters for selected list items display the action button on selected elements of the list time distance pace intensity itemsource the information about how the individual elements of the list should look like is provided by itemsource, which is represented by the list of elements of the detailsitemdata class. views/workout/detailspageview.xaml <cui:circlelistview.itemssource> <x:array type="{x:type models:detailsitemdata}"> <models:detailsitemdata name="time" value="{binding elapsedtime}" icon="images/details_time_icon.png"> <models:detailsitemdata.valuebounds> <rectangle x=".5" y="193" width="-1" height="-1" /> </models:detailsitemdata.valuebounds> <models:detailsitemdata.namebounds> <rectangle x=".5" y="245" width="-1" height="-1" /> </models:detailsitemdata.namebounds> </models:detailsitemdata> <models:detailsitemdata name="distance" value="{binding distance}" icon="images/details_distance_icon.png"> <models:detailsitemdata.valuebounds> <rectangle x=".5" y="193" width="-1" height="-1" /> </models:detailsitemdata.valuebounds> <models:detailsitemdata.namebounds> <rectangle x=".5" y="245" width="-1" height="-1" /> </models:detailsitemdata.namebounds> </models:detailsitemdata> <models:detailsitemdata name="average pace" value="{binding averagepace}" icon="images/details_average_pace_icon.png"> <models:detailsitemdata.valuebounds> <rectangle x=".5" y="193" width="-1" height="-1" /> </models:detailsitemdata.valuebounds> <models:detailsitemdata.namebounds> <rectangle x=".5" y="245" width="-1" height="-1" /> </models:detailsitemdata.namebounds> </models:detailsitemdata> <models:detailsitemdata name="intensity" value="{binding intensity, converter={staticresource bpmrangevalueconverter}}" icon="images/details_intensity_icon.png" isactionbuttonvisible="true"> <models:detailsitemdata.valuebounds> <rectangle x=".5" y="172" width="-1" height="-1" /> </models:detailsitemdata.valuebounds> <models:detailsitemdata.namebounds> <rectangle x=".5" y="224" width="-1" height="-1" /> </models:detailsitemdata.namebounds> </models:detailsitemdata> </x:array> </cui:circlelistview.itemssource> models/workout/detailsitemdata.cs using xamarin.forms; namespace workout.models.workout { /// <summary> /// details item data class. /// used as one element of the details page list. /// </summary> public class detailsitemdata : bindableobject { #region properties public static readonly bindableproperty valueproperty = bindableproperty.create("value", typeof(string), typeof(detailsitemdata), default(string)); /// <summary> /// workout detail name. /// </summary> public string name { get; set; } /// <summary> /// workout detail value. /// </summary> public string value { get => (string)getvalue(valueproperty); set => setvalue(valueproperty, value); } /// <summary> /// workout detail icon. /// </summary> public string icon { get; set; } /// <summary> /// item layout value bounds. /// </summary> public rectangle valuebounds { get; set; } /// <summary> /// item layout name bounds. /// </summary> public rectangle namebounds { get; set; } /// <summary> /// workout detail action button visibility flag. /// </summary> public bool isactionbuttonvisible { get; set; } #endregion } } itemtemplate the values provided by itemsource are used in itemtemplate. views/workout/detailspageview.xaml <cui:circlelistview.itemtemplate> <datatemplate> <viewcell> <absolutelayout heightrequest="360" horizontaloptions="fillandexpand" verticaloptions="fillandexpand"> <image absolutelayout.layoutflags="xproportional" absolutelayout.layoutbounds=".5, 74, autosize, autosize"> <image.source> <fileimagesource file="{binding icon}" /> </image.source> </image> <label text="{binding value}" fontsize="{staticresource fontsizem}" textcolor="#fff" absolutelayout.layoutflags="xproportional" absolutelayout.layoutbounds="{binding valuebounds}"> </label> <label text="{binding name}" fontsize="{staticresource fontsizexxs}" fontattributes="bold" textcolor="#aaffcc" absolutelayout.layoutflags="xproportional" absolutelayout.layoutbounds="{binding namebounds}"> </label> <button absolutelayout.layoutflags="all" absolutelayout.layoutbounds="0, 1, 1, .25" text="ok" textcolor="#1b1b7d" backgroundcolor="#aaffcc" command="{binding bindingcontext.finishcommand, source={x:reference listview}}" isvisible="{binding isactionbuttonvisible}" tizen:visualelement.style="bottom" /> </absolutelayout> </viewcell> </datatemplate> </cui:circlelistview.itemtemplate> the values modify the content in each viewcell element accordingly, so that: the name and value properties set the values of the text property of the selected label elements the namebounds and valuebounds properties set the layoutbounds property of absolutely positioned label elements the icon property sets the source property of the image elements responsible for displaying the item icon the isactionbuttonvisible property sets the isvisible property of button elements, making them visible when the given value is true read more to learn more about the implementation of circlelistview in the workout application, please see this tutorial. thank you for reading the tutorials about the workout app. for more information about this app and developing for the tizen platform, please visit developer.tizen.org.
Nov 19, 2020
Dariusz Paziewski
Connect Samsung Developer Conference
webspeaker list check out the speakers who joined us at sdc22 to share their experience and expertise jonghee han vice chairman, ceo and head of device experience divisionsamsung electronics sebastian seung president & head of samsung researchsamsung electronics yongjae kim evp, deputy head of r&d team, visual display businesssamsung electronics sang kim svp & head of product & marketing, samsung electronics america samsung electronics jaeyeon jung vp & head of smartthings, mobile experience businesssamsung electronics sally hyesoon jeong vp & head of framework r&d group, mobile experience businesssamsung electronics mark benson head of smartthingssmartthings inc. anil yadav head of bixby lab, samsung research americasamsung electronics shin baik principal engineer of security team, mobile experience businesssamsung electronics alissa dornbos engineering managersmartthings inc. allan devantier vp of audio research and developmentsamsung electronics barry holland product directorsamsung electronics byungkwon kang principal s/w engineersamsung electronics charis ryu engineersamsung electronics charles lim tizen licensing pmsamsung electronics chulheon jeong software engineer, framework r&d groupsamsung electronics david kwon director of partnership & business developmentsamsung electronics david lee evp, head of samsung nextsamsung electronics donghun shin senior s/w engineersamsung electronics eldad persky vp of product & engineering, ads & datasamsung electronics eun-ae cho software project leadersamsung electronics evan artis senior product managersmartthings inc. haeyoung jun principal engineer, standards research teamsamsung electronics heinz pabst software project leadersamsung electronics hobum kwon corporate vp, platform teamsamsung electronics hosub lee software engineersamsung electronics hyun kim head of core ux groupsamsung electronics hyunju shin principal engineer, platform teamsamsung electronics hyunseok cha principal s/w engineersamsung electronics jaeho ko ux designersamsung electronics james pak corporate vp, b2b partnershipssamsung electronics jeoungju kim engineersamsung electronics jidon yeo principal engineer, data research teamsamsung electronics jihye song staff engineer, s/w architectsamsung electronics jinhoon cho ux designersamsung electronics jinwoo song principal engineer, data research teamsamsung electronics jiwon kim staff engineersamsung electronics john alioto director, developer relationssamsung electronics john couling senior vp, entertainmentdolby laboratories joohwan kim principal engineersamsung electronics joosun moon principal ux designersamsung electronics josh ross content strategist, core ux groupsamsung electronics juneho lee principal s/w engineersamsung electronics kianoosh karami director of engineeringsmartthings inc. kihwan kim corporate vpsamsung electronics kyle sporre principal product managersmartthings inc. kyunghoon han ux designersamsung electronics laura morinigo web developer advocatesamsung electronics mateusz obidzinski b2b technical support engineersamsung electronics matthew reyes pm, mobile gamingdolby laboratories minji lee wallet strategy groupsamsung electronics philip leung partnerships managersamsung electronics richard song director, b2b partnershipsamsung electronics robert white sr. directorsamsung electronics roger kibbe senior developer evangelistsamsung electronics ryan kim principal s/w engineer, tizen enterprise spmsamsung electronics sangin lee software engineer, smartthingssamsung electronics sanguk jeon head of core platform labsamsung electronics sean ginevan head of digital partnership, android enterprisegoogle llc sean park senior product manager, experience planning groupsamsung electronics seongnam oh senior technical director, video systemssamsung electronics soowan kim technical product manager, visual s/w r&d groupsamsung electronics soyoung lee principal engineersamsung electronics sungchull lee software engineer, health s/w r&d groupsamsung electronics surojit chatterjee chief product officercoinbase taeho kgil corporate vp, security & privacy teamsamsung electronics wojciech kajder head of part/b2b product and program managementsrpol/samsung youngsang shin principal engineersamsung electronics yunsik bae staff engineer, connectivity r&d groupsamsung electronics
success story mobile, marketplace
blogwelcome to the latest entry in the 2018 source code: a dev’s guide. to help devs make the most of 2018, we’re posting informative q&as with industry experts throughout the month of january. in this post, matt smith, vp of visa developer platform, shares his insights, tips and predictions for the mobile payments space. how do you think the rise of mobile commerce changes the way devs design apps? the rise of mobile commerce has forced developers to design and develop for mobile-first user journeys. the ability to conveniently find and transact on things from anywhere at any time is having a profound impact on the way developers design applications. companies are seeing the need compete on the differentiated experiences they create. consuming outside api-based services that complement your application’s purpose and thus let go of traditional development philosophies that mandated owning your entire value chain provides agility and supports focus on the customer experience. these commerce experiences rely heavily on all tenants of responsive design and a core of api-centric resources. in short, mobile commerce has pushed developers to consume and produce apis that can be harmonized to create convenient digital journeys for their customers. mobile payments are a space where devs need to collaborate with big financial players/institutions. what’s your advice to devs on strategic partnerships? devs should always keep an open mind on who to partner with. there have been many instances where defined markets have failed to adopt or partner with new technologies and ways of executing, which has caused many large name brands and companies to fail. video rental companies refused to invest in online streaming. taxi companies refused to develop or deploy an easier way to catch a ride. big retailers have almost gone bankrupt refusing to modernize and compete with online retailers. strategic partnerships can help you move forward and show you new perspective on solving problems. innovation is key, and strategic partnerships should be fostered to enable and encourage that innovation. doubts about security can get in the way of consumer adoption regarding mobile payments. how can devs ensure that the information shared across apps is secure? the goal of a mobile developer in the payment space in regards to security should be to answer the question following question: “how do i gain and maintain my customer’s trust?” security is, and will continue to be, paramount in the mobile payments industry. ssl, tls, encryption and biometrics are all technologies that every mobile developer wanting to deliver payment apps should be using. proper vetting of resources that you want to consume will help to ensure that your customer’s data is kept secure. today’s customers are willing to make commerce a daily part of their mobile routine; your app’s security should always reinforce that decision. the future of mobile payments is rapidly changing. what is the one big bet that developers should be making in 2018 when it comes to developing mobile app payment solutions? 2018 will see the continued rise of the collaborative open api ecosystem. devs will be building payment journeys that consume services cross-industry and that produce new services that are published back out for others. these journeys will include emerging standards and payment apis. consuming a partner’s flexible apis to build new mobile-first user experiences will enrich the global api ecosystem. this ecosystem lifecycle will itself become a metric of health as it relates to developers and their inter-dependency on each other. thanks to matt for sharing his expertise. be sure to like us on facebook and follow us on twitter so you don’t miss any other great content from our partners.
Jan 25, 2018
Matt Smith
announcement mobile, ai, iot, ar/vr/xr
blogin the fast-changing world of development, a new year always brings new trends and exciting technologies. for me, it has also brought a new role as a samsung technical evangelist. previously, i was a developer champion for samsung’s artik iot platform, working within the maker community. and prior to that, i was an independent developer focusing on full-stack mobile app development, hybrid and native.with that background in mind, i always say i eat javascript for breakfast, have swift and linux protein shakes for a midday snack, and enjoy open source super foods. i also have a sweet tooth for ar and iot. my appetite for development is also accompanied by a strong desire to engage with the developer and creative communities who are equally passionate about creating amazing things. that’s why i’m so excited about my new role. one of my main responsibilities will be making sure our developer community stays on top of industry innovations by providing the resources you need to create really cutting-edge work. this starts with the 2018 source code: a dev’s guide. over the next few weeks, we’ll be asking the industry’s brightest minds about the trends they’re watching and for their top dev predictions for 2018. but before we get to that, i’d like to share my personal predictions for 2018 from a developer standpoint: the evolution of artificial intelligence in healthcare from iot to voice user interfaces (vui) to autonomous cars, ai is steadily evolving around our daily activities. this is perhaps most apparent within the healthcare sector. here, ai is solving a variety of challenges in predicting illnesses by capturing and analyzing physiological and well-being data, as well as relationships between prevention/treatment and patient outcomes, just to name a few. in 2018, i see more open research data being made available and more health apis for developers to take advantage of (e.g. holistic apps, products and services). intelligent iot made easy by itself, iot generates large amounts of unstructured data. without the ability to analyze it at a high, frictionless pace, this data can be easily wasted. now, with iot playgrounds like smartthings cloud, developers will be able to create smartapps that can easily integrate third-party cloud-to-cloud devices. in 2018, i believe we’ll see a massive leap forward in the ease of iot app development and the overall functionality of these apps. the creation of new revenue streams in ar/vr/mr in the developer world, these acronyms represent many opportunities. the way we consume content, the way we make transactions and the way we socialize with the rest of world will continue to be transformed in 2018’s digital universe. with the help of partners like facebook oculus and google arcore, you will be able to develop immersive and interactive apps to engage a new generation of consumers. if you are a developer polishing your monetization strategy in ar/vr/mr, you will be well positioned to blaze revenue stream models other developers will look to as the gold standard for years to come. be sure to check back here for more valuable insights and perspectives designed to help position you for success in 2018. remember to follow #beasamusungdev on twitter and like us on facebook to make sure you don’t miss a thing. i’m excited to meet you in 2018!
Jan 4, 2018
Josue Bustos
Develop Smart TV
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
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
Develop Smart Hospitality Display
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
docseason 2, episode 8 previous episode | episode index | next episode this is a transcript of one episode of the samsung developers podcast, hosted by and produced by tony morelan a listing of all podcast transcripts can be found here host tony morelan senior developer evangelist, samsung developers instagram - twitter - linkedin guests aleksander tyszka, hyun kim, dan appelquist, aaron swift, roger kibbe, sooyeon kim, eric cloninger samsung developer conference after taking a year off due to the pandemic, we recently held our annual developer conference, sdc21 this year’s conference was a virtual conference, with insightful highlight sessions and in-depth tech talks in this episode, i sit down with several samsung insiders, to recap the many highlights from this year’s show we'll chat about one ui 4, the samsung incubation program, smartthings, bixby, our partnership with google and the new watch ecosystem, samsung internet and our new podcast platform listen download this episode topics covered samsung incubation program one ui 4 samsung internet smartthings bixby developers watch ecosystem samsung podcast platform transcript note transcripts are provided by an automated service and reviewed by the samsung developers web team inaccuracies from the transcription process do occur, so please refer to the audio if you are in doubt about the transcript tony morelan 00 01 hey, i'm tony morelan, and this is pow!, the samsung developers podcasts, where we chat with innovators using samsung technologies, award winning app developers and designers, as well as insiders working on the latest samsung tools welcome to season two, episode eight after taking a year off due to the pandemic, we recently held our annual developer conference sdc21 this year's conference was a virtual conference with insightful highlight sessions in in depth tech talks in this episode, i sit down with several samsung insiders to recap some of the great moments from this year's show we'll chat about one ui 4, the samsung incubation program, smartthings, the new watch ecosystem, samsung internet and a new podcast platform enjoy so at sdc21, one of the most interesting talk sessions that i watched was the kafir innovator session where they talked about the samsung incubation program and joining me on the podcast is someone who works closely with that incubation program, alec tyszka, who's a manager technology strategy and partnerships at samsung yeah, welcome to the podcast hey, tony, how are you doing? well, let's start with what is the samsung incubation program? aleksander tyszka 01 20 sure so samsung innovation program is an incubation program that we've launched already in europe a few years back, and that we've expanded this year in the us the program itself has two main goals is one we want our business unit so you know, different groups at samsung that work on digital appliances, tvs, smartphones, wearables, we want to give them a way to do very sort of rapid prototyping to quickly develop new products and services but very highly innovative ones things that weren't organically be created if we just did our everyday work the other one is to also be able to work with the labs that samsung have done work on, though, on long term projects, we want to have sort of all the brands that that leverage all the brands we have at samsung to create these, these this long-term vision that we have about what are the services that people are going to use? what are the products that people are going to need, and try to find a way to bring these products and services to life? tony morelan 02 22 yeah, so i saw, you know, in that session where they, you know, talked about that, that need to innovate in some of those technologies that came out of those partnerships, where you know, like the health sensors with wearables, z fold, things like that, it's pretty interesting to think that those technologies came out of those partnership collaborations aleksander tyszka 02 41 yeah, i think when we start working with cutting edge technology, and you mentioned the z fold, especially some technologies i've been that have been developed internally at samsung, for flexible and foldable screens does are quite unique, right? there's only a handful of company that that make them in the world and then if you talk of, of the scale, by which we work with these, we don't make five foldable phones, right, we make 10s of millions so sure what when you work at this scale, with those sort of cutting-edge bleeding edge technology, it just takes a lot, a lot of efforts to bring them to life and samsung alone can't really do it, we need to find partners, and we need to work with them and those are typically startups and all that all sort of the people that work around startups, incubators, accelerators, venture capitalist industry experts, in we need to find the solutions to improve the product and bring these products to life tony morelan 03 34 yeah, and i'm sure that, you know, having that collaboration with those, those innovators really help you like think ahead, thinking to the future, you know, where do you need to go? where do you need to focus your energy? so it's great that there is this program to allow samsung to work with these, these innovators so tell me what are some of the details of the of the program aleksander tyszka 03 54 so the program itself is a six-month long program, we get we'll provide some funding stun company, anywhere from 20 to 100k, depending on what the companies do, if it's hardware, a software, there's no string attached with this funding, we don't take any equity and like some of the big household names like y combinator is 500 startups and then we provide a lot of mentoring, mostly technical mentoring from our engineers and our labs sure and the idea is just to help them build a prototype help them showcase a demo to our executive immediately after the program after six months, two years, two outcomes we're really looking for and then we'll qualify as successful outcomes is either investment or commercialization meaning we'll work with the companies will leverage our solution to build a product tony morelan 04 41 ah, that's great so in the call for innovator session, what was the key highlight the key takeaway from that session? aleksander tyszka 04 47 sure the key highlight for us is really that we need partners we want to be part of the ecosystem and we want to give back that ecosystem you know, startups are a major part of that ecosystem they're very forward looking we want to, we want to leverage their ideas, and we want to contribute positively to them want to help them and we want to be able to connect with the entire ecosystem behind the startups, the universities, the vcs, incubators, we want to work with all these people that's the main takeaway is samsung wants to remain, you know, very innovative, but we want to do it tony morelan 05 22 with partners you know, my takeaway from that session was hearing that success story fibricheck, where they created that on device, ecg sensing, that would help detect irregular and rapid heart rate using ai in our in our galaxy watch and seeing that, you know, it wasn't just that we provided funding, but it was that collaboration where you know, where we helped build the medical grade application, we, you know, helped with the regulatory approval, but then also learning that that we helped with, you know, define what their business model was in their in their go to market strategy that was really neat to see that that success story that was shared aleksander tyszka 06 02 yeah, i think for especially when companies in the health space, right, we did that, that's a pretty fragmented space, right? there's a lot of device manufacturers in many different countries that have their own sort of regulatory constraints by working with these types of companies, we provide a very sort of great way, a great go to market strategy for them, it's sort of built in, it's like, here's our wearables, we sell, you know, 10s of millions of them every year and they're very standard, they're easy to integrate, and well will support older go to market, going through retail stores, and those sort of things i mean, it makes it easier for the company right to quickly grow their company and for help, specifically, that fear check is such a great example of the sort of things we're trying to achieve, right and there's a ton more we can do at that space, people are talking about noninvasive, continuous glucose monitoring, maybe hydration as well in the future, and we want to find a company building these features and try to work with them tony morelan 07 01 yeah, and, you know, just at large, we've got this enormous ecosystem, you know, with our devices, you know, with galaxy store smartthings, bixby and there's just so many areas that we can be involved with aleksander tyszka 07 11 yeah, the ecosystem we provide is it's huge and it's sometimes it's hard for us to prioritize which companies we want to bring in into that ecosystem, right but going through a program like samsung's incubation program, were able to quickly filter for the best partners and focus our efforts, our efforts, sorry, on the ones that were most contribute to that ecosystem tony morelan 07 32 so it was great to hear you know, all about the samsung incubation program, what is the best way for people to connect with your team? aleksander tyszka 07 41 so we will have a website up and running pretty soon until then you can email us at info jump@samsung com tony morelan 07 49 so there were a lot of great sessions at sdc21 what were some of the favorite sessions that you saw that developers should check out? aleksander tyszka 07 56 yeah, i think the first one i have in mind is the one on the foldable device, i have a full device myself, i really, really like it, i get a lot of comment when people see it and then when they know and looking at stuff with it, there's basically different modes, right? you can you can use the front screen and use it like a regular device but the second you fold it, like a 45-degree angle, you want the app to act differently with the application so a good example of that is what if it became sort of like a gameboy where you have your screen on one on one ends? and bottom part of your controllers? yeah and there's a lot more use case like that what about video conferencing tool where you can see other people in the top screen in the bottom screen is a whiteboard where people can collaborate so i think there's a lot of use cases that can develop and we haven't even begun sort of scratching the surface of what can be devops so i look forward to see more developers think about that start developing around that and see what they can come up with tony morelan 08 49 excellent that's great hey, alec, i really appreciate you coming on the podcast today it was it was wonderful to learn much more about what you guys are doing at the samsung incubation program aleksander tyszka 08 58 oh, thank you very much for having me tony was a pleasure excellent thanks tony morelan 09 01 so one ui four was one of the biggest announcements we made at sdc and i'm excited to have on the podcast, head of the core ux group for samsung mobile, he and kim hyun kim 09 12 hi, i'm leon kim, and for inviting me and it's very exciting to be joining podcast tony morelan 09 19 so when you why is the user interface installed on samsung devices and was originally released back in 2019 for people who are listening to the podcast that might not be familiar with the details of one ui? can you give us a brief overview? hyun kim 09 32 oh, sure one ui means entire software experience that galaxy devices are delivering to our users, meaning it actually includes productivity experience and watching videos and privacy experience, onboarding experience and all different services and apps and all that our customer can enjoy from galaxy devices tony morelan 09 56 you gave a highlight session at sdc on the soon to be released one ui four that was really insightful can you share some of the key takeaways from that session? hyun kim 10 06 sure ever since we launched the one ui, we've been emphasized our users to be able to focus on what matters at each moment so focus is one of the highlighted experience that we want to enhance, as well and when you're a 4 0 on top of it, we also want to deliver the comfort experience as well especially these days, pandemic gives our users screen for t, meaning the screen time is increasing and the number of apps that people are juggling, and for period of time that they are looking at the screen is increasing and then people are having eye fatigue and we actually really need to deliver more comfortable experience for their eyes and for their peace of mind so we took care of all those aspects when we design on ui four so we took out visual lewis's as much as possible, we took out the number of colors, we took out the number of different font sizes, minimize the visual noises, so that user can focus on and consume the important content and third test that they think it matters at the moment very comfortably also, we allow extra diem feature, when user see the screen went dark, we want their eyes to be more comfortable so we collaborate with google make the screen even darker than the darkest level right now and we believe that would be more comfortable with those new features and new design tony morelan 11 56 yeah, no, that's great and i loved hearing about the natural interactions, these intuitive interactions that are being developed into one uio 4 talk about that hyun kim 12 05 recently, people are juggling more number of apps, and they are facing the more number of features and they're consuming more amount of content, meaning we need to provide very simple ui, ui needs to be higher level of intuitiveness so we wanted to put more gesture on the content itself so that user can feel they manipulate and control content itself without looking at ui component so then, non-visual component should help users to feel the reaction when user touch the screen so we put motions, visuals and physical feedback harmonize together, so that when user touch the content and move the content and drag and drop the content, we want them to feel they are moving the real physical object to one place to another tony morelan 13 08 yeah, and those vibrations, those are called haptics, correct haptics, hyun kim 13 11 right? every version of you on ui, we enhance the haptics and this year, the direction of enhancement of haptic feedback is not only just adding a right bit back in the right place, but also, we add the haptic feedback with motion and visuals together to create a feeling of natural interaction in the physical world tony morelan 13 35 yeah, so i know that that that combination of sound animation and haptics will definitely provide for some very, very real-life device interactions talk a bit about privacy, because i know that privacy was mentioned in your session, what are some of the improvements related around privacy? hyun kim 13 53 basically, what we believe is transparency is very important so providing peace of mind, for our customer, about the privacy, the basically transparency is really important the first one is we're showing all the apps list that are using user's personal data so the user can see which apps are using which data and then user can easily access the individual apps permission, turning on and off also, on offered right corner of the device the screen is showing when camera or mic is on then icon is displayed, so that user can clearly recognize okay, camera is on mic is on and if it's not fair, then you can feel safe okay, nobody's listening or watching tony morelan 14 47 yeah, that's, that's great so coming from one ui three, what are some of the biggest improvements that we're now going to see in one ui for hyun kim 14 55 improvement wise as a new experience is self-expression, the more we research customers, the more we're sure that they're expressing themselves in many different ways and have any fun ways and they want to express their emotions and thoughts, and creativities and their identities and themselves, as they are in many different places in our galaxy one ui for we want them to enjoy expressing themselves for instance, we're launching a new tool for them to create a fun emoji pair animation for them to create their own content to express their emotions but sometimes one emoji isn't just enough for them to express their rich emotions people can choose two different images to put together and put animation to bring the combo to life and then there are chosen to emoji can be animated and delivered to their friends and family via messenger and it'll be very fun content, like exploding head yeah, you can create your own content there are many, many fun, any major that we're providing also, there are presets so we believe people will enjoy this in samsung keyboard when they communicate each other and they will express their emotion in a very fun way also, we enhance photo editor a lot so that people can express their thoughts and creativity when they picture and edit it and share every year we've been enhancing photo editor video earlier about this year, we redesigned editors so that user can see this very seamless and easy, simple, intuitive editor ux tony morelan 16 54 and i loved when you spoke about extracting wallpaper colors to be used throughout the ui experience hyun kim 17 00 oh, yeah, that's, that's another very fun feature, except for expression isn't just about what you send out self-expression is about your styles, you can style your phone, you can extract the color from your wallpaper, you also can pick your wallpaper from your gallery so you can choose whatever your favorite pictures from your gallery and put your wallpaper and then we're providing four different color palette that can apply to your one ui and you can choose one of the four options, then your ui color will be changed and color schemes will be different or depending on what you're choosing and this is a little different than other like theming services because when your eyes original usability and identity are still there but the color keeping the readability usability, the only the color is going to be changing yeah and you can still enjoy the benefit of one ui with only the color that you choose from the wallpaper tony morelan 18 12 yeah, in you get that single experience across all platforms, meaning you know all of your devices, whether it's your phone, your tablet, your watch galaxy book, tell me a little bit more about that cross-platform experience, hyun kim 18 24 we have been putting effort, the device eco system experience this year, we launched the wherewith for when you watch and more than ever, we put the best seamless experience between galaxy book galaxy watch, and flip and folder and phone and tablet and we also launched enhanced version of quick share the experience for sending receiving files between devices, click share allows users to send and receive any type of files to your friends who has galaxy and to your devices and receive as well quickly if the devices are around you tony morelan 19 14 yeah, that's great so tell me when will when ui for be available on different devices hyun kim 19 21 we're really excited to be releasing one ui four update before the end of the year tony morelan 19 26 and to upgrade is it as simple as going into your menu settings, your software, update menu settings and just selecting the upgrade? hyun kim 19 35 yeah, you can update it go to settings and software update tony morelan 19 39 excellent so for developers that want to learn more about when ui for what is the best way, hyun kim 19 45 you can go to websites like www dot developer at samsung com/one-ui tony morelan 19 56 what other sessions at sdc would you suggest that developers checkout? hyun kim 19 59 sure, there are many, many exciting helpful sessions but one other person that i want to recommend is one of the highlights session for the title was what's new in foldable and they're talking about multitasking capabilities and flex mode to help developers optimize their own apps and optimizing web pages supporting flex mode by using the web share device posture api tony morelan 20 25 yeah, yeah and there was also there was a tech talk session that i liked, called one ui designing a more intuitive, approachable experience that was by jung woo, you that was another great, great session hyun kim 20 36 yeah, he's actually a member in my group and he has been putting a huge amount of effort to prepare that session and i know the content is very fun and exciting tony morelan 20 48 well, thanks for joining me on the podcast again it was wonderful to chat with you and about the upcoming release of one ui for sure thank hyun kim 20 55 you thanks thanks for having me here tony morelan 20 58 all right next on the podcast is someone very familiar with the show who i've had on the podcast several times now, dan, apple quest from samsung internet dan appelquist 21 06 hi, tony it's great to be back on the podcast tony morelan 21 10 excellent so dan is the director of developer advocacy for samsung internet we did an episode last year and actually did another episode earlier this year so be sure to go check out those to learn a ton about samsung internet, and what dan's team's doing but for those that might not be familiar with samsung internet, can you tell us what is samsung internet? dan appelquist 21 28 sure i'm leading the developer advocacy group of samsung internet, our group is based in in the uk, actually and we're kind of an international team what is samsung internet? samsung internet is samsung's mobile browser for android phones it's also available for any android phone, but it is shipped on samsung phones it's the purple planet you know, if you're if you're familiar with your normal samsung icon, set your one ui concept that's us that's the purple planet we also just launched a version for galaxy watch, which is very cool that's hot off the press news right now so if you've got a one of the latest galaxy watches, you can also download samsung internet for galaxy watch it's based on chromium, the chromium project, which is the same open source project that google chrome is based off of, a lot of other browsers are based on chromium however, samsung is also a major contributor into the chromium project into the chromium open source projects so we're not just taking the chromium browser and slapping our own ui on it that we're actually contributing in to chromium and we do an awful lot to build our own features and technologies into samsung internet so in, in particular, we focus on privacy so we protect your privacy with features like safe browsing, our own in house smart anti tracking technology, and the ability to install third party blockers, ad blockers, tracking blockers, that kind of thing so those are the kinds of things that we're doing to kind of protect people as they use the web and that's an that's such a key important role that browsers have we're also a great platform first progressive web apps if you have attended any of our previous sessions at previous sdcs you'll know that we're big fans of progressive web apps just briefly, a progressive web app is a web application that can be installed onto your device and looks to the user as if it is a native application but it's actually running inside the browser so good example is twitter has a progressive web app pwa many other web sites and web properties have progressive web app versions of their other applications and in fact, we just participated in a separate conference, which just ran recently in collaboration with microsoft and google, and that had a complete focus on pwa s and if you're interested in that, it's all streamable from pwa summit org tony morelan 24 06 awesome so there were some great sessions at sec related to samsung at both when it came to foldables and with extensions, can you tell me what were some of the highlights for you? sure dan appelquist 24 16 so we're really, really excited to be able to speak at sdc this year about our work with foldables so as far as foldables go, the exciting news that we're able to talk about is that we're launching an experimental api called the device posture api it's being developed in the world wide web consortium in the w three c as a proposed web standard with intel and microsoft as partners this api is launched behind a flag right now, tony morelan 24 47 what does that mean dan appelquist 24 48 behind a flag? it means you have to you have to activate it, in order to make it work it's not going to work out of the box and that's because it is experimental the reason it's like that is because we want people to experiment with this api sure, it may change, right and usually when api's are in this kind of place where are in a phase of their development where they might change their launched behind a flag, so that developers get a chance to play with it, play with it feedback into the process and by the way, laura, for my team who gave the talk on device posture api at sdc is also the person participating in the standards committee, the w three c devices and sensors working group and contributing that into that work all of that is happening on github so there's absolutely an opportunity for developers to get engaged and all of that information is in is in laura's talk as well tony morelan 25 45 oh, yeah, that's great yeah, i had laura on the podcast earlier this year that she would she was an excellent guest dan appelquist 25 50 she's, she's great she's really good we've also been working with some partners to get their feedback and to get some early implementations out there so that we can get some experience with this in particular, we're working with youtube and we're working with a company called whereby, which is a video conferencing company based out of norway okay so these are good examples of where you might want to change the ui of your web application when the user folds the device and that's basically the key element here that we're talking about and that's also why when we're talking about this new api, we're talking about it in the context of responsive design yeah, and that was a lot of the focus of laura's talk as well responsive design, meaning that the application itself responds to changes in the screen size in the orientation, that kind of thing so you are responding and being i'm adapting the ui to the to the user's needs tony morelan 26 52 yeah and i love the interactive code lab, the laura had been involved with there dan appelquist 26 58 that's right and, and that, again, can allow you to kind of sink your teeth into this api, and, you know, with code examples, and, and real tutorial about how to get up and running with this so yeah, so again, very excited to be able to do this in the virtual sdc environment tony morelan 27 20 yeah excellent so next, let's talk about the extensions, the session that that was that was given, right tell me about that so dan appelquist 27 27 yeah, my colleague cyclon gave a talk on the current state of our extensions api so we launched a third-party extensions api this year and we opened that up to a wider developer community by the way, we're on one of very few mobile browsers that actually allow third party extensions and we also have within the browser itself, you can go to the extensions menu, and you can find a list of the of the kinds of approved extensions that we have excellent but those are also they're downloadable from the galaxy store but once installed, they become part of the browser, right? so the extensions add new features to the browser right so just to highlight two of the extensions that are currently available for installation, we have the translator extension, which allows you to translate web pages from one language to another that's actually developed in house really, yeah, very, very cool, very cool stuff and we recently launched an extension from the web monetization company coil that is, that's a technology that can make anonymous micro transactions micro payments to websites that you browse from a cryptocurrency wallet and this is, this is a kind of approach that is seen by some people as a replacement for pervasive tracking networks that currently power advertising on the web one way of moving beyond that is to pay websites directly for the time that you spend on them so this is a really interesting idea we've been tracking this for a while and talking to people at coyle, who are also participants in w three, c, and a lot of the other kind of developer activities that were that we're involved in as well so we're very excited to be able to launch this extension it's their extension, but it's launched in the in the samsung browser, and you can install it and then you can start kind of paying websites through coil for the time that you spend on them it only supports websites that that are subscribed to the coil system, right so it's exactly yeah, it's early days on it, but it's something that's very exciting tony morelan 29 34 yeah, yeah interesting concept, sort of like the pay as you go yeah, format dan appelquist 29 38 yeah yeah you know, i don't work for coyle, right but one of the things i think is interesting about it is that those transactions are anonymous so it's very privacy preserving, and it fits together with our philosophy of trying to enhance and protect user privacy tony morelan 29 53 yeah, no, i know privacy is a big thing for you guys over samsung internet yeah, definitely so are there any other sessions at sdc21, that developers should be sure to check out dan appelquist 30 03 well, i would suggest checking out the session called what's new and foldables first of all, which is a kind of highlight session, give it gives a high-level overview and gives a lot of really good context about flex mode, what flex mode is, or what we're referring to as flex mode, which is, again, adapting the user experience of any application to the conditions of the folding device and how that's so important from a user experience standpoint and my colleague dongbu actually gives a brief intro in that session to the device postures api, which leads into laura's longer, more detailed talk got it, and he gives a demo a little demo of how that works as well, which is, which is very cool tony morelan 30 49 yeah, i love learning about all the multitasking capabilities with foldables that was that was great to hear yeah so if developers want to learn more about samsung internet, what is the best way? dan appelquist 31 00 well, you can visit our page on developer samsung com/internet that's got links to our blog, and we blog on medium as well but really, if you go to developer samsung com/internet you can find links there to all the places on the web where, we're present you can also follow us at samsung internet on twitter excellent, where you can always find out what we're doing and you know, we try to keep that up to date with news about samsung internet, but also just the developer activities that we're participating in the standards activities that we're participating in our team manages that twitter handle directly so it's a direct line to our team and our dms are open so if you do have questions about samsung internet, you can feel free to dm us they're tony morelan 31 50 awesome awesome hey, dan, thanks very much for being on the podcast and giving us an insight into the highlights with samsung internet and sdc21 dan appelquist 31 59 thank you, tony it's always a pleasure awesome thanks, tony morelan 32 01 dan there were some great tech talks at sdc related to smart things and lots of great new innovations for shared i'm excited to have aaron swift on the podcast director of customer and partner strategy at smart thanks hey, aaron aaron swift 32 16 hey, tony, how are you doing? tony morelan 32 18 doing just fine, lots of tech talks and even a highlight session for smart things so let's start with the session smart things find from lost to found what were some of the key points with this session aaron swift 32 28 smartthings find launched last year as a service to enable customers to locate galaxy devices such as phones, watches earbuds, your s pen pro, like whatever you might leave on the bus or the train accidentally it comprises more than 100 million find nodes and over 230,000 devices are located every day tony morelan 32 49 so a find no just to clarify, find note is that like another device that's this part of this network, aaron swift 32 55 yeah, like a phone or a tablet, a galaxy phone or a galaxy tablet, running the smartthings app with smartthings fine and as you saw, philip and moon did a great presentation talking about other hardware oems can now integrate their products with smart things fine so we have today our first smart tag device which you could attach to your keys that's available on the market now for everyone but anyone who wants to can start building their own tag devices or integrating their hardware products into the final tony morelan 33 29 yeah, i think that opening up the smartthings five network to the outside hardware oems is going to be huge and will absolutely expand the network tremendously aaron swift 33 39 yeah and they made a set of tools there's this fine device sdk and the test suites they make it really easy for any device manufacturer, whether it's ble, or ultra-wideband, to start integrating their devices if you're using the nordic dialogue or nxp chipset yeah, it's really easy to add the fine sdk into your device for certification tony morelan 34 01 that's going to be that's going to be great there was a session called smart things build and tell me what were some of the highlights for you in that session aaron swift 34 09 that session was led by jenny brand meyer and andy sayer are director of product management and director of engineering okay, and they talked about extending our platform, which historically has been very end user focus, you are buying samsung tvs and appliances for your home and now we're extending the platform for multifamily builders and apartment managers to put in the new apartment buildings okay, there's a new toolset with that, that will allow an installer to go set up hundreds of apartments and hundreds of refrigerators and dishwashers and washing machines and apartments really tony morelan 34 46 quickly so this is giving them the ability to sort of monitor the like what's happening with the with these devices if there's you know, you've got some sort of fault that happens within the system, they can detect that aaron swift 34 58 yeah, so property managers we'll be able to integrate your monitor their fleet of samsung appliances from their property management tool are there any tony morelan 35 08 apis or sdks? related to this? aaron swift 35 12 yeah, so one of the cool things about this new offering is there's a dedicated set of tools and api and sdk set to make it easy for property management software companies, like in trata, to come integrate and provide fleet management for all of the appliances tony morelan 35 28 the one thing that comes to mind, though, when you mentioned something about, you know, giving property managers, the ability to sort of monitor all these devices that are in these homes, comes down to privacy, what's in place related to privacy, when you're talking about something like this aaron swift 35 43 user privacy is front of mind to us, whether you are a home owner or a renter and so what we've done is we put together a new set of permissions on the platform, so that property managers only have the minimum access to data coming off of the appliance is needed to troubleshoot for failures got it if there happens to be something wrong, the property managers will be able to pull some information off of the appliances to troubleshoot the air, but they cannot tell that you're getting your 11pm glass of milk before you go to bed tony morelan 36 18 yeah, the last thing i need is my property manager knowing that i was in my freezer last night going for little ice cream bins aaron swift 36 24 right, right and so we've made sure that users are front of mind in this, that's, that's great, and that their privacy is protected tony morelan 36 31 yeah, that's super important there was also a session called smartthings edge and i thought this was really interesting this is where the execution is done locally without reliance on the cloud tell me more about that session aaron swift 36 44 in summer 2020, we announced major changes coming to our platform, this session ended up being such a long session with so many great speakers, because we are really excited to be talking about those changes sure a couple of my favorite ones are from zack and vlad talking about smart things edge before, when you use smart things to turn on a light with a motion sensor, your motion sensor would detect motion in your home, it would send that motion event to your hub up to the cloud, the cloud would tell you to run that automation, send the event back down to the hub to tell the light ball to turn on sure and that happened quickly but it's not quite as natural as still being able to go turn on the light or the local motion sensor in your home yeah so what smartthings edge does is it took the device events and the automation event and was able to start processing them locally yeah so now when you use that motion sensor to turn on a light motion is detected that goes to the hub, the automation is processed on the hub, and sent back over to the light to turn off without ever having to reach out to the cloud to confirm that event tony morelan 37 56 like what would be a device where you needed like instant, instant, you know, reaction time between the hub and the and the device aaron swift 38 05 so all zigbee and z wave and wi fi devices have the ability to run locally on the hub now with automations okay, so one of the most natural feeling ones is that example i gave with the light you want light to turn on right away? yeah similarly, if you want to be walking into a room and having the temperatures change, or having the vents open and close, the thermostat adjusts those are great use cases for local automations as well okay, what we're doing now is we're investing more features into the rules api to make more automations run locally got it so over time, you'll see more and more complex automations be able to run locally on your hub tony morelan 38 43 for edge devices is it a closed ecosystem? or is it can anyone build for edge? aaron swift 38 49 great question so we've released a collection of edge devices on our smartthings developers github repository that anyone can reference and then any hardware oem can add their fingerprint or their devices to that repository anyone can build their own edge devices if they want to tony morelan 39 10 wow, that's, that's, that's great so i saw there was a highlight session building the future smart home today that talked about the new matter standard can you tell me what was shared in that in that session? aaron swift 39 21 matter is the foundation for smart homes of the future? over 200 companies have come together to develop a standard that is going to be the basis for smart home devices to integrate in the future tony morelan 39 34 would you say that like today the is the ecosystem? is it pretty fragmented? aaron swift 39 39 correct there are all sorts of different smart home standards from all sorts of different companies out there, and each one operates just a little bit different from each other, which makes it hard for device manufacturers to integrate with each platform mater is going to take that fragmentation and create a common application language and data model that will apply across all the data from smartphone platforms, regardless of tony morelan 40 02 yeah, i think that's going to be great, especially for consumers so that they don't have to like decide between which technologies they want to, to purchase that it's all going to kind of seamlessly work together aaron swift 40 12 correct and if you buy a light bulb with the with the matter logo on it, you will know that it'll work with smart things, or any other matters supported ecosystem tony morelan 40 21 that's awesome that is super, super great to hear so you've talked a lot about all these different technologies related to smart things what's the best way for developers to learn even more about smart things? aaron swift 40 34 the best place to go for more information is developer samsung com/smartthings from there you can learn more about building edge devices or cloud devices or stay tuned for future updates on our investment in matter you know all of the sdc sessions on smartthings were great are there any other sessions that you would recommend developers checkout i'm personally a bit of a tv nerd so i'm really excited for redefining the experience of watching tv and what's new in samsung smart tv services tony morelan 41 04 yeah, no, i know, a bunch of the people over the tv plus and it's a great group and doing a lot of amazing things over there a lot of great content coming out that's exciting excellent hey, aaron, i really appreciate you coming on the podcast it was great chatting with you and learning a bit more about smart things and looking forward to chatting with you again in the in the near future aaron swift 41 22 great thanks, tony tony morelan 41 26 so next, i'd like to welcome roger kibbe to the podcast senior developer evangelist for bixby samsung's intelligent assistant technology welcome, roger roger kibbe 41 35 well, thanks you and i talked gosh, was probably over a year ago yeah, actually on the podcast so i'm excited to be back and talk to you about what's new and what we just saw at sdc yeah tony morelan 41 47 so it was i think about a year and a half ago safe to say that a lots happened since then so tell me what is the latest with bixby developers? roger kibbe 41 55 yeah, so we just announced several things that sdc are highlighted some things that changed first thing i want to talk about is some of the ways we've made it easier to develop for bixby and these weren't new announcements, but kind of highlighting some of the changes we've made over the past year or so and so a lot of these are focusing on improving the developer experience, one of the things we did is we created a new training ui so use the training ui to create natural language training and one of the great challenges and voice experiences is to get your natural language training, working well after all, it's the way users interact with all the business logic that you've written so that's a great challenge and so we built a new ui to make that more intuitive and hopefully easier and simpler to build great experiences we also built something we call the component gallery because bixby is on multimodal devices, there is a ui for bixby experience and the component gallery is a wysiwyg component editor so i'm writing some code for what we call bixby views, i can pop up the component gallery, configure something graphically, and it just dumps the code right in so it just makes it easier and then finally, we made it super simple to load a capsule directly from github so we have a bunch of sample code on github and now directly in the studio you can load that sample code from github without having to go and clone it or download it and go through all the previous hassles he had to do so just an example of some of the improvements we made to make it frankly, just easier if your day to day life as a developer developing something for bixby tony morelan 43 32 awesome so let me ask on the end, that component gallery actually was watching one of the sdc sessions on that is pretty cool so just to clarify, this is where like on the device when you give a voice prompt, and the device bixby reacts to that you can then have graphic images appearing on the device is that correct? roger kibbe 43 50 yeah, yeah so you can either when you're basically whenever bixby is communicating with the user, you can actually have a graphical ui on there that's complimentary and it also could have things like buttons on it, or sliders or controls, because one of the things is all these samsung devices so you know, the phone, the watch the television, the tv, all have a ui on there so bixby is not just a voice experience, but it's really a multimodal experience so you need to build graphical ui, we built a tool to make it pretty darn easy to do so tony morelan 44 26 so i heard a bit about bixby on windows tell me tell me about this new announcement roger kibbe 44 30 yeah, so brand new so bixby is available on the galaxy book notebooks so there's the samsung's newest notebooks so bixby is right there is a command key to launch bixby can turn on hi bixby so you can talk to your windows notebook you can ask questions and you can have it control smartthings home automation, you can ask it to find files you can ask them to change windows settings so right now, you know it's focused on a fairly narrow set of things but i'm super excited about we have this brand-new device, a windows laptop, what can you do with a voice front end in front of that? and what are ways where we can make it simpler and easier for a user to use their laptop? by talking to it? to my mind? there's a lot to be discovered there yeah, what we created is kind of step one in a journey toward, you know, making voice a modality that makes it easier for us to interact with our technology, which is what it's all about yeah, exactly tony morelan 45 31 and you had mentioned smart things there was a session at sdc titled enabling intelligent voice control on your iot devices and i know in that they talked about smart things and a lot about bixby tell me, what were some of the key takeaways for you from that session? roger kibbe 45 45 yeah so we introduced something called the bixby home platform, and it's a way of interfacing what you've done a big sweet voice with some of the smart things capabilities and the best way to explain it is for me to give some examples of what you can do and so first example is i might say hi, bixby turn on the dining room lights now if i'd set up dining room lights in smart things, boom, work great today but if i hadn't set up something called dining room lights, today, bixby re prompt you? or say, i can't find dining room lights, that's not a really good user experience sure so what you can set up with the bixby home platform is a lot more smarter logics so hi, bixby turn on the dining room lights, because we can say sorry, i can't find dining room lights, but you have kitchen lights, your bedroom lights, you have den lights? which one would you like to turn on? and so then you kind of the user asked for something that it didn't understand but at a set of airing out? it's like, well, i know you wanted to turn a light on yeah, here's the lights i can turn on and so i kind of prompted the user to, you know, what's the right can you want, much like we would do, frankly, a natural conversation tony morelan 47 00 exactly if roger kibbe 47 01 you ask me something that i didn't understand, i'd probably go can you clarify that? right yeah and so and this is a little bit of adding that kind of logic there so i think that's one great example of just a quote unquote, air becoming a success sure the other thing i want to highlight, and i think this is where it gets really interesting, and frankly, pretty sexy, to me, is where you're actually taking the voice input and you're taking what the iot device, its state and what it's sensing and combining them for some intelligent response okay, so let me let me give you an example so i could say hi bixby, turn on my air purifier, yeah, buy an air purifier, boom, today would turn it on all good but now with the bixby home platform, i can set it up so when i say hi bixby turn on the air purifier, instead of instantly turning on, i can go query the air purifier and say, hey, you know, what's, what's the air quality? okay, and if air quality was moderate, or acceptable, boom, i just turn it on and the default fan speed, maybe medium is on but let's say the air quality is poor well, then when i query it back and says, oh, air quality is poor now i can say, well, you want to turn it on and the air quality is poor i'll turn it on but i'm actually going to turn on and turn the fan to high so you're getting this this feedback loop? it's really, you're getting the user what they asked for, you're getting the state of an iot device you're combining those together? yeah and then the action is just smarter to my mind, this is pretty, i say, sexy and exciting because if you think about this, this is getting into much more intelligence sure the devices know, i know what you asked for, i know the state, i'm going to take the most intelligent action based upon those two inputs and that's what bixby home platform is all about it's really a development tool that lets you build experiences, like what i was just talking about tony morelan 48 59 yeah, i absolutely love that and i loved when he said in the session, that there's they're planning to open this up to partners and also to third party devices yeah, reach is going to be huge roger kibbe 49 10 absolutely well, i mean, i think that's one of the big things with a smartthings ecosystem, right is it's not just for samsung devices, but it's for, you know, devices from dozens or hundreds of manufacturers so if i can read some information on the device, i can get that information and i can do something very logical and just make things work more intelligently isn't that what we all want from our technology? tony morelan 49 32 exactly, yeah so on that note, you know, something i saw also very interesting in that session was the bixby home studio i absolutely love the whole idea of, you know, with your mouse, you can just drag and drop it and build out, you know, these experiences, all without coding yeah, that's on bixby home studio so like that is roger kibbe 49 50 the tooling behind what the experiences that i just talked about, so that you could intuitively built out, i use that air purifier example because actually, if you look at the session, they built out that exact experience and i think except i encourage people to go take a look at that because that is a really good way to kind of understand what i'm talking about, and hopefully get you excited about, huh, wow, there's something cool that i could build as an end user experience tony morelan 50 22 yeah and the demo they gave was pretty in depth i mean, this is not just a you know, they didn't just skim over the, you know, the concept of bixby home studio, they actually went through and built it out yes, it was pretty nice so that was an awesome session but i know there were a bunch of other sessions all kind of related to, you know, smart things in bixby what were some of the other sessions that you would suggest developers to check out? roger kibbe 50 44 yeah, so i would definitely check out the two bixby sessions that we that we mentioned and as you can see, a lot of the focus is on bixby and smart things yeah so if you're a bixby developer, i would suggest you check out some of the spark thing sessions and understand that, because i think a lot of the focus of what we're looking at is, hey, how do we get home controller devices to work super, super well with voice so that and that really is a dance between what bixby is doing and what smartthings is doing, and building that together and that's what the bixby home studio is all about so understand the two sides of the equation and then you'll understand and hopefully can build some really cool tony morelan 51 27 stuff yeah, i love the collaboration that's happening between smartthings and bixby so if developers want to learn more about bixby what's the what's the best way? roger kibbe 51 37 i yeah, so first thing would be go to bixbydevelopers com and that's a homepage for everything bixby that's download the studio, where we have our documentation, and just a bunch of information the other thing is we have a pretty active youtube channel so just look for bixby developers on youtube, youtube slash bixby developers, loads and then pretty much everything we do that's new, or we introduce a new youtube video, we would definitely post that to twitter okay, so that's twitter and that's bixby developers and then i do a weekly like tech tip of the week, like a two-minute video tutorial, and that's posted to twitter as well or also facebook so you can find that on facebook and then finally, i am the host of a podcast yeah, i guess focuses on all things voice not just bixby it is called bixby developers chat you can find it in your favorite podcast player or you should be able to ask your voice assistant hi bixby play bixby developers chat, podcast or another voice assistant and all of them should be able to play it so that is another resource tony morelan 52 45 that's awesome and it's a great podcast i have listened to your to your work you do you do an excellent job from one podcaster to another roger kibbe 52 52 well, thank you that's the kind of compliment you'd like to hear because we all understand the challenges and what you need to do to make a great podcast tony morelan 53 01 guests and let me remind everyone go check out that episode we did it was in the first season with roger, you can learn a bunch more about bixby and how to get started creating voice assisted capsules roger kibbe 53 11 well, thanks, tony really appreciate it and go check out those sdc videos to get a really more in depth understanding of the things we've talked about today tony morelan 53 19 thanks, roger banks one of the biggest announcements we made this past year is our latest watches now run on a new operating system called wear os powered by samsung and joining me on the podcast today is su yong kim, one of the software engineers here at samsung that has worked closely on our new watch ecosystem hey, sam thanks for joining me on the podcast today sooyeon kim 53 38 hi, tony thanks for having me today my name is yan qin and i'm a software engineer at samsung i'm very excited today to briefly recap our sdc sessions on samsung galaxy watch and where it was powered by samsung, which we jointly built with google tony morelan 53 55 yeah so there were several sessions related to the new watch ecosystem in the unified platform what would you say are the benefits of the new wear os powered by samsung? rooyen kim 54 04 so there are many, many benefits but first, we have created a seamless and deeply connected experience across not only samsung galaxy devices, but also for wear smartwatches and android smartphones with this new unified platform, we want to expand our ecosystem bring greater scale to our developer community, and at the same time, delight consumers with a variety of choices from watches to watch faces and apps tony morelan 54 33 yeah, it's true not only this, the developer community going to expand it but also the consumer reach is going to grow even wider can you talk about the growth of the smartwatch market over the past several years? sooyeon kim 54 44 well, the smartwatch market is continuously growing and in fact, according to counterpoint research shipments grew by 35% for the first quarter of 2021 compared to last year and after samsung galaxy watch for launch before august, we once again recognize this explosive growth and will continue to work hard to meet the demands of this growing market tony morelan 55 08 yeah, i agree as smartwatches get smarter than market demand is only going to increase can you tell me what are some of the new and exciting apps available for the new wear os powered by samsung? sooyeon kim 55 19 so users can enjoy familiar samsung apps like samsung pay smartthings and bixby but now google apps are also available like google maps, and youtube music we are also partnering with a wide variety of partners and developers on apps that are available for download from the play store on your watch on your phone there is also a dedicated category for watch apps, so you can easily browse and download them directly to your watch tony morelan 55 46 yeah, i love that youtube music is now available on galaxy watch for many people are buying the watch because they like to track workouts and have an active lifestyle and listening to music has always been a key component to working out can you tell me how is the new samsung galaxy watch for taking advantage of the health and wellness market? sooyeon kim 56 03 so we want to help users keep track of their health status and fitness activities so we brought groundbreaking health features and sophisticated sensors to our new samsung galaxy watch four in selected markets users can check body composition, blood pressure, electrocardiogram skeletal muscle mass based on the tablet grade water, fat percentage, and so on tony morelan 56 26 yeah, it's absolutely amazing that with this little device on your wrist, you can now check things like skeletal muscle mass and fat percentage and can conduct an ekg test can current android developers build watch apps for the new wireless powered by samsung and publish just as they've done before sooyeon kim 56 41 so we aim to make every step of watch app development from ease of bill to market launch as simple as possible with this new unified platform so yes, android developers, you can continue to build your apps within this familiar environment using android studio with watch emulators and existing and new wear os specific api's developers can also deploy and increase exposure for their apps with the watch apps category on the google play store tony morelan 57 11 yeah, so my background is in graphic design and for me, my biggest question was, were we going to build a new tool that would allow designers to create watch faces for the new unified platform? and when they learned the answer was yes, i was really excited so what are some of the new exciting features with the new west powered by samsung watch base design tool, watch face studio, sooyeon kim 57 31 anyone can download, design and publish watch faces for whereas on the play store, you don't have to learn how to code and just need to explore the new design tool watch face studio for more details there is a separate tech talk session on this tony morelan 57 45 yeah, so that session was called introducing the new watch face studio, it was a great overview of the new tool that showed just how easy it is for someone to create a watch face without any coding what are some of the other sessions from sdc21 that watch face developers should check out? sooyeon kim 57 59 oh, first there is the highlight session watch ecosystem or new era where we cover the new samsung galaxy watch ecosystem at a high level then there are tick tock sessions, build your app and the new watch ecosystem is where we specifically talk about watch app development and run through a range of api's by inviting a special guest from google and there is also a session on a new health platform that runs on where was powered by samsung tony morelan 58 27 yeah, there were a lot of great sessions all related to wearables, and lots of new opportunities for developers what is the best way for developers to learn more about the new watch ecosystem? sooyeon kim 58 36 for developers, i encourage visiting the samsung developers and the android developer sites, you can go to developer samsung com/galaxy-watch and also developer android com/where i really appreciate you coming on to the podcast today and giving your insight in to the new watch ecosystem super exciting times thanks tony thanks for inviting me so tony morelan 58 51 i'd like to welcome back to the podcast, eric clung injure, who leads developer relations at samsung eric and i did a pre sdc podcast where we gave a little preview on what to expect it sdc21, and highlights from some of our past developer conferences if you haven't checked out that episode yet, be sure to go back in and give it a listen eric, welcome back to the podcast eric cloninger 59 22 hey, tony, that was a lot of fun you know, we've been doing conferences for years and even though sdc21 was a virtual conference, it was a lot of work and a lot of work by a lot of people at samsung, yourself included and you know, i'd like to really give a shout out to everybody who put in a lot of effort a lot of late nights and all on it so i hope that the people who listened to the keynote and the spotlight session and all the technical sessions got something out of it yeah and hopefully next year, we can do this live yeah, tony morelan 59 54 no, i'm looking forward to that but yes, it was it was a great virtual conference so i've asked eric to join me on this episode to chat about the sdc session that i gave called grow your podcast audience with samsung eric cloninger 1 00 06 earlier this year, samsung made it really easy for device users to listen to podcasts can you share? what is the new podcast platform? tony morelan 1 00 14 yeah, so the new podcast platform, it's super easy to access from your device on the home screen, all you do is swipe left, which is our minus one screen that is samsung free, which is basically free entertainment from samsung all in one place there's four tabs there so there's the watch tab, which is if you wanted to stream tv, there's the read tab, if you want it to read news, there's the play tab, which is playing games and then of course, there is the listen tab, which is all about listening to podcasts eric cloninger 1 00 47 so who can access all of that content with samsung free? yeah, so tony morelan 1 00 50 samsung free is available on all of our latest devices so this is basically the note devices and s series going all the way back to s nine plus all the versions of z fold in z flip right now samsung free is only available in the us but we are expanding to europe soon i've been told that by the end of the year, we will be hitting some european countries eric cloninger 1 01 12 that's great so why did we launch a new podcast service? tony morelan 1 01 15 samsung's podcast strategy is to make it easy for the millions of samsung device users to listen to their favorite podcast shows and discover new episodes quickly and easily and also it gives publishers an impactful way to reach new listeners and really expand their audience eric cloninger 1 01 31 so how do those publishers bring their shows to samsung so grab tony morelan 1 01 34 your url from your podcast rss feed, and you can find that from your podcast hosting provider, take that rss feed in go to samsung podcast com sign up for a free samsung account and all you do is fill out a short form that allows you to import your rss feed url typically, it takes less than five minutes for you to fill out that form and that quickly, your show is now available on all of the samsung free devices eric cloninger 1 02 00 so what samsung free and the podcast platform doing to help publishers get their shows discovered tony morelan 1 02 05 so our editorial team is always looking for new and exciting shows to promote every week, we feature about seven new shows on our homepage and these promotional features have been extremely valuable for publishers in fact, there was one publisher in mind recently, marty ray project chats he saw a 2,000% increase in downloads just after being featured on our homepage so that was really great to see the value in that promotion for him eric cloninger 1 02 29 yeah, that's incredible numbers there so you're the host of our podcast, the samsung developer podcast is that how you got involved with the podcast platform team? tony morelan 1 02 39 exactly they reached out to me when they were first building the service and eventually asked if i would help promote it i said, absolutely that's when they asked me to present an sdc so you can check out my session and learn much more about the new podcast platform eric cloninger 1 02 53 right so the sdc content that is on the website is available for anyone to see at any time so are there any other sessions on the sdc21 website that potential podcasters and developers should check out? tony morelan 1 03 10 yeah, well, i would say what really got me excited was seeing all of the game focus sessions that we had up there so there's one session called galaxy store games focused developer friendly that was a great session on all the new game focused improvements for both gamers and developers and there was another session called games for everyone that samsung instant plays it's another great session for game developers to learn how to bring their html5 games directly to galaxy store, making it easy for users to play games without having to download and install anything eric cloninger 1 03 42 that is an exciting new way for people who are interested in playing casual games to get into something new without having to download hundreds of megabytes of content so i think that's going to be a game changer for all of us yeah, definitely so tony, thank you for giving us some insight on the new podcast platform and also for sitting down with different people associated with sdc21 it was a fantastic virtual conference and it was great to hear about the sessions on one ui, the incubation program smart things in bixby tony morelan 1 04 11 yeah and i also like the interviews that we did on our new watch ecosystem, you know, chatting with dan again on samsung internet that was great and, of course, our new podcast platform i'd like to thank all of my guests today and to you, eric for taking a moment to chat about sdc21 eric cloninger 1 04 27 thank you very much, tony closing 1 04 30 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 tony morelan 1 04 46 the pow! podcast is brought to you by samsung developers and produced us by tony morelan
Preferences Submitted
You have successfully updated your cookie preferences.