Filter
-
Content Type
-
Category
Mobile/Wearable
Visual Display
Digital Appliance
Platform
Recommendations
Filter
Develop Smart Hospitality Display
docapplication security this topic describe the security of applications which run on samsung devices related info web security testing guide owasp secure software development lifecycle microsoft security development lifecycle sdl cwe list version 4 6 overview security is becoming an important issue with the increase of various smart devices in order to protect data from users and businesses, samsung devices are enhancing security in several layers, from hardware to software as samsung device applications are also software driven by samsung, the security needs to be taken into account samsung device applications can store important information such as code and key values and personal information of the user, which is an important resource that must be protected these resources can be leaked due to a variety of reasons, such as a simple mistake by a developer or hacking by an attacker in order to safeguard this, samsung device applications need to be developed according to secure by design in particular, the personal information of the user should comply with the policy related to the personal information for each country secure by design all software within the devices developed by samsung are based on the secure development lifecycle sdl model, and development step is divided into analysis, design, implementation, and testing, so vulnerability should be removed by performing a security review at each step from the same point of view, applications operating on samsung device should maintain the same security level for this, we recommend that you consider security in the application development phase by referring to the following step-by-step security review security in the analysis/design phase you should identify important information that is stored and transferred and ensure that the information is handled safely if you receive user input, you should review that you do not require more information than you need, and there is no issue with the input format you must identify the important information to be used and ensure that the information is displayed on vulnerable areas in the flow of the program in particular, when transmitting important information outside the device, you need to ensure that it communicates with the specified server through a secured channel at the time of designing, you must first define important information that needs to be protected and design it in a proper manner to protect it security in the implementation phase it must be implemented in compliance with security rules to prevent information in the software from being leaked through known vulnerabilities important information obtained in the design phase should be stored by applying security techniques such as encryption and make sure that it does not exist in plain text within the program establish secure coding rules for each language and proceed with development accordingly you must use only the minimum permissions required and notify the user of the permissions you use you should make sure that the security channel is properly set on the network, and the latest version of the technology is applied if you use encryption algorithms, you must use them securely using verified standard algorithms where vulnerabilities are not reported security in test phase security checks must be performed before deployment to prevent security issues and maintain security through maintenance after deployment before deployment, it is necessary to verify that there is no issue with analysis, design, and implementation when actually operated through simulated hacking, packet checking, etc after deployment, if a new vulnerability is found or a modification occurs in the security check, it must be patched and applied to all users as soon as possible security review process in order to maintain the security of the application ecosystem, samsung is performing security checks on the submitted applications samsung checks the risk or misuse cases that may occur due to the submitted applications, and if there is an issue, the deployment process can be stopped and the application submitter can be advised to fix it application security guide this section provides basic security guidelines to consider in the development of applications for a safe and reliable application running environment, we recommend that you proceed with the following points in the development phase data protection three key factors for data protection are confidentiality, integrity, and availability if an application sends or stores sensitive information, the application must encrypt data stored on these devices and protect it from attackers it is very important to protect sensitive data such as user credentials or personal information in application security if the mechanism of the operating system is not used correctly, sensitive data can be unintentionally exposed definition of sensitive data personally identifiable information that can be exploited for identity theft for example, resident registration number, social security number, credit card number, bank account number, health information, etc sensitive data that can lead to loss of honor and loss of money if leaked all data that must be protected for legal or compliance reasons security item description data protection sensitive data, such as passwords or pin data, should not be exposed through the user interface the key values used by the application must be hardcoded or not stored in plain text sensitive data should not be stored in an application container or external storage sensitive data should not be recorded in the application log sensitive data should not be shared with third parties unless it is necessary in the architecture sensitive data should not be shared with third parties unless it is necessary in the architecture keyboard cache must be disabled from the text input that processes sensitive data sensitive data should not be exposed even during internal communication you should ensure that the data stored in the client-side storage ex html5 local storage, session store, indexeddb, regular cookie, or flash cookie does not contain sensitive data make sure that you have provided clear t&c for the collection and use of the provided personal information and that you have provided selective consent to the use of that data before you use it reference links european union general data protection regulation gdpr overvieweuropean union data protection supervisor - internet privacy engineering networkapplication development privacy guide table 1 data protection security description and reference links authentication if there is a feature to log-in to the remote service by the user, it must be configured through security design even when most of the logic is operating on a remote service, the device must also meet security requirements on how to manage user accounts and sessions security item description authentication if the application provides remote services to the user, user name and password authentication must be performed from the remote service if you use status storage session management, the remote service must authenticate the client request using the randomly generated session identifier without sending the user's credentials if using stateless token-based authentication, the remote services must provide signed tokens using security algorithms when a user logs out, the remote service must end the existing session table 2 authentication security description access control an application can access a resource only if it has access to it security item description access control application must require only the minimum access required application must use the privilege that match the permissions and specify the privileges used when accessing user data, make sure that the principle of minimum access privilege requirement is followed applications must have access to apis, data files, urls, controllers, directories, services, and other resources with minimal access required you should verify and process all input from external resources and users this should include data received through the ui, a user-defined url, inter-process communication ipc , etc if an application uses a completely unprotected custom url, you should not export sensitive information important data or apis must be protected from user access other than data owners reference links owasp cheat sheet access control table 3 access control security description and reference links communications when the network is used, the application should not display the transmitted/received content using a secured channel security item description communications data must be encrypted on the network using tls transport layer security security channels must be used consistently throughout the application the setting of the security channel must be configured to protect information safely the data being transmitted must be protected from being snatched/taken over in the middle ex defence against man in the middle attack reference links owasp – tls cheat sheet table 4 communications security description and reference links input validation you must defend the command insertion attack through validating the validity of input value input value validation should be considered at all stages of development security item description input validation input values must process the data based on type and content, applicable laws, regulations and other policy compliance, and define how to handle it you must ensure that input validation is performed on a trusted service layer you need to check whether it protects against parameter attacks such as mass parameter allocation attacks or unsafe parameter allocation all possible input values e g html form fields, rest requests, url parameters, http headers, cookies, batch files, rss feeds, etc must be checked using validation ex whitelist you should check whether the values entered are in the correct form in well-defined schemas, including allowed characters, lengths, and patterns the url redirection and forward should display a warning that only whitelist targets are allowed or that you are connecting with potentially untrusted content make sure you use memory safety strings, secure memory copy, and pointer calculation to detect or prevent stacks, buffers, or heap overflows in order to prevent integer overflow, you need to make sure that sign, range, and input validation techniques are used reference links xml external entity xxe prevention cheat sheetreducing xss by way of automatic context-aware escaping in template systems table 5 input validation security description and reference links password management in case of application with different user password, security settings are required for them security item description password management you must ensure that the password does not contain spaces and cut/copy is not performed in the password change feature, you should check that the user's current password and new password are required it is recommended to provide a password strength meter so that users can set a stronger password it is also recommended to provide rules that limit allowed character types uppercase letter, numeric, special characters you should check that it is recommended to change your user password within the right due date do not store the user password in the application's properties or settings file in plain text or recoverable form passwords must be stored, transferred, and compared in a hashed state using a standard hash function to prevent random attacks, you should use the login limit number of login or captcha default password should not be generated make sure you do not show the key information, like passwords in the log reference links cwe-804 guessable captchacwe-836 use of password hash instead of password for authenticationcwe-257 storing passwords in a recoverable formatcwe-261 weak encoding for passwordcwe-263 password aging with long expiration table 6 password management security description and reference links session manager a session is a technique for controlling and maintaining the status of a user or device interacting with one user in a web application a session has a unique value for each user and cannot guess or share that value security item description session manager you should check that the session token is not exposed/displayed in the application's url parameter or error message make sure the application generates a new session token from user authentication you should check that the session token is stored using properly secured cookies or security methods you should check that a session token is generated using a standard encryption algorithm make sure the session is not reused by verifying that the session token is invalid when logout and session expires reference links owasp session management cheat sheetalgorithms, key size and parameters report 2014 table 7 session manager security description and reference links error handling the purpose of error handling is to allow applications to provide security events related to monitoring, status check, and increase in permission, and not just creating logs security item description error handling you must ensure that common error handling formats and access method are used you must make sure exception handling is used on the code base to explain expected and unexpected error conditions you must ensure that other error handlers that can prepare all unprocessed exceptions are defined in case of an error, you must make sure that the message shown to the user does not contain application-related technical or sensitive information we recommend using separate error codes for error support table 8 error handling security description release check the following before releasing the application security item description release application must be signed and distributed with a valid certificate, and the private key must be properly protected debugging code and developer support code test code, back door, hidden settings, etc must be removed deployed applications should not output or record detailed errors or debugging messages libraries and frameworks etc used by applications should be checked for known vulnerabilities the equipment used for release must be able to respond to external threats viruses, hacking, etc it should be built in release mode a separate debug message should not be left from the application if you include binary, debug information should be removed if a vulnerability occurs after release, you should update the application as soon as possible and always keep the latest version table 9 release security description
Distribute Galaxy Store
doccontent publish api the content publish api is used to view, modify, submit, and change the status of apps registered in galaxy store seller portal and provides programmatic access to the same types of functionality provided by seller portal the content publish api is part of the galaxy store developer api you must meet all of the requirements of the galaxy store developer api including, but not limited to, creating the access token and including the access token in the authorization header of every content publish api call for more information about registering apps, app status, or using seller portal, refer to the galaxy store seller portal user guide the following is a quick reference to the content publish apis name request description view seller’s app list get /seller/contentlist view a list of all of the seller's registered apps view seller’s app details get /seller/contentinfo view information about one of the seller's registered apps modify app data post /seller/contentupdate modify app information, including images, icons, and binary files, after an app has been submitted and is for sale in galaxy store submit app post /seller/contentsubmit submit an app for review change app status post /seller/contentstatusupdate change the status of an app registered in seller portal create file upload session id post /seller/createuploadsessionid generate a session id required to upload a file file upload post /galaxyapi/fileupload upload files required for app submission or for updating an app authorization header parameters every request must include authorization header parameters which specify the content type, your access token, and service account id see create an access token for more information about how to create an access token and service account id attribute type description authorization string required use bearer <your-access-token> where <your-access-token> is the access token you requested from the galaxy store authentication server service-account-id string required the service account id used to create the jwt associated with the access token can be found in the assistance > api service area of seller portal content-type string required for post, put, and patch requests must be application/json the following example shows the header used with the content publish apis curl -x content_publish_api_request \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" view seller’s app list view a list of all of the seller's registered apps request get /seller/contentlist example curl -i -x get \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ "https //devapi samsungapps com/seller/contentlist" response parameters name type description contentname string name of the app contentid integer the unique 12-digit identifier of the app contentstatus string the status of the app in seller portal standardprice double the standard price in usd united states of america dollars that determines the default country-specific price for all distribution countries paid boolean whether or not the app download requires a user payment y the user must pay to download the appn the app is free to download modifydate string the date the app was last updated in seller portal success [ { "contentname" "samsung pay", "contentid" "000001234567", "contentstatus" "registering", "standardprice" null, "paid" "n", "modifydate" "2021-02-23 01 26 26 0" }, { "contentname" "samsung health", "contentid" "000002345678", "contentstatus" "for_sale", "standardprice" "0", "paid" "n", "modifydate" "2021-02-23 00 23 19 0" }, { "contentname" "samsung gallery", "contentid" "000003456789", "contentstatus" "ready_for_change", "standardprice" "0", "paid" "n", "modifydate" "2021-02-22 23 40 46 0" }, { "contentname" "samsung music", "contentid" "000004567890", "contentstatus" "ready_to_preexamination", "standardprice" "10", "paid" "y", "modifydate" "2021-02-18 06 48 08 0" }, { "contentname" "smartthings", "contentid" "000009876543", "contentstatus" "under_content_review", "standardprice" "0", "paid" "n", "modifydate" "2020-10-06 06 44 35 0" }, { "contentname" "galaxy wearable", "contentid" "000008765432", "contentstatus" "canceled", "standardprice" "0", "paid" "n", "modifydate" "2020-08-11 04 40 27 0" } ] notethe contentstatus of registering returned by the api is the same as the updating state displayed in seller portal see failure response codes for a list of possible response codes when a request fails view seller’s app details view information about one of the seller's registered apps request get /seller/contentinfo parameters name type in description contentid string querystring required the unique 12-digit identifier of the app curl -i -x get \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ "https //devapi samsungapps com/seller/contentinfo?contentid=000007654321" response parameters see the content publish api reference for more information about these parameters success [ { "contentid" "000007654321", "apptitle" "the best app ever!", "icon" "https //img samsungapps com/content/d33aazz11a/2021/0214/iconimage_20210214000000000 png", "iconkey" null, "contentstatus" "registering", "defaultlanguagecode" "eng", "applicationtype" "android", "longdescription" "the app that solves all your problems ", "shortdescription" "", "newfeature" "", "agelimit" "0", "chinaagelimit" "0", "opensourceurl" "", "privatepolicyurl" "", "youtubeurl" "", "copyrightholder" "", "supportemail" "support@mycompany com", "supportedsiteurl" "", "binarylist" [ { "filename" "app_filename apk", "binaryseq" "1", "versioncode" "3", "versionname" "3", "packagename" "my package name", "nativeplatforms" null, "apiminsdkversion" "26", "apimaxsdkversion" null, "iapsdk" "n", "gms" "y", "filekey" null } ], "standardprice" "0", "paid" "n", "autoaddcountry" false, "publicationtype" "01", "startpublicationdate" null, "stoppublicationdate" "2023-01-02", "usexportlaws" true, "reviewcomment" null, "reviewfilename" null, "reviewfilekey" null, "edgescreen" null, "edgescreenkey" null, "edgescreenplus" null, "edgescreenpluskey" null, "notifyresult" [], "sellcountrylist" [ {"countrycode" "aut", "price" "0"}, {"countrycode" "deu", "price" "0"}, {"countrycode" "esp", "price" "0"}, {"countrycode" "fra", "price" "0"}, {"countrycode" "ita", "price" "0"}, {"countrycode" "jpn", "price" "0"}, {"countrycode" "kor", "price" "0"}, {"countrycode" "nld", "price" "0"}, {"countrycode" "tur", "price" "0"} ], "supportedlanguages" ["deu", "eng", "fra", "ita", "jpn", "kor"], "addlanguage" [ { "languagecode" "deu", "newfeature" "", "description" "the app that solves all your problems ", "apptitle" "the best app ever!", "screenshots" [ { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0223/deu/screenimage_202102230000000002 png", "screenshotkey" null, "reuseyn" false }, { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0223/deu/screenimage_2021022300000000 png", "screenshotkey" null, "reuseyn" false }, { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0223/deu/screenimage_20210223000000009 png", "screenshotkey" null, "reuseyn" false }, { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0223/deu/screenimage_202102230000000001 jpeg", "screenshotkey" null, "reuseyn" false } ] } ], "screenshots" [ { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0218/eng/screenimage_20210218000000000 png", "screenshotkey" null, "reuseyn" false }, { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0218/eng/screenimage_20210218000000001 png", "screenshotkey" null, "reuseyn" false }, { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0218/eng/screenimage_20210218000000002 png", "screenshotkey" null, "reuseyn" false }, { "screenshotpath" "https //img samsungapps com/content/d33aazz11a/2021/0218/eng/screenimage_20210218000000003 png", "screenshotkey" null, "reuseyn" false } ], "category" [ { "name" "others", "type" "one_depth_category" }, { "name" "music", "type" "general_category" } ], "heroimage" "https //img samsungapps com/content/d33aazz11a/2021/0219/eng/coverimage_20210219000000007 png", "heroimagekey" null } ] notethe contentstatus of registering returned by the api is the same as the updating state displayed in seller portal see failure response codes for a list of possible response codes when a request fails modify app data modify app information, including images, icons, and binary files, after an app has been submitted and is for sale in galaxy store tipto modify an app, use the response from contentinfo to create the input required for this request request post /seller/contentupdate see the view seller's app details successful response example for the json structure see the content publish api reference for more information about the request parameters notecontentid, defaultlanguagecode, paid, and publicationtype, must be included in the request if you are updating addlanguage, binarylist, screenshots, or sellcountry, these subparameters must be included addlanguage[{languagecode, description, apptitle}], binarylist[{binaryseq, filekey, gms}], screenshots[{reuseyn}], and sellcountry[{countrycode}] see the content publish api reference for more information curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{"contentid" "000007654321","apptitle" "publish api tester","icon" null,"iconkey" "5d33bb33-9999-0000-1111-66776633dd99", "contentstatus" "registering","defaultlanguagecode" "eng","applicationtype" "android","longdescription" "test app","shortdescription" "","newfeature" "", }' \ "https //devapi samsungapps com/seller/contentupdate" to replace a screenshot, use the reuseyn and screenshotkey parameters see screenshots parameters for more information to add to the supportedlanguages, addlanguage, and sellcountrylist parameters, append additional content to the json structure to remove all content from the addlanguage, binarylist, screenshots, and sellcountrylist parameters, leave them blank in the request for example, "addlanguage" "" to keep the existing content for these parameters neither add nor delete content , set them to null for example, "binarylist" "null" examples modify app metadata curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{ "contentid" "000007654321", "apptitle" "the best app ever!", "iconkey" "<new-icon-key>", "defaultlanguagecode" "eng", "longdescription" "new-long-description", "shortdescription" "", "newfeature" "<new-feature>", "agelimit" "0", "chinaagelimit" "0", "opensourceurl" "", "privatepolicyurl" "", "youtubeurl" "", "copyrightholder" "", "supportemail" "support@mycompany com", "supportedsiteurl" "", "standardprice" "10", "paid" "y", "publicationtype" "03", "startpublicationdate" "2021-03-31 10 00 00", "stoppublicationdate" "2022-01-02", "usexportlaws" true, "reviewcomment" "<new-review-comment>", "reviewfilename" null, "reviewfilekey" "<new-review-file-key>", "edgescreenkey" "<new-edge-screen-key>", "edgescreenpluskey" "<new-edge-screen-plus-key>", "notifyresult" [], "supportedlanguages" ["deu", "eng", "fra"], "heroimagekey" "<new-hero-image-key>", "addlanguage" "null", "binarylist" "null", "screenshots" "null", "sellcountrylist" "null" }' \ "https //devapi samsungapps com/seller/contentupdate" remove and add countries of app sales curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{ "contentid" "000007654321", "apptitle" "the best app ever!", "defaultlanguagecode" "eng", "paid" "n", "publicationtype" "03", "sellcountrylist" [ {"countrycode" "deu", "price" "0"}, {"countrycode" "fra", "price" "0"}, {"countrycode" "gbr", "price" "0"}, {"countrycode" "usa", "price" "0"}, {"countrycode" "<new-sell-countrycode1>", "price" "0"}, {"countrycode" "<new-sell-countrycode2>", "price" "0"}, {"countrycode" "<new-sell-countrycode3>", "price" "0"}, {"countrycode" "<new-sell-countrycode4>", "price" "0"} ], "supportedlanguages" ["deu", "eng", "fra"] }' \ "https //devapi samsungapps com/seller/contentupdate" remove and add app screenshots curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{ "contentid" "000007654321", "apptitle" "the best app ever!", "defaultlanguagecode" "eng", "paid" "n", "publicationtype" "03", "screenshots" [ {"reuseyn" true}, {"screenshotkey" "<update-screenshot-2-key>", "reuseyn" false}, {"screenshotkey" "<update-screenshot-3-key>", "reuseyn" false}, {"reuseyn" true}, {"screenshotkey" "<new-screenshot-5-key>", "reuseyn" false}, {"screenshotkey" "<new-screenshot-6-key>", "reuseyn" false} ] }' \ "https //devapi samsungapps com/seller/contentupdate" remove additional languages for app curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{ "contentid" "000007654321", "apptitle" "the best app ever!", "defaultlanguagecode" "eng", "paid" "n", "publicationtype" "03", "addlanguage" [ { "languagecode" "<new-addlanguage-1-code>", "newfeature" "<new-addlanguage-1-code-new-feature>", "description" "<new-addlanguage-1-code-description>", "apptitle" "<new-addlanguage-1-code-title>", "screenshots" [ {"screenshotkey" "<new-addlanguage-1-screenshot-1-key>", "reuseyn" false}, {"screenshotkey" "<new-addlanguage-1-screenshot-2-key>", "reuseyn" false}, {"screenshotkey" "<new-addlanguage-1-screenshot-3-key>", "reuseyn" false}, {"screenshotkey" "<new-addlanguage-1-screenshot-4-key>", "reuseyn" false} ] }, { "languagecode" "<new-addlanguage-2-code>", "newfeature" "<new-addlanguage-2-code-new-feature>", "description" "<new-addlanguage-2-code-description>", "apptitle" "<new-addlanguage-2-code-title>", "screenshots" [ {"screenshotkey" "<new-addlanguage-2-screenshot-1-key>", "reuseyn" false}, {"screenshotkey" "<new-addlanguage-2-screenshot-2-key>", "reuseyn" false}, {"screenshotkey" "<new-addlanguage-2-screenshot-3-key>", "reuseyn" false}, {"screenshotkey" "<new-addlanguage-2-screenshot-4-key>", "reuseyn" false} ] } ] }' \ "https //devapi samsungapps com/seller/contentupdate" register binary curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{ "contentid" "000007654321", "apptitle" "the best app ever!", "defaultlanguagecode" "eng", "paid" "n", "publicationtype" "03", "binarylist" [ { "filename" "myapp apk", "binaryseq" "1", "versioncode" "3", "versionname" "3", "packagename" "com my app20210330", "nativeplatforms" null, "apiminsdkversion" "1", "apimaxsdkversion" null, "iapsdk" "n", "gms" "y", "filekey" null }, { "binaryseq" "2", "gms" "y", "filekey" "<new-binary-file-key>" } ] }' \ "https //devapi samsungapps com/seller/contentupdate" response success status 200 success { "ctntid" "000007654321", "contentstatus" "registering", "httpstatus" "ok", "errorcode" null, "errormsg" null } notethe contentstatus of registering returned by the api is the same as the updating state displayed in seller portal see failure response codes for a list of possible response codes when a request fails submit app submit the app for review an app must be reviewed before it is offered for sale in galaxy store you can check the status of the app using contentlist or contentinfo see app review for more information about the app review process noteapps must be in the registering state before they can be submitted this is the same as the updating state displayed in seller portal request post /seller/contentsubmit parameters name type in description contentid string body required the unique 12-digit identifier of the app curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{"contentid" "000007654321"}' \ "https //devapi samsungapps com/seller/contentsubmit" response success status 204 no content see failure response codes for a list of possible response codes when a request fails change app status change the status of an app registered in seller portal you can distribute, suspend, or terminate an app request post /seller/contentstatusupdate name type in description contentid string body required the unique 12-digit identifier of the app contentstatus string body required the status to which to change your app set to one of the following values for_sale to distribute an app that has the status of ready_for_sale or ready_for_change suspended to suspend the sale of an app when the app has the status of for_sale terminated to end the sale of an app when the app has the status of suspended curl -i -x post \ -h "content-type application/json" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -d '{"contentid" "000007654321", "contentstatus" "for_sale"}' \ "https //devapi samsungapps com/seller/contentstatusupdate" response success status 204 no content see failure response codes for a list of possible response codes when a request fails create session id for file upload generate a session id required to upload a file the session id is unique and valid for 24 hours request post /seller/createuploadsessionid curl -i -x post \ "https //devapi samsungapps com/seller/createuploadsessionid" response success status 200 ok { "url" "https //seller samsungapps com/galaxyapi/fileupload", "sessionid" "d7ca6869-128e-4bfb-a56d-674d77f08848" } file upload upload files required for app submission or for updating an app the filekey in this response is used in the modify app data request refer to app registration - information on app-related image/video registration for image file requirements notethe base url for this api is different from the rest of the apis on this page https //seller samsungapps com/galaxyapi/ instead of https //devapi samsungapps com/seller/ request post /galaxyapi/fileupload name type in description file string body required file to upload, such as a binary file, image icon, cover image, or screenshot , or zip file game industry age rating certificates or other reference information needed for app review , and type of file sessionid string body required unique id generated by createuploadsessionid curl -i -x post \ -h "content-type multipart/form-data" \ -h "authorization bearer <your-access-token>" \ -h "service-account-id <your-service-account-id>" \ -f "file=@\" /icon_512x512 png\";type=image/png;filename=\"icon_512x512 png\"" \ -f "sessionid=d7ca6869-128e-4bfb-a56d-674d77f08848" \ "https //seller samsungapps com/galaxyapi/fileupload" response success status 200 success { "filekey" "5d33cb93-b399-41c0-9c41-667946736d09", "filename" "icon_512x512 png", "filesize" "86265", "errorcode" null, "errormsg" null } see failure response codes for a list of possible response codes when a request fails failure response codes the following are response codes you may see when the request fails status code and message 400bad request error code error reason in detail invalid request or content error 3001 screenshoturl count is not valid you must include at least four screenshots 3050 invalid price for a paid app if this is a paid app, the price cannot be set to zero 4106 failed to distribute content request error 4125 image upload key cannot be null if you are replacing the screenshot, you must include the screenshotkey 403forbidden 4008 this content is not yours no ownership rights of content 4105 content is not ready for distribution unable to submit/change or no ownership rights of contents 4129 content is not ready for distribution unable to submit/change beta application 7001 required parameter is missing file request error 7002 sessionid does not exist to upload the file, please get the sessionid session id does not exist
Develop Samsung Wallet
docbusiness support for special purposes overview once partner service onboarding is complete, it is possible to create your own templates such as boarding passes, coupons and tickets into samsung wallet for creating a new kind of wallet, base template creation is needed before actual wallet card creation in general, wallet card creation and modification are possible through the ‘wallet partners portal' however, a server api is provided for cases where it is necessary to manage a large number of cards cards created through api can also be checked and managed in the same way on the ‘wallet partners portal' changes to each card status can be processed at the ‘wallet partners portal', and information on how to change them should be checked through the partner server portal guide the description of each state is as follows state description draft when a wallet card is created for the first time, it becomes a “draft” state in this state, all setting values can be modified verifying in order for the card to launch and activate, it must go through the verification step the “verifying” state is a step in which the administrator requests approval in order to be verified in order to be verified, at least one csr must be registered and general information must be configured rejected the administrator registers the reason for rejection when rejecting the launched wallet card it is sent to the partner by email from the system, including the reason for rejection partners can apply for launch again by checking the reason for rejection and modifying the wallet card information active the administrator has approved partner’s requests the card is activated, and the activation cannot be canceled when the card is activated, it is made visible to the user blocked the activated card has been blocked this function can only be performed by the administrator for reference, the “testing mode” is maintained on after the card is created, and it is impossible to turn on the “testing mode” again after the “testing mode” is turned off even if the card is active, if the testing mode is on, the service is not normal the testing mode must be changed to off it is now possible to add wallet cards to a user's wallet wallet cards are added as described in 'add to samsung wallet', but in special cases, wallet cards can be added automatically only to allowed partners without user interaction api guidelines 'adding wallet card templates' defines interfaces for providers to conveniently create wallet cards to samsung wallet the generated wallet card templates can be managed for updates using 'updating wallet card templates' authorized partners can add wallet cards to users directly from the partner server using 'adding wallet cards' below [service domain] environment domain public domain https //tsapi-card walletsvc samsung com adding wallet card templates this chapter describes how to create wallet card to samsung wallet [request] type value description method post url /partner/v1/card/template headers authorization string 1024 required credential token the token can have prefix bearer" as an authorization type i e , bearer <credentials> x-smcs-partner-id string 32 required partner id x-request-id string 32 required request identifier random generated uuid string x-smcs-cc2 string 2 required country code iso-3166-1 alpha-2 of user account body parameters ctemplate object required tokenized card template actual payload data in basicjson format to communicate betweenpartners and samsung wallet this must be secured in jwt json web token format * see the chapter security for more details payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id unique value for each template created by a partner this value is set to a number of 19 digits or less cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 required main headquarters location code refer to iso-3166-1 alpha-2 for the country code cardtemplate cardtype string 100 required template card type refer to wallet cards cardtemplate subtype string 100 required template card sub type refer to wallet cards cardtemplate designtype string 100 optional the value that defines the design type of the wallet card refer to wallet cards cardtemplate applogoimg string 200 optional banner logo image url the maximum size of that image is 1024*1024e g http //www yourdomain com/banner_logo_image png cardtemplate saveinserveryn string 1 optional sets whether to save the card data this value can only be set in the ‘id card’ type cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate nonetworksupportyn string 1 optional sets whether to support to openthe wallet card under 'no network' status this feature cannot be modified after the wallet card is approved either 'y' or 'n' * default 'n' cardtemplate sharebuttonexposureyn string 1 optional sets whether to support to sharing function this feature cannot be modified after the wallet card is approved either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional if this value is set, user authentication is required when using the card, to protect the user's sensitive information either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional this value is screen capture prevention flag whether the contents view prevents screen capture cardtemplate category string 20 optional this item can only be set if the card type is “generic” set the category to get more detailed statistical information e g parking_pass, membership, reservations, insurance, health, receipt, coupon_stamp, note, photo, others cardtemplate prtnrcarddata string 1000 optional partner url of <get card data> check the url format below and implement api according to uri refer to partner server api specification e g https //yourdomain cardtemplate prtnrcardstate string 1000 optional partner url of <get card state> check the url format below and implement api according to uri refer to partner server api specification e g https //yourdomain cardtemplate prtnrmempoint string 1000 optional partner url of <get membership point> cardtemplate cardmetacp string 1000 optional partner url of <get card meta cp> cardtemplate getfulfillmentlist string 1000 optional partner url of <get fulfillment list> cardtemplate prtnrbalance string 1000 optional partner url of <get card balance> cardtemplate state string 15 optional when creating a card, it can be used to create the card's state as a “verifying” state rather than a “draft” state you can only choose “draft” or verifying”* default 'draft' cardtemplate desc string 500 optional description example * example card template object { "prtnrid" "4083254626439156160", "templaterefid" "123456781864545365", "title" "coupon", "countrycode" "kr", "cardtype" "coupon", "subtype" "others", "nonetworksupportyn" "n", "sharebuttonexposureyn" "y" } * example post /partner/v1/card/template [headers] authorization eyjjdhkioijbvvriiiwidmvyijoxlcjwyxj0bmvyswqioiixmjg1o x-smcs-partner-id partner-id-0001 x-request-id req-202303140003 x-request-cc2 kr [payload] { "ctemplate" "eyjjdhkioijkv1qilcjhbgcioijsinrpbwvzdgftcci6imnyzwf0z…" } [response] type value description http status 200 ok payload cardid wallet card id example 200 ok { "cardid" "3hdpejr6qi380", "resultcode" "0", "resultmessage" "success" } [result]] http status code description 200 200 ok 400 400 bad request requests cannot or will not be processed the request due to something that is perceived to be a client error 401 401 unauthorized authorization token is invalid or expired 500 500 internal server error 503 503 service unavailable updating wallet card templates wallet card tmplates updated through api can also be checked and managed in the same way on the ‘wallet partners portal' partners can manage all wallet cards they have created [request] type value description method post url /partner/v1/card/template?cardid={card id} headers authorization string 1024 required credential token the token can have prefix "bearer" as an authorization type i e , bearer <credentials> x-smcs-partner-id string 32 required partner id x-request-id string 32 required request identifier random generated uuid string x-smcs-cc2 string 2 required country code iso-3166-1 alpha-2 of user account path parameters n/a query parameter card id string 32 required wallet card identifier granted from partner portal * it exists when updating a specific card template body parameters ctemplate object required tokenized card template actual payload data in basic json format to communicate between partners and samsung wallet this must be secured in jwt json web token format * see the chapter security for more details payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate cardid string 32 required cardid received a response when creating a card cardtemplate templaterefid string 19 required partner template id unique value for each template created by a partner this value is set to a number of 19 digits or less cardtemplate title string 32 optional wallet card name cardtemplate countrycode string 2 optional main headquarters location code refer to iso-3166-1 alpha-2 for the country code cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url the maximum size of that image is 1024*1024 cardtemplate saveinserveryn string 1 optional sets whether to save the card data this value can only be set in the ‘id card’ type cardtemplate nonetworksupportyn string 1 optional sets whether to support to openthe wallet card under 'nonetwork' status this featurecannot be modified after thewallet card is approved either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional sets whether to support to sharing function this feature cannot be modified after the wallet card is approved either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional if this value is set, user authentication is required when using the card, to protect the user's sensitive information either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional this value is screen capture prevention flag whether the contents view prevents screen capture cardtemplate category string 20 optional this item can only be set if the card type is “generic” set the category to get more detailed statistical information e g parking_pass, membership, reservations, insurance, health, receipt, coupon_stamp, note, photo, others cardtemplate prtnrcarddata string 1000 optional partner url of <get card data>check the url format below and implement api according to uri refer to partner server api specification e g https //yourdomain cardtemplate prtnrcardstate string 1000 optional partner url of <get card state>check the url format below and implement api according to uri refer to partner server api specification e g https //yourdomain cardtemplate prtnrmempoint string 1000 optional partner url of <get membership point> cardtemplate cardmetacp string 1000 optional partner url of <get card meta cp> cardtemplate getfulfillmentlist string 1000 optional partner url of <get fulfillment list> cardtemplate prtnrbalance string 1000 optional partner url of <get card balance> cardtemplate state string 15 optional if the card status is “draft”, you can only select “verifying” cardtemplate testingmodeoff string 1 optional this value can be set only when the card status is active normal service is possible only when the testing mode is changed to off * default ‘n’ cardtemplate desc string 500 optional description example *example card template object { "prtnrid" "4083254626439156160", "cardid" "3hdpejr6qi380", "templaterefid" "123456781864545365", "title" "coupon", "countrycode" "kr", "nonetworksupportyn" "n", "sharebuttonexposureyn" "y" } * example post /partner/v1/card/template?cardid=3hdpejr6qi380 [headers] authorization eyjjdhkioijbvvriiiwidmvyijoxlcjwyxj0bmvyswqioiixmjg1o x-smcs-partner-id partner-id-0001 x-request-id req-202303140003 x-request-cc2 kr [payload] { "ctemplate" "eyjjdhkioijkv1qilcjhbgcioijsinrpbwvzdgftcci6imnyzwf0z…" } [response] type value description http status 200 ok payload cardid wallet card id example 200 ok { "cardid" "3hdpejr6qi380", "resultcode" "0", "resultmessage" "success" } [result]] http status code description 200 200 ok 400 400 bad request requests cannot or will not be processed the request due to something that is perceived to be a client error 401 401 unauthorized authorization token is invalid or expired 500 500 internal server error 503 503 service unavailable adding wallet cards a typical addition to wallet card is triggered by user interaction, such as pressing the 'add to wallet' button or link however, if the user consents, we support automatically adding a wallet card to the user for a special purpose this is an api that allows partners to provide wallet cards to users the request payload must contain information about the target to which the card is to be added this information may be related to your account, or it may be information about a card that is already registered then the user device is notified of card registration through a push notification partners wishing to use this api must be granted permission by an administrator [card data specification] card id {card id} is an id issued when the partner manager signs up for partner services and register the wallet card they want to service refer to partner onboarding guide document for details cdata actual payload data in basic json format to communicate between partners and samsung wallet see the details on the below sheet card data token card data token the specific wallet card data mentioned as cdata must be secured in jwt json web token format see a chapter security for details [request] type value description method post url /{cc2}/atw/v1/cards/{card id} headers authorization string 1024 required credential token the token can have prefix "bearer" as an authorization type i e , bearer <credentials> x-smcs-partner-id string 32 required partner id x-request-id string 32 required request identifier random generated uuid string x-smcs-cc2 string 2 required country code iso-3166-1 alpha-2 of user account path parameters cc2 string 2 conditional country code iso-3166-1 alpha-2 * required if using public domain card id string 32 required wallet card identifier granted from partner portal body parameters cdata object required actual payload data in basic json format to communicate between partners and samsung wallet this must be secured in jwt json web token format * see the chapter security for more details payload object card object required wallet card object card type string 16 required wallet card type *see wallet cards card subtype string 16 required wallet card sub type *see wallet cards card data[] array of object required wallet card data container data[] refid string 32 required a unique content identifier defined by the content provider data[] createdat long 13 required data creation timestamp epoch timestamp in milliseconds *utc±00 00 data[] updatedat long 13 required data update timestamp epoch timestamp in milliseconds *utc±00 00 data[] language string 8 required default card language code e g en, ko data[] attributes object required container of attributes data[] attributes {fields} required attributes fields by card type*see wallet cards data[] localization[] array of object optional container of localizationed language*see wallet cards localization[] language string 8 required multilingual contenct language code e g en, ko localization[] attributes {fields} for displaying a given language, ‘data[] attributes’ can be replaced by localized versions *see wallet cards account object conditional user account object account type string 16 required type of user identifier e g phonenumber, email account value string 64 required user identifier example * example card object { "card" { "type" "ticket", "subtype" "movies", "data" [{ "refid" "ref-20230304-001", "createdat" 1612660039000, "language" "en", "attributes" { "title" "samsung wallet", "mainimg" "https // /main png" *refer to wallet cards }, "localization" [{ "language" "ko", "attributes" { "title" "삼성 월렛" } }] }] }, "account" { "type" "phonenumber", "value" "+821012345678” } } * example post /atw/v1/cards/1656147182764415319 [headers] authorization eyjjdhkioijbvvriiiwidmvyijoxlcjwyxj0bmvyswqioiixmjg1o x-smcs-partner-id partner-id-0001 x-request-id req-202303140003 x-request-cc2 kr [payload] { "cdata" "eyjjdhkioijkv1qilcjhbgcioijsinrpbwvzdgftcci6imnyzwf0z…" } [response] type value description http status 200 ok payload n/a example 200 ok [result]] http status code description 200 200 ok 400 400 bad request requests cannot or will not be processed the request due to something that is perceived to be a client error 401 401 unauthorized authorization token is invalid or expired 500 500 internal server error 503 503 service unavailable resources wallet card templates & attributes boarding pass card type boardingpass sub type airlines, train , buses type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “boardingpass”* required when creating a template cardtemplate subtype string 100 conditional select from these values “airlines”, “trains”, “buses”* required when creating a template cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode off either 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240 "templaterefid" "2138240408282551312", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "boardingpass", "subtype" "airlines", "applogoimg" "http //www yourdomain com/banner_logo_image png", "nonetworksupportyn" "n" "sharebuttonexposureyn" "y" "privacymodeyn" "n" "preventcaptureyn" "n" } } event ticket card type ticket sub type performances, sports, movies, entrances, others type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “ticket”* required when creating a template cardtemplate subtype string 100 conditional select from these values performances, sports, movies, entrances, others* required when creating a template cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode offeither 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240", "templaterefid" "2138240408282551314", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "ticket", "subtype" "entrances", "applogoimg" "http //www yourdomain com/banner_logo_image png", "nonetworksupportyn" "n", "sharebuttonexposureyn" "n", "privacymodeyn" "n", "preventcaptureyn" "n" } } coupon card type coupon sub type others type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “coupon”* required when creating a template cardtemplate subtype string 100 conditional this value set “others”* required when creating a template cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode off either 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240", "templaterefid" "2138240408282551313", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "coupon", "subtype" "others", "applogoimg" "http //www yourdomain com/banner_logo_image png", "nonetworksupportyn" "n", "sharebuttonexposureyn" "y", "privacymodeyn" "n", "preventcaptureyn" "n", } } gift card card type giftcard sub type others type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “giftcard”* required when creating a template cardtemplate subtype string 100 conditional this value set “others”* required when creating a template cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode off either 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240", "templaterefid" "2138240408282551315", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "gift", "subtype" "others", "applogoimg" "http //www yourdomain com/banner_logo_image png", "nonetworksupportyn" "n", "sharebuttonexposureyn" "y", "privacymodeyn" "n", "preventcaptureyn" "n", } } loyalty card type loyalty sub type others type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “loyalty”* required when creating a template cardtemplate subtype string 100 conditional this value set “others”* required when creating a template cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode off either 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240", "templaterefid" "2138240408282551316", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "loyalty", "subtype" "others", "applogoimg" "http //www yourdomain com/banner_logo_image png", "nonetworksupportyn" "n", "sharebuttonexposureyn" "n", "privacymodeyn" "n", "preventcaptureyn" "n" } } id card card type idcard sub type employees, nationals , drivers, others type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “idcard”* required when creating a template cardtemplate subtype string 100 conditional select from these values employees, nationals , drivers,others* required when creating a template cardtemplate saveinserveryn string 2 optional either 'y' or 'n'* default 'y' cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode off either 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240", "templaterefid" "2138240408282551317", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "idcard", "subtype" "employees", "applogoimg" "http //www yourdomain com/banner_logo_image png", "saveinserveryn" "y", "nonetworksupportyn" "n", "sharebuttonexposureyn" "y", "privacymodeyn" "n", "preventcaptureyn" "n" } } pay as you go card type payasyougo sub type evcharges type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “payasyougo”* required when creating a template cardtemplate subtype string 100 conditional this value set “evcharges”* required when creating a template cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate sharebuttonexposureyn string 1 optional either 'y' or 'n'* default 'y' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode offeither 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240", "templaterefid" "2138240408282551318", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "payasyougo", "subtype" "evcharges", "applogoimg" "http //www yourdomain com/banner_logo_image png", "nonetworksupportyn" "n", "sharebuttonexposureyn" "y", "privacymodeyn" "n", "preventcaptureyn" "n" } } generic card card type generic sub type others type value description payload object cardtemplate object required wallet card template object cardtemplate prtnrid string 32 required partner id cardtemplate templaterefid string 19 required partner template id cardtemplate title string 32 required wallet card name cardtemplate countrycode string 2 conditional main headquarters location* required when creating a template cardtemplate cardtype string 100 conditional this value set “generic”* required when creating a template cardtemplate subtype string 100 conditional this value set “others”* required when creating a template cardtemplate designtype string 100 optional select from these values “generic 01”, “generic 02”, “generic 03”* default “generic 01” cardtemplate prtnrapppckgname string 128 optional app package name cardtemplate applogoimg string 200 optional banner logo image url cardtemplate nonetworksupportyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate privacymodeyn string 1 optional either 'y' or 'n'* default 'n' cardtemplate preventcaptureyn string 1 optional screen capture prevention flag cardtemplate category string 20 optional select from these values “parking_pass”, “membership”, “reservations”, “insurance”, “health”, “receipt”, “coupon_stamp”, “note”, “photo”, “others” cardtemplate state string 15 optional wallet card's state* default 'draft' cardtemplate testingmodeoff string 1 optional testmode offeither 'y' or 'n'* default ‘n’available only when updating templates cardtemplate desc string 500 optional description { "cardtemplate" { "prtnrid" "4082825513190138240", "templaterefid" "2138240408282551319", "title" "wallet card title", "prtnrapppckgname" "prtnrapppckgname", "countrycode" "us", "desc" "desc", "cardtype" "generic", "subtype" "others", "applogoimg" "http //www yourdomain com/banner_logo_image png", "designtype" "generic 02", "nonetworksupportyn" "n", "category" "membership", "privacymodeyn" "n", "preventcaptureyn" "n" } }
Learn Developers Podcast
docseason 1, episode 6 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 guest ash nazir iot gadgets in this episode of pow, i interview ash nazir, editor in chief for the website iot gadgets ash was an early advocate for tizen os, building a huge following, tizen experts with that success, ash and his team launched the website blog iot gadgets as a way to expand their coverage of hardware, software and all things internet in addition to iot gadgets, ash also runs the largest facebook group dedicated to samsung galaxy watch with over 75 thousand members listen download this episode topics covered tizen os maemo meego linux foundation tizen experts writing for iot gadgets facebook group, samsung galaxy watch more about iot gadgets based in manchester, england, iot gadgets is dedicated to bringing you the best internet of things iot news directly to you we are living in exciting times and are proud to be part of this new technology 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 02 hey, i'm tony morelan and this is pow! podcasts of wisdom from the samsung developer program, where we talk about the latest tech new trends and give insight into all the opportunities available for developers looking to create for samsung on today's show, i interview ash nazir, editor in chief for the website iot gadgets what started out as a small blog related to the tizen operating system ash and his team have built a super successful news and information focused website featuring articles on the latest software hardware and all things internet including a facebook group dedicated to samsung smartwatches that has over 75,000 members enjoy so tell me who is ash nazir? ashiq nazir 00 46 so that that's quite a deep question, but i'm going to keep it quite light and you know, you know, not too philosophical as fashion is as i'm basically a network engineer that's my background, and i'm from manchester in england as you can probably tell from the tony morelan 01 01 accent okay, now have you lived in manchester your whole life? ashiq nazir 01 05 yeah, yeah born and bred tony morelan 01 06 so when you were in school did you study network engineering? ashiq nazir 01 10 so i studied, wait for it the mathematics statistics and computing ventures in you'd probably spit them out by then but it was really my work life the jobs that i went to into after that, so i do love it support i did networking, implementation, network design, network infrastructure, and lots of other networking related jobs that was me fully immersed in that field tony morelan 01 42 so you learned after school, when you really dove into the workforce, that's where you got off your experience so when you're not network engineering, what do you like to do for fun? ashiq nazir 01 51 so this is one thing that not a lot of people will kind of understand, but i like fitness i like training and i don't work on the guns or the pythons as much as people think but i have got a modest you know and so for anybody who doesn't know, pythons guns, that sort obviously refers to your arms, which is what most guys, they love building the humps you know, they'll neglect the rest of the body 02 24 phenomenal tony morelan 02 26 yeah which is i'm kind of thinking that's not actually a typical engineer the physique of the typical engineer i think you stand out a little bit at some of these conferences ashiq nazir 02 35 um, once upon a time when i started doing a lot of this thing, and it support it sport was once the forte of the nerd yes, the computer geek in the in the closet you won't let him out when your computer's dying or near death, and then you lock him away after you use fixed your computer and i broke that mold i can tell you that so even a lot of the conferences that i attended over the years yeah, i did stand out a little bit tony morelan 03 08 yeah, definitely, definitely so i want to talk about iot gadgets so iot gadgets is a blog that you run that i know came out of your excitement for tyson os so can you tell me how you first discovered tyson and why you became so passionate about it? ashiq nazir 03 24 okay, now, so this is a little bit of a big question forgive me, i'm going to have to expand on this slightly once upon a time, there was an operating system called miko, and there was this mobile phone that they brought out, which was the nakia and 900 now, this was one of the first linux based true phones and there were lots of things that you could do you had a built in terminal, he had a real web browser that supported flash now, most people don't really know what that entails but once upon a time, you couldn't play flash animations in a mobile web browser it was just unheard of in the likes of apple and other things, you could not do those things so i started following this operating system and i started promoting it on twitter and, you know, unbeknownst to me, i became sort of a bit of an evangelist and before i knew it, i had sort of 6000 people that were following my twitter account wow and a year or so and then, you know, i was invited over to a conference in dublin now, and that was the point where meemo was becoming meego and this was when intel partnered with nakia and then it was a natural fit to me to follow on to meego and, and there's lots of wonderful things that operating system could do unfortunately, there's a change of direction and amiga was discontinued, but then intel continued with it and samsung came on board what we found was tyson which was favored by the linux foundation now for myself, i'm one of the few people that have traveled the world to almost every single ties and conference and summit all over the world being involved in ties in and helping promote it now at that time, i started a website called to ty's an expert's yes, that was to obviously promote tyson tony morelan 05 25 about what year was that? did you were started tyson experts that was back in 2011 so tyson experts at the site, they started how did you go from tyson experts to specifically iot gadgets? ashiq nazir 05 40 well, at the time were tyson experts we covered a lot of blog articles about tyson sdks ids so anybody who doesn't understand so sdks software development kit, ids, integrated development environment, and then what we wanted to do is broaden a bit of the coverage of seidman things that we were involved in and then in 2018, we started iot gadgets and started more dooms some blockchain cryptocurrency stuff, and more stuff related around iot or the internet of things tony morelan 06 16 got it okay so obviously, you've got a lot of writers that are writing for iot gadgets i'm assuming you've got some staff writers i actually did understand, though, that you do welcome guest writers so can you give me a little bit of background about your writers? and if someone wants to submit an article, how did they become a guest writer for iot gadgets? ashiq nazir 06 33 so basically, we've had lots of writers come and go over the years now and what we found is a lot of writers tend to be found on iot gadgets so even samsung themselves, they have hired a few of our writers over the years as well, tony morelan 06 53 really so they're being discovered on iot gadgets that's it that's it so ashiq nazir 06 58 yeah, we welcome people join in and, you know, if people have got the passion, love for writing and computing, by all means they can contact us and an easy way to join in is if you go onto the website, which is www iotgadgets com and just click on write to us, or write for us, shall i say, okay, you're straight through to us tony morelan 07 21 that's excellent so tell me personally, what are some of your favorite topics to cover? ashiq nazir 07 26 and so for myself, we've been very much involved in a lot of smartwatch stuff so that that's a lot of our focus is still smartwatch, based around smartwatches, the apps, the watch faces software updates, now, that kind of thing okay tony morelan 07 45 so another thing that i then when i was doing a little bit of background research on iot gadgets was that you run a pretty big facebook group that is focused on the samsung galaxy watch that i think you've got like almost 75,000 members so talk a little bit about that facebook group and tell me what it has to offer ashiq nazir 08 05 so, with the figure of 75,000, that you mentioned, we're up to actually, let me just have a quick look we're actually over 77,000 tony morelan 08 17 now really? ashiq nazir 08 19 wait not for nobody and neither does our facebook group it's a great place for people to meet each other, who are obviously smartwatch enthusiasts, and developers to showcase their apps, showcase their watch faces, and get relevant feedback you know, we all need to know what works, what doesn't work and it's an excellent place for people to promote themselves tony morelan 08 44 that's wonderful i mean, because i know that's one of the challenges, you know, when i was developing some apps, was you know, you've created this great app, but then how do you get people to, to discover it? and so always trying to find different ways to make yourself known out there is a huge challenge so, you know, knowing that you've got this facebook group with such a huge active community, that's going to be a huge benefit for developers just starting out so that's absolutely amazing to hear so tell me what's in the future for iot gadgets? ashiq nazir 09 16 well down the road, we're actually hoping to start doing a lot more wearable reviews and obviously, at the moment, people are staying at home a fair bit, for some reason, not sure why aren't doing lots more home fitness apps, and okay, for myself, i've got the background i've got the thing to sell that because hey, i love fitness so, just for me, tony morelan 09 43 that's great that's great so tell me what are some of the benefits for developers looking to create apps using tyson? ashiq nazir 09 49 so tyson, one of the propositions right from the outset, was this was going to be an operating system that you can use on a variety of devices, but on smartwatches on the mobile side, it has excellent battery life now, for a lot of people, you they might not comprehend what a brilliant battery life means until they actually try using a device when they're trying to use some fancy app and you know, they can only get half the day to assault so that was something that was brilliant right from the start and you've got solid performance, where like, say, for my smartwatch you know, i've never really known it to crash or have any issues it just performs and that's what you want from a smartwatch you want it to perform you don't want it to be another bane of your existence sure you don't want to be on the phone to tech support hey, what's wrong? you never want to talk to tech support you want to break that relationship and that's what i love about it tony morelan 10 53 that's great that's great so you've been doing this you know iot gadgets for a while i know that you've been experiencing a lot of different tyson app so you got to tell me what is your favorite type of tyson app you know what surprised and impressed you ashiq nazir 11 08 saw myself, i'm going to call back to a bit of that health and fitness stuff so obviously with samsung, they you've got the samsung health app that integrates very nicely with your titan, smartwatch and a lot of your apps that count your calories that count your steps, that they're all that information, then get stored into some health so for myself, i love that thing of, of being able to see things on my watch and then it's all collated and it's available at my fingertips to see how fast i was and what was my heart rate and, and from that data, you can then obviously, analyze your performance and figure out hey, what do you do next? exactly tony morelan 11 53 that's great so can you tell me do you have any ideas of a type an app that you would love to see a developer create ashiq nazir 12 02 you're going to call me boring i'm just going to say, perhaps but so i think it'd be great for having fitness apps where to watch us could actually chat to each other so, you know, for yourself, if you're doing a particular workout somebody else who's doing a particular workout, you can actually it'd be great to see two apps showing you performing against somebody in real time mm hmm i'm not sure obviously, that the use of the screen is really small on a smartwatch, but, you know, just look at some small metrics that can show you who's beating him i'm sure that'd be quite exciting tony morelan 12 39 that would be that would be so you know, i was doing a little bit of a research on this topic recently and saw that it was interesting a lot of the community when it comes to using a smartwatch as it relates to fitness, they don't want to be told that hey, great job you've walked, you know, so many steps today are a great job you've got it chair, you're doing exercise so the information they want to receive is that, hey, it's time to get moving that you haven't reached your goal so it's more of that motivation so it's not the encouragement that, you know, awesome, you did good today, it's more like, get out of the seat and let's get rolling so what's your thought on that sort of approach with an app ashiq nazir 13 23 um, so with that sort of functionality, we've actually got that in the titan smartwatches so every periodically if you haven't moved for a while, it'll actually tell you, hey, head up, do something and they'll give you a little, there'll be little suggestions that will show that, you know, you might want you to swing your torso around, or stand up or flap your arms around and the whole idea is that it can, you know, motivate you to start moving, because they say, you know, a, a journey of 1000 steps starts with one so even if you get up and you start doing something that is obviously a step in the right direction so that's built into the os so something that builds further onto that, another app, that state takes it another step further so then it can collate the number of steps you've possibly done that day and compared it to other days and just giving you a similar sort of, or slightly more encouragement to get you moving tony morelan 14 27 exactly think that'd be really good yeah, no, i completely agree so i know that iot gadgets is put out a lot of different articles, a lot of different blogs can you tell me which article or blog that you're most proud of? ashiq nazir 14 42 so i love the excitement in the ties and community of lights been on devices so we get a huge amount of interest in upcoming devices we're really proud of the fact that we are one of the blogs that come first with all the latest information have, you know what's happening out there? and what are the new devices that are coming out? so, no, soon, there might be some more galaxy watch devices coming out so you just have to go to www iotgadgets com, and you'll find out more that's a shameless plug so tony morelan 15 19 love it, love it so, you know, doing these for all these years, i know that you've had to face some challenges so talk a little bit about some of the challenges that iot gadgets has had to face ashiq nazir 15 30 wow so i think one of the biggest ones that and that we were fortunate enough to face and there's not a lot of websites that have this sort of issue is the amount of traffic we get so initially, like any other blog, you know, you set up, set yourself up with somebody servers out there and is able to handle your traffic and then we'd put some news out there, bang the website's dead is just way too much you know? traffic coming in to too many visitors so then, you know, you upgrade the server and then next time you have some big news, bang, that one's dead and you think, wow, this is deja vu so we've had that situation, unfortunately or fortunately so always good in the blogging world to get lots of traffic that, you know, there's so many times we had to upgrade ourselves to get to the point where we can click something and we're confident the surfers not going to die i'm going to say something i mean, we're going to publish a particular post, and the server is going to be able to handle the traffic so that's been the one unfortunately, that's been one of the biggest hurdles we've had to overcome tony morelan 16 41 and it's obviously a good challenge to have to face i mean, yeah, yeah, yeah ashiq nazir 16 48 yeah, you know, it's one of them things you might you've definitely doing something right if you've got that problem yeah tony morelan 16 55 so tell me what is the best way for people to contact iot gadgets? no, you'd mentioned the website are there any other ways that people can contact iot gadgets? ashiq nazir 17 05 yes, certainly so we've we're obviously on the web emails that are very good one so if you fire off an email to contact@iotgadgets com is a mailbox that's always monitored we're obviously on social media, which twitter, facebook, instagram, and they're all monitored as well so tell me what those your social media handles are so it's iot gadgets across all of them and yeah, they're, they're all monitored and you can see you'll hopefully get a reply within 24 hours, possibly instantly i'm awake at three o'clock in the morning wonderful, which hasn't happened in the past now tony morelan 17 48 yes, when you when you put out a big blog in the in your, your monitoring your servers, i'm sure you're up at all hours ashiq nazir 17 54 well, the world the world doesn't sleep unfortunately so even i've gone to some conferences i've got introduced to people and they've turned around and say, do you ever sleep? because they realize what time zone i'm in, what time zone they're in and the two things don't match tony morelan 18 13 i think what you're saying is that you want a developer to create an app for you for your smartwatch that says, hey, ash, it's time to go to sleep now couldn't sleep just ashiq nazir 18 21 yeah and it just automatically switches everything off there we go tony morelan 18 25 so excellent ash, it was wonderful, chatting with you and getting to know a little bit more about not only you but also iot gadgets, super excited about what you guys are doing and looking forward to reading some more blogs about upcoming information so again, thank you very much for being on the podcast today ashiq nazir 18 39 hey, tony it's been really great being here and thanks for having us on and thanks for taking the time once you appreciate it outro 18 48 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 develop samsung com today and start your journey with samsung the pow! podcast is brought to you by the samsung developer program and produced by tony morelan
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
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
SDP DevOps
doc개인정보 처리방침 삼성전자는 사용자의 개인정보를 안전하게 보호하는 것을 가장 중요하게 생각합니다 삼성전자는 사용자가 신뢰할 수 있도록, 사용자가 제공한 개인정보를 목적에 따라 적법하게 사용하고, 제공한 개인정보에 대한 사용자의 권리와 선택을 보장하기 위해 최선을 다합니다 이를 위해 제공된 개인정보가 어떤 목적으로 사용되고, 어떻게 보호되는지, 투명하게 공개합니다 또한 사용자가 어떤 권리를 갖는지, 그 권리를 어떻게 행사할 수 있는지 자세히 알려드립니다 1 개인정보 수집 항목 및 방법 1 개인정보 수집 항목 삼성전자는 사용자가 회원을 가입하거나 서비스를 이용할 때, 다음과 같은 개인정보를 수집합니다 서비스 제공에 꼭 필요한 개인정보만 수집하며, 추가로 개인정보가 필요한 경우에는 별도의 선택 동의를 받은 후 수집합니다 구분 자세한 내용 필수항목 - samsung account id, 이름, 이메일, 국가 정보 - 파트너십 또는 서비스 신청 시 이용자가 제공한 이용자가 속한 회사 및 단체에 관한 정보와 이용자가 개발 중인 앱 또는 서비스에 관한 정보 선택항목 - 이용자가 속한 회사, 직업, 직위 및 관심 주제 기타 자동으로 생성/수집되는 개인정보 - ip주소, 쿠키, 서비스 이용기록, 방문기록 ※ 삼성전자는 사용자의 사생활을 침해할 우려가 있는 민감정보 사상 ·신념, 노동조합·정당의 가입·탈퇴, 정치적 견해, 건강, 성생활 등에 관한 정보 등 는 수집하지 않습니다 ※ 삼성전자는 만 14세 미만 사용자의 개인정보는 수집하지 않습니다 단, 서비스 이용을 위해 만 14세 미만 사용자의 개인정보를 수집할 때는 사전에 법정대리인에게 동의를 받고, 개인정보 사용이 끝나면 해당 정보를 바로 삭제하며, 개인정보가 사용되는 동안 개인정보를 안전하게 관리합니다 2 개인정보 수집 방법 삼성전자는 다음과 같이 개인정보를 수집합니다 회원 가입하거나 서비스를 이용할 때 사용자가 직접 제공한 개인정보를 수집 파트너십 신청 및 베타서비스 참가 신청 등 신청 폼을 통한 수집 서비스를 이용할 때 웹사이트에서 자동으로 생성된 정보 ip주소, 서비스 이용 기록 등 를 수집 고객 서비스 상담할 때 전화, 이메일, 상담게시판, 상담 메뉴 등을 통한 수집 사용자가 참여한 이벤트, 프로모션 등을 통한 수집 2 개인정보 수집∙이용 목적 삼성전자는 수집한 개인정보를 다음과 같이 사용합니다 목적 자세한 내용 회원 관리 및 본인 확인 - 사용자 식별, 회원 가입/탈퇴 의사 확인, 나이 확인 및 법정대리인 동의 진행, 사용자 또는 법정대리인의 본인 확인 - 서비스 부정 이용 등 방지, 민원 등 사용자의 요청사항 처리 - 공지사항 등 전달 서비스 제공 - sdk 다운로드, 기술 관련 문의 응대 및 파트너십 요청에 대한 응대 제공 포털컨텐츠 관련 정보 제공 - sdk 업데이트 신규 sdk 정보 제공 및 관련 행사 소식 전달 서비스 개선 및 개발 - 고객만족 조사, 제품/서비스 이용에 대한 분석 및 통계, 시장 트렌드 분석, 기존 서비스 개선, 신규 서비스 기획∙연구∙개발 마케팅∙광고 등에 활용 - 이벤트∙프로모션 등 마케팅 정보 제공 및 경품 배송, 인구통계학적 특성 또는 관심사 기반 마케팅 전송 및 광고 게재 고객문의 응대 - 상담 접수 및 답변 제공, 문의 내역 관리 3 개인정보 제3자 제공 삼성전자는 사용자의 동의 없이 개인정보를 외부에 제공하지 않습니다 단, 다음의 경우는 예외입니다 법률에 특별한 규정이 있거나 법령상 의무를 준수하기 위해 불가피한 경우 서비스 제공에 따른 요금 정산을 위해 필요한 경우 4 개인정보 처리위탁 삼성전자는 더 나은 서비스 제공을 위해 개인정보 처리 업무를 외부 전문 업체에 위탁합니다 위탁받는 업체 명칭 위탁하는 업무 내용 tecace software, ltd ◻ 서비스 제공을 위한 시스템 개발 및 운영, 시스템 모니터링 등 salesforce com ◻ 고객 정보 분석 및 관리 zendesk inc ◻ 고객 문의 사항 응대 mailchimp ◻ 월간 뉴스레터 발송 및 정보 제공 메일 발송 amazon web services inc ◻ 개인정보가 저장된 클라우드 서버 운영 및 관리 google inc ◻ 삼성 개발자 포털 이용자 통계 분석 주식회사 큐로드 ◻ galaxy theme/galaxy watch face 파트너 검수 삼성에스디에스 주 ◻ 시스템 운영 및 관리 주식회사 리시드 ◻ samsung health 서비스 파트너 검수 국외에는 다음과 같이 위탁합니다 업체 명칭 연락처 이전되는 항목 이전 국가, 일시 및 방법 이전 목적 위탁 업무 및 보유∙이용 기간 tecace software, ltd contact@tecace com 1 1 항의 수집 항목 미국 개인정보 보관 기간 동안 개인정보가 보관된 시스템 개발 및 운영 salesforce com https //www salesforce com/kr/form/contact/contactme/ 1 1 항의 수집 항목 미국 개인정보 보관기간 동안 고객 정보 분석 및 관리 zendesk inc https //www zendesk com/contact/ 이름, 이메일, 문의 내용 미국 개인정보 보관 기간 동안 기술 문의 응대 및 지원 문의 응대 mailchimp https //mailchimp com/contact/ 이름, 이메일, 국가 미국 개인정보 보관 기간 동안 뉴스레터 서비스 운영 amazon web services inc https //aws amazon com/compliance/contact/ 1 1 항의 수집 항목 미국 개인정보 보관 기간 동안 개인정보가 보관된 서버를 운영 및 관리 google inc https //analytics google com/ 쿠키, 기기 브라우저 관련 데이터, ip 주소, 사이트/앱 활동 수집 개인 식별 정보 미전송 미국 웹사이트에서 일어나는 사용자 상호작용에 대한 통계 측정용 ip 주소 서비스 보안 제공 및 유지, 사용자 접속 국가 정보를 알려주는 역할 , 사용자 및 이벤트 데이터 보관 38개월 삼성전자는 개인정보 처리를 위탁할 때, 개인정보가 안전하게 보호될 수 있도록 위탁받는 업체와 다음 내용이 포함된 계약을 체결하고, 개인정보를 안전하게 처리하도록 관리합니다 위탁된 업무 처리와 관계없는 개인정보 처리 금지 개인정보 보호를 위한 기술적∙관리적 조치 다른 업체로 재위탁 제한 위탁업무 종료 후 개인정보 반환 또는 삭제 의무 손해배상 등 책임에 관한 사항 삼성전자는 위탁받는 업체 또는 위탁 업무 내용이 변경될 경우, 개인정보 처리방침에 공개 또는 개별 공지하여 알려드립니다 5 개인정보 삭제 삼성전자는 회원 탈퇴 등 개인정보 수집 및 이용이 끝나면 해당 정보를 바로 삭제합니다 단, 다음과 같이 다른 법령에 따라 일정 기간 개인정보를 보관해야 할 경우, 삼성전자는 해당 기간 동안 개인정보를 안전하게 보관한 후 삭제합니다 보유 항목 보유 기간 법적 근거 계약 또는 청약철회 등에 관한 기록 5년 전자상거래 등에서의 소비자보호에 관한 법률 대금결제 및 재화 등의 공급에 관한 기록 5년 전자상거래 등에서의 소비자보호에 관한 법률 소비자의 불만 또는 분쟁처리에 관한 기록 3년 전자상거래 등에서의 소비자보호에 관한 법률 신용정보의 수집/처리 및 이용 등에 관한 기록 3년 신용정보의 이용 및 보호에 관한 법률 표시/광고에 관한 기록 6개월 전자상거래 등에서의 소비자보호에 관한 법률 사용자의 인터넷 등 로그 기록 / 사용자가 접속한 장소를 기록한 자료 3개월 통신비밀보호법 그 외 통신사실 확인 자료 12개월 1 삭제 절차 사용자의 개인정보는 사용이 끝나면 바로 삭제됩니다 위에서 언급한 것과 같이 개인정보를 보존해야 할 경우에는 별도의 데이터베이스 db 또는 다른 장소에 옮겨서 법정 기간 동안 보관하며, 기간이 지나면 바로 삭제합니다 2 삭제 방법 삼성전자는 전자 파일 형태로 저장된 개인정보는 기록을 열어볼 수 없는 방법으로 삭제하며, 종이에 기재된 형태의 개인정보는 분쇄나 소각을 통해 삭제합니다 6 사용자 및 법정대리인의 권리 및 행사 방법 삼성전자는 개인정보에 대한 사용자의 권리를 존중합니다 사용자 만14세 미만인 경우에는 법정대리인 는 언제든지 개인정보 열람, 정정·삭제, 처리정지, 동의 철회를 삼성전자에 다음의 방법으로 요청할 수 있습니다 단, 개인정보보호법 등 관련 법령에 따라 일부 권리 행사가 제한될 수 있습니다 웹페이지 dashboard 메뉴에서 account info 설정 메뉴 이용 삼성 개인정보 포털 https //privacy samsung com 이용 대표전화 1588-4730 이용 고객지원 담당부서 또는 개인정보 보호책임자에게 연락 다음 목차 참조 7 고객지원 담당부서 및 개인정보 보호책임자 삼성전자는 사용자의 개인정보를 보호하고 개인정보와 관련된 불편사항을 개선하기 위해 고객지원 담당부서 및 개인정보 보호책임자를 지정하고 있습니다 사용자는 담당자에게 본인의 개인정보에 대한 권리 행사를 요청할 수 있으며, 삼성전자 서비스를 이용하며 발생한 개인정보 보호와 관련된 모든 민원을 신고할 수 있습니다 삼성전자는 사용자의 신고사항에 대해 충분한 내용으로 신속하게 답변을 드릴 것입니다 1 고객지원 담당부서 고객지원 담당부서 삼성전자 mx 사업부 se팀 s/w인프라개발그룹그룹 문의처 support@samsungdevelopers com 2 개인정보 보호책임자 및 개인정보 보호 담당부서 개인정보 보호책임자 개인정보보호사무국장 개인정보 보호 담당부서 개인정보보호사무국 전화 1588-4730 문의처 privacy sec@samsung com 3 기타 기관 기타 개인정보 침해 신고나 상담이 필요한 경우에는 아래 기관에 문의해 주세요 개인정보침해 신고센터 privacy kisa or kr / 국번 없이 118 대검찰청 사이버수사과 www spo go kr / 국번 없이 1301 경찰청 사이버수사국 ecrm cyber go kr / 국번 없이 182 8 개인정보 자동 수집 장치 설치, 운영, 거부에 관한 사항 삼성전자는 사용자의 정보를 수시로 저장하고 찾아내는 쿠키 cookie 를 사용합니다 쿠키는 회사 웹사이트 운영에 이용되는 서버가 사용자의 브라우저에 보내는 아주 작은 텍스트 파일로, 사용자의 기기내 저장공간에 저장됩니다 1 쿠키 사용 목적 삼성전자는 다음과 같은 목적으로 쿠키를 사용합니다 자동 로그인 기능 구현 회원/비회원의 접속 빈도 또는 방문 시간 등 분석 사용자의 취향과 관심분야 파악 및 사용 기록 확인, 각종 이벤트 참여 및 방문 횟수 파악 등을 통한 타겟 마케팅과 개인 맞춤 서비스 제공 등 2 쿠키 설정 방법 사용자는 쿠키를 설치할 것인지 선택할 수 있습니다 사용 중인 웹브라우저의 설정 메뉴 예 인터넷 익스플로러 11 0 도구 > 인터넷옵션 > 개인정보 에서 쿠키 허용 수준을 변경하거나, 모든 쿠키의 저장을 거부할 수 있습니다 단, 사용자가 쿠키 설치를 거부할 경우 일부 서비스가 제공되지 않을 수 있습니다 9 안전한 개인정보 보호를 위한 조치 삼성전자는 사용자의 개인정보를 안전하게 보호하기 위하여 다양한 보호조치와 노력을 하고 있습니다 관리적 조치 내부 관리계획 수립 및 시행, 개인정보 교육 실시 등 기술적 조치 개인정보에 대한 접근통제 장치 운영 및 접근 권한 제한, 개인정보 처리시스템 접속기록 보관 및 위조/변조를 방지하기 위한 보안기능 사용, 개인정보의 암호화, 백신 프로그램 및 보안 프로그램 설치 등 물리적 조치 전산실, 자료보관실 등의 접근통제 10 개인정보 처리방침 업데이트 개인정보 처리방침은 처리하는 개인정보 내용 등 변경사항이 있으면, 이를 반영하여 언제든지 업데이트될 수 있습니다 개인정보 처리방침이 업데이트될 경우, 시행되기 최소 7일 전에 공지사항 등을 통해 미리 알려드립니다 개인정보 처리방침 버전 번호 v 1 2 개인정보 처리방침 시행 일자 2023년 2월 28일
SDP DevOps
doc삼성전자 samsung developer portal 개인정보 처리방침 삼성전자는 사용자의 개인정보를 안전하게 보호하는 것을 가장 중요하게 생각합니다 삼성전자는 사용자가 신뢰할 수 있도록, 사용자가 제공한 개인정보를 목적에 따라 적법하게 사용하고, 제공한 개인정보에 대한 사용자의 권리와 선택을 보장하기 위해 최선을 다합니다 이를 위해 제공된 개인정보가 어떤 목적으로 사용되고, 어떻게 보호되는지, 투명하게 공개합니다 또한 사용자가 어떤 권리를 갖는지, 그 권리를 어떻게 행사할 수 있는지 자세히 알려드립니다 주요 개인정보 처리 표시 라벨링 개인정보 수집 samsung account id, 이름, 이메일, 국가 정보, 개발 중인 앱 또는 서비스 관련 정보, 서비스 이용기록 등 개인정보의 처리 목적 회원 관리 및 본인 확인, 서비스 제공, 서비스 개선 및 개발 등 개인정보의 보유기간 회원 탈퇴시까지 개인정보 처리위탁 tecace software, ltd, salesforce com, zendesk inc, amazon web services inc , google inc, 주식회사 큐로드, 삼성에스디에스㈜, samsung r&d center vietnam 및 주식회사 리시드 개인정보 제3자 제공 예외적인 경우를 제외하고, 외부에 제공하지 않음 고충처리부서 · 부서명 삼성전자 mx 사업부 se팀 s/w인프라개발그룹 · 이메일 주소 support@samsungdevelopers com ※ 세부사항은 아래의 개인정보 처리방침 본문을 확인하시기 바랍니다 1 개인정보 수집 항목 및 방법 1 개인정보 수집 항목 삼성전자는 사용자가 회원을 가입하거나 서비스를 이용할 때, 다음과 같은 개인정보를 수집합니다 서비스 제공에 꼭 필요한 개인정보만 수집하며, 추가로 개인정보가 필요한 경우에는 별도의 선택 동의를 받은 후 수집합니다 구분 자세한 내용 필수항목 - samsung account id, 이름, 이메일, 국가 정보 - 파트너십 또는 서비스 신청 시 이용자가 제공한 이용자가 속한 회사 및 단체에 관한 정보와 이용자가 개발 중인 앱 또는 서비스에 관한 정보 선택항목 ① 관심 컨텐츠 선별 제공 - 이용자가 속한 회사, 직업, 직위 및 관심 주제 ② 마케팅∙광고 활용 목적 - 이메일 정보, 국가 정보, 서비스 이용기록 기타 자동으로 생성/수집되는 개인정보 - ip주소, 쿠키, 서비스 이용기록, 방문기록 ※ 삼성전자는 사용자의 사생활을 침해할 우려가 있는 민감정보 사상·신념, 노동조합·정당의 가입·탈퇴, 정치적 견해, 건강, 성생활 등에 관한 정보 등 는 수집하지 않습니다 ※ 삼성전자는 만 14세 미만 사용자의 개인정보는 수집하지 않습니다 단, 만 14세 미만 아동의 개인정보를 처리하기 위하여 개인정보보호법에 따른 동의를 받아야 할 때는 그 법정대리인에게 동의를 받고, 개인정보 사용이 끝나면 해당 정보를 바로 삭제하며, 개인정보가 사용되는 동안 개인정보를 안전하게 관리합니다 2 개인정보 수집 방법 삼성전자는 다음과 같이 개인정보를 수집합니다 회원 가입하거나 서비스를 이용할 때 사용자가 직접 제공한 개인정보를 수집 서비스를 이용할 때 웹사이트 등에서 자동으로 생성된 정보 ip주소, 서비스 이용 기록 등 를 수집 고객 서비스 상담할 때 전화, 이메일, 상담게시판, 상담 메뉴 등을 통한 수집 사용자가 참여한 이벤트, 프로모션 등을 통한 수집 2 개인정보 수집∙이용 목적 삼성전자는 수집한 개인정보를 다음과 같이 사용합니다 목적자세한 내용 회원 관리 및 본인 확인 - 사용자 식별, 회원 가입/탈퇴 의사 확인 - 서비스 부정 이용 등 방지, 민원 등 사용자의 요청사항 처리 - 공지사항 등 전달 서비스 제공 - sdk 다운로드, 기술 관련 문의 응대 및 파트너십 요청에 대한 응대 제공 서비스 개선 및 개발 - 고객만족 조사, 제품/서비스 이용에 대한 분석 및 통계, 시장 트렌드 분석, 기존 서비스 개선, 신규 서비스 기획∙연구∙개발 마케팅∙광고 등에 활용 - 이벤트∙프로모션 등 마케팅 정보 제공 및 경품 배송, 인구통계학적 특성 또는 관심사 기반 마케팅 전송 및 광고 게재 - 개발자 포털 뉴스레터 발송 서비스 및 이벤트 홍보 포함 고객문의 응대 - 상담 접수 및 답변 제공, 문의 내역 관리 3 개인정보 제3자 제공 삼성전자는 사용자의 동의 없이 개인정보를 외부에 제공하지 않습니다 단, 다음의 경우는 예외입니다 법률에 특별한 규정이 있거나 법령상 의무를 준수하기 위해 불가피한 경우 서비스 제공에 따른 요금 정산을 위해 필요한 경우 재난, 감염병, 급박한 생명·신체 위험을 초래하는 사건·사고, 급박한 재산 손실 등의 긴급사항이 발행하는 경우 4 개인정보의 추가적인 이용∙제공 판단기준 삼성전자는 개인정보 보호법 제15조 제3항 및 제17조 제4항에 따라 개인정보 보호법 시행령 제14조의2에 따른 사항에 부합하는 경우에 한하여 사용자의 동의 없이 개인정보를 추가적으로 이용∙제공할 수 있습니다 삼성전자는 사용자의 동의 없이 추가적인 이용∙제공을 하기 위해서 다음과 같은 사항을 고려합니다 개인정보를 추가적으로 이용∙제공하려는 목적이 당초 수집 목적과 관련성이 있는지 여부 개인정보를 수집한 정황 또는 처리 관행에 비추어 볼 때 추가적인 이용∙제공에 대한 예측 가능성이 있는지 여부 개인정보의 추가적인 이용∙제공이 사용자의 이익을 부당하게 침해하는지 여부 가명처리 또는 암호화 등 안전성 확보에 필요한 조치를 하였는지 여부 5 개인정보 처리위탁 삼성전자는 더 나은 서비스 제공을 위해 개인정보 처리 업무를 외부 전문 업체에 위탁합니다 위탁받는 업체 명칭 위탁받는 업무 내용 tecace software, ltd ◻ 서비스 제공을 위한 시스템 개발 및 운영, 시스템 모니터링 salesforce com ◻ 고객 정보 분석 및 관리 zendesk inc ◻ 고객 문의 사항 응대 amazon web services inc ◻ 개인정보가 저장된 클라우드 서버 제공 google inc ◻ 웹사이트 사용자 상호작용에 대한 통계 측정 주식회사 큐로드 ◻ galaxy theme/galaxy watch face 파트너 검수 삼성에스디에스 주 ◻ 시스템 운영 및 관리 주식회사 리시드 ◻ samsung health 서비스 파트너 검수 samsung r&d center vietnam ◻︎ 서비스 제공을 위한 시스템 개발 및 운영, 시스템 모니터링 등 국외에는 다음과 같이 위탁합니다 서비스 이용 도중 개인정보의 국외이전을 거부하시려면 account info | samsung developer 페이지에서 회원 탈퇴 해주시기 바랍니다 다만 동의를 거부하실 경우 서비스를 이용하실 수 없습니다 업체 명칭 연락처 이전되는 항목 이전 국가,일시 및 방법 이전 목적 위탁 업무 및 보유∙이용 기간 tecace software, ltd contact@tecace com 1 1 항의 수집 항목 미국 개인정보 보관기간 동안, 서비스 제공을 위한 시스템 개발 및 운영, 시스템 모니터링 salesforce com https //www salesforce com/kr/form/contact/contactme/ 1 1 항의 수집 항목 미국 개인정보 보관기간 동안, 고객 정보 분석 및 관리 zendesk inc https //www zendesk com/contact/ 이름, 이메일, 문의 내용 미국 개인정보 보관기간 동안, 고객 문의 사항 응대 amazon web services inc https //aws amazon com/compliance/contact/ 1 1 항의 수집 항목 미국 개인정보 보관기간 동안, 개인정보가 저장된 클라우드 서버 제공 google inc https //analytics google com/ 쿠키, 기기 브라우저 관련 데이터, ip 주소, 사이트/앱 활동 수집 개인 식별 정보 미전송 미국 38개월, 웹사이트 사용자 상호작용에 대한 통계 측정 samsung r&d center vietnam rtl support@samsung com 1 1 항의 수집 항목 베트남 개인정보 보관기간 동안, 서비스 제공을 위한 시스템 개발 및 운영, 시스템 모니터링 삼성전자는 개인정보 처리를 위탁할 때, 개인정보가 안전하게 보호될 수 있도록 위탁받는 업체와 다음 내용이 포함된 계약을 체결하고, 개인정보를 안전하게 처리하도록 관리합니다 위탁된 업무 처리와 관계없는 개인정보 처리 금지 개인정보 보호를 위한 기술적∙관리적 조치 다른 업체로 재위탁 제한 위탁업무 종료 후 개인정보 반환 또는 삭제 의무 손해배상 등 책임에 관한 사항 삼성전자는 위탁받는 업체 또는 위탁 업무 내용이 변경될 경우, 개인정보 처리방침에 공개 또는 개별 공지하여 알려드립니다 6 개인정보 삭제 삼성전자는 회원 탈퇴 시 해당 정보를 바로 삭제합니다 단, 다음과 같이 다른 법령에 따라 일정 기간 개인정보를 보관해야 할 경우, 삼성전자는 해당 기간 동안 개인정보를 안전하게 보관한 후 삭제합니다 보유 항목 보유 기간 법적 근거 계약 또는 청약철회 등에 관한 기록 5년 전자상거래 등에서의 소비자보호에 관한 법률 대금결제 및 재화 등의 공급에 관한 기록 5년 전자상거래 등에서의 소비자보호에 관한 법률 소비자의 불만 또는 분쟁처리에 관한 기록 3년 전자상거래 등에서의 소비자보호에 관한 법률 신용정보의 수집/처리 및 이용 등에 관한 기록 3년 신용정보의 이용 및 보호에 관한 법률 표시/광고에 관한 기록 6개월 전자상거래 등에서의 소비자보호에 관한 법률 사용자의 인터넷 등 로그 기록 / 사용자가 접속한 장소를 기록한 자료 3개월 통신비밀보호법 그 외 통신사실 확인 자료 12개월 1 삭제 절차 사용자의 개인정보는 사용이 끝나면 바로 삭제됩니다 위에서 언급한 것과 같이 개인정보를 보존해야 할 경우에는 별도의 데이터베이스 db 또는 다른 장소에 옮겨서 법정 기간 동안 보관하며, 기간이 지나면 바로 삭제합니다 2 삭제 방법 삼성전자는 전자 파일 형태로 저장된 개인정보는 기록을 열어볼 수 없는 방법으로 삭제하며, 종이에 기재된 형태의 개인정보는 분쇄나 소각을 통해 삭제합니다 7 사용자 및 법정대리인의 권리 및 행사 방법 삼성전자는 개인정보에 대한 사용자의 권리를 존중합니다 사용자 만14세 미만인 경우에는 법정대리인 는 언제든지 개인정보 열람, 정정·삭제, 처리정지, 동의 철회를 삼성전자에 다음의 방법으로 요청할 수 있습니다 단, 개인정보 보호법 등 관련 법령에 따라 일부 권리 행사가 제한될 수 있습니다 삼성 개인정보 포털 https //privacy samsung com 이용 대표전화 1588-4730 이용 고객지원 담당부서 또는 개인정보 보호책임자에게 연락 다음 목차 참조 8 고객지원 담당부서 및 개인정보 보호책임자 삼성전자는 사용자의 개인정보를 보호하고 개인정보와 관련된 불편사항을 개선하기 위해 고객지원 담당부서 및 개인정보 보호책임자를 지정하고 있습니다 사용자는 담당자에게 본인의 개인정보에 대한 권리 행사를 요청할 수 있으며, 삼성전자 서비스를 이용하며 발생한 개인정보 보호와 관련된 모든 민원을 신고할 수 있습니다 삼성전자는 사용자의 신고사항에 대해 충분한 내용으로 신속하게 답변을 드릴 것입니다 1 고객지원 담당부서 고객지원 담당부서 삼성전자 mx 사업부 se팀 s/w인프라개발그룹 문의처 support@samsungdevelopers com 2 개인정보 보호책임자 및 개인정보 보호 담당부서 개인정보 보호책임자 개인정보보호사무국장 개인정보 보호 담당부서 개인정보보호사무국 전화 1588-4730 문의처 privacy sec@samsung com 3 기타 기관 기타 개인정보 침해 신고나 상담이 필요한 경우에는 아래 기관에 문의해 주세요 개인정보분쟁조정위원회 www kopico go kr / 국번없이 1833-6972 개인정보침해 신고센터 privacy kisa or kr / 국번 없이 118 대검찰청 사이버수사과 www spo go kr / 국번 없이 1301 경찰청 사이버수사국 ecrm cyber go kr / 국번 없이 182 9 개인정보 자동 수집 장치 설치, 운영, 거부에 관한 사항 삼성전자는 사용자의 정보를 수시로 저장하고 찾아내는 쿠키 cookie 를 사용합니다 쿠키는 회사 웹사이트 운영에 이용되는 서버가 사용자의 브라우저에 보내는 아주 작은 텍스트 파일로, 사용자의 기기내 저장공간에 저장됩니다 1 쿠키 사용 목적 삼성전자는 다음과 같은 목적으로 쿠키를 사용합니다 자동 로그인 기능 구현 회원/비회원의 접속 빈도 또는 방문 시간 등 분석 사용자의 취향과 관심분야 파악 및 사용 기록 확인 각종 이벤트 참여 및 방문 횟수 파악 등을 통한 타겟 마케팅과 개인 맞춤 서비스 제공 등 2 쿠키 설정 방법 사용자는 쿠키를 허용할 것인지 차단할 것인지 선택할 수 있습니다 사용 중인 웹브라우저의 설정 메뉴에서 쿠키 허용 수준을 변경하거나, 모든 쿠키의 저장을 거부할 수 있습니다 웹브라우저를 다음과 같이 설정할 수 있습니다 - chrome 웹브라우저 우측 상단의 설정메뉴 > 개인정보 및 보안 > 쿠키 및 기타 사이트 데이터 - microsoft edge 웹브라우저 우측 상단의 설정 메뉴 > 쿠키 및 사이트 권한 > 쿠키 및 사이트 데이터 관리 및 삭제 - whale 웹브라우저 우측 상단의 설정 메뉴 > 개인정보 보호 > 쿠키 및 기타 사이트 데이터 단, 사용자가 쿠키 설치를 거부할 경우 일부 서비스가 제공되지 않을 수 있습니다 10 행태정보 수집·이용 및 거부 등에 관한 사항 삼성전자는 행태정보를 다음과 같이 처리합니다 구분 자세한 내용 수집하는 행태정보의 항목 - 이용자의 웹 서비스 설치 이력 - 이용자의 웹 서비스 방문 이력 - 이용자의 웹 서비스 검색/결제/구매 등 사용 이력 - 기타 규제기관 가이드라인에 따라 행태정보로 인정되는 온라인상의 이용자 활동정보 행태정보의 수집 방법 - 이용자의 정보를 저장하고 수시로 찾아내는 쿠키 cookie 를 설치·운용 - 이용자가 웹 사이트 방문 시 생성 정보 수집 툴 등을 통해 자동 수집 전송 - 이용자가 웹사이느 로그인 시, sdk 다운로드 기록 자동 수집 - - 기타 관련 법령 및 가이드에 따라 허용된 방법 행태정보의 수집 목적 - 이용자들이 이용한 회사의 각 서비스와 이용형태 등을 분석하여 이용자에게 최척화된 개인 맞춤형 상품 추천 서비스 광고 포함 제공 - 개인의 관심 분야에 따라 차별화된 정보 및 개인 맞춤서비스 뉴스레터 등 제공 - 기타 이용자의 행태정보를 분석하여 신상품 개발, 서비스 개편 등의 척도로 활용 가능 행태정보의 보유ㆍ이용 기간 - 회원 탈퇴시까지 보유 이용자의 통제권 행사 방법 - 이용자는 삼성전자가 제공하는 개인 맞춤형 상품 추천 서비스를 수신 거부하거나 기타 개인 맞춤 서비스를 차단할 수 있는 선택권을 다음과 같은 방법으로 행사할 수 있습니다 1 웹브라우저 · chrome ① 크롬 설정, ② 고급 → 개인정보 → 콘텐츠 설정, ③ 쿠키 -> 타사 쿠키 및 사이트 데이터 차단 2 스마트폰 아이폰, 안드로이드폰 · 아이폰 ① 설정 → ② 개인정보보호 선택 → ③ 광고 선택 → ④ 광고 추적 제한 해제 os버전에 따라 다소 상이할 수 있음 · 안드로이드폰 ① 설정 → ② 계정 → 구글 계정 선택 → ③ 광고 선택 → ④ 광고 맞춤설정 선택 해제 os버전에 따라 다소 상이할 수 있음 행태정보 관련 문의 및 피해 구제 방법 - 담당부서 삼성전자 mx 사업부 se팀 s/w인프라개발그룹 - 이메일 주소 support@samsungdevelopers com 11 안전한 개인정보 보호를 위한 조치 삼성전자는 사용자의 개인정보를 안전하게 보호하기 위하여 다양한 보호조치와 노력을 하고 있습니다 관리적 조치 내부 관리계획 수립 및 시행, 개인정보 교육 실시 등 기술적 조치 개인정보에 대한 접근통제 장치 운영 및 접근 권한 제한, 개인정보 처리시스템 접속기록 보관 및 위조/변조를 방지하기 위한 보안기능 사용, 개인정보의 암호화, 백신 프로그램 및 보안 프로그램 설치 등 물리적 조치 전산실, 자료보관실 등의 접근통제 12 개인정보 처리방침 업데이트 개인정보 처리방침은 처리하는 개인정보 내용 등 변경사항이 있으면, 이를 반영하여 언제든지 업데이트될 수 있습니다 이전의 개인정보 처리방침은 아래에서 확인하실 수 있습니다 - 2023 2 28 ~ 2023 12 14 적용 - 2022 2 9 ~ 2023 2 27 적용 - 2021 12 1 ~ 2022 2 8 적용 - 2020 10 30 ~ 2021 11 30 적용 개인정보 처리방침 버전 번호 v 1 3 개인정보 처리방침 시행 일자 2023년 12월 15일
Preferences Submitted
You have successfully updated your cookie preferences.