Filter
-
Content Type
-
Category
Mobile/Wearable
Visual Display
Digital Appliance
Platform
Recommendations
Filter
Develop Samsung Pay
docconfigure webview enablements to invoke samsung pay application in webview, you should override the shouldoverrideurlloading method javascript and dom storage are disabled in a webview by default you can enable the both through the websettings attached to your webview websettings allows any website to use javascript and dom storage for more information, visit websettings sample code kotlin import android webkit webview import android webkit webviewclient import android content intent import android content activitynotfoundexception companion object { private const val samsung_pay_url_prefix string = "samsungpay" } private lateinit var webview webview webview settings run { javascriptenabled = true domstorageenabled = true } webview webviewclient = object webviewclient { override fun shouldoverrideurlloading view webview, request webresourcerequest boolean { // get url from webresourcerequest val url = request url tostring // add below if statement to check if url is samsung pay deep link if url startswith samsung_pay_url_prefix { try { val intent = intent parseuri url, intent uri_intent_scheme startactivity intent } catch e activitynotfoundexception { // exception would be occured if the samsung wallet app is not installed // go to install samsung wallet app from market val installintent = intent parseuri "samsungapps //productdetail/com samsung android spay", intent uri_intent_scheme installintent addflags intent flag_activity_new_task startactivity installintent } // return true will cause that the url will not be loaded in webview return true } // the remaining part of the shouldoverrideurlloading method code // return false when you want to load url automatically by webview return false } }
tutorials game, marketplace, mobile
blogoscar clark, evangelist at unity technologies, recently hosted a webinar on the seven rules of monetization. if you happened to miss it, you’re in luck because we’ve posted the replay below. in what was a jam-packed hour, oscar spoke about the importance of learning through experimentation, failure and data, offering expertise and examples designed to help developers avoid the mistakes he’s seen throughout his almost 20 years in monetization and social freemium game design. while you’ll get much more detail and nuance through watching the replay, here are a few highlights pulled from the webinar as they relate to the rules of mobile game monetization: rule 1: utility - what do your players value? utility is defined as how well your game functions as just that: a game (and an enjoyable one at that). rather than building a game with only monetization in mind, by authentically focusing on utility, developers can generate better revenue opportunities in the long run. to this end, use ads strategically, thinking of the places and stages in your game where they will add the most value without being a distraction. rule 2: anticipation - why should they 'expect future value'? how do you help players get over their buying anxiety? buying is a risky proposition for the end user. generally, they are uncertain what the outcome will be and are worried they are getting led on. this is perhaps the biggest hurdle that you as a developer will have to clear. therefore, you have to show the player what the potential reward is. you have to create an expectation of delight. you need to demonstrate value, spark interest and show the player that it pays for them to opt in. rule 3: scarcity - what are the 'opportunity costs'? build in ‘scarcity’ – it’s integral to your game design. it is a powerful motivator that will often trigger players to pay. ‘limited time offers’ do work. without scarcity, there’s no dilemma created for the player. with no dilemma, there’s no decision to be made, and with no decision, there’s no challenge. also be careful to not break the underlining game economy by flooding the market with ‘cheap gold.’ you need to carefully consider how your purchasable items impact the game experience, and make smart choices when you bundle items to ensure there’s always scarcity. rule 4: timing - understanding the player lifecycle if you’re going to monetize your game, you need to understand the player lifecycle. while the instinct is to convert players to paying customers right away, instead, this is the stage where you as a developer need to figure out how to keep people playing as long as possible. this is often difficult since mobile games only have about a 40% retention rate. players are just figuring out controls and gameplay, and always don’t have the best ux initially. therefore, instead of conversion, all your efforts must go into showing players what’s possible in your game, and why they should keep playing. rule 5: repetition - why should players return to play? you need to create repeat customers, because people who play your game more are the people who will spend more money. however, developers need to watch out for player fatigue, so ensure that you’re able to give players an opportunity to take a break every once in a while. you need to design your sessions a bit shorter, so your players can sneak in a few games while on public transportation or waiting in line, as no mobile gamer wants a session that lasts 15 minutes. rule 6: evidence - why analytics is essential data is so important. the best game designers already excel at solving problems, so if you as a dev can use testing and analytics to identify problem areas in your games, you can then use those insights to weave creative solutions. when analyzing data, don’t just look at conversions, but at repeat purchases. if your in-app purchases don’t create repeat buyers, then something is amiss. your monetization model is flawed if gamers only pay to play once. rule 7: scale - the ultimate rule of free-to-play remember, at the end of the day, scale trumps everything. ultimately, the more people playing your game means there are more people who can potentially contribute to your overall profitability. but in order to scale and grow, you have to again focus on utility and creating an engaging game that people want to play. the ultimate rule of thumb: do not sacrifice the quality of gameplay for the potential of profitability. if you’re looking for more tips and advice, be sure to watch the webinar replay here.
Samsung Developer Program
Develop Samsung Pay
apioverview package class tree index help package com samsung android sdk samsungpay v2 class watchmanager java lang object samsungpaybase com samsung android sdk samsungpay v2 watchmanager all implemented interfaces apptoappconstants public final class watchmanager extends samsungpaybase implements apptoappconstants this class provides apis for watch management partner apps must check the samsung pay watch status on the device before performing any card management also, this class provides apis getting cards information, adding new card to samsung pay on watch, and so on since api level 2 5 field summary fields modifier and type field description static final string device_serial_num key to represent device serial number to generate the paymentappinstanceid static final int error_invalid_parameter this error indicates that the given parameter is invalid this is returned as spaysdk extra_error_reason for spaysdk error_registration_fail error static final int error_spay_pin_lock_setup_canceled this error indicates that user canceled the pin lock setup partner app should ask user to setup pin for samsung pay gear static final int error_spay_watch_connection this error indicates that samsung pay watch plug-in can not connect with samsung pay watch partner app should ask user to check bluetooth connection or pairing static final int error_spay_watch_pay_progress this error indicates that samsung pay watch is in a process of payment static final int error_spay_watch_pin_lock_setup_canceled this error indicates that user canceled the pin lock setup partner app should ask user to setup pin for samsung pay watch static final int spay_watch_taking_log_for_report this error indicates that samsung pay watch is taking log for error report static final int spay_watch_update_is_ongoing this error indicates that samsung pay watch being updated fields inherited from interface com samsung android sdk samsungpay v2 apptoappconstants error_auth_code_expired, error_auth_code_invalid, error_auth_code_max_try_reached, error_auth_code_type_invalid, error_authentication_closed, error_authentication_failed, error_authentication_not_ready, error_authentication_timed_out, error_card_already_registered, error_card_idv_not_supported, error_card_not_supported, error_framework_internal, error_invalid_card, error_invalid_cardinput, error_max_card_num_reached, error_max_pan_provision_num_reached, error_server_reject, error_tsm_fail, error_verify_card, error_wallet_id_mismatch, extra_app2app_intent, extra_app2app_payload, extra_card_balance, extra_card_status_reason, extra_issuer_app_card_linked constructor summary constructors constructor description watchmanager android content context context, partnerinfo partnerinfo api to get the watchmanager instance the caller should set valid serviceid method summary all methodsinstance methodsconcrete methods modifier and type method description void activatesamsungpay api to bring the samsung pay on watch app to a state in which cards can be added samsung pay on watch might be samsung account is not signed in state partner app checks the samsung pay on watch status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_setup_not_completed, partner app can call this api to launch samsung pay on watch and user can sign in to the app void addcard addcardinfo addcardinfo, addcardlistener listener api to add a card from partner app example issuer/bank app to samsung pay on watch partner app uses this api to add card to samsung pay on watch by providing the required card details void getallcards android os bundle cardfilter, getcardlistener listener api to get all the cards from samsung pay on watch for the given filter void getsamsungpaystatus statuslistener listener api to get the samsung pay on watch status on the device partner issuers applications must call this api to check the current state of samsung pay on watch before doing any operation void getwalletinfo list<string> keys, statuslistener listener api to get the requested wallet information from samsung pay on watch partner app can use this information to uniquely identify the user and samsung pay on watch app on a particular device void gotoupdatepage api to go to samsung pay on watch update page partner app checks the samsung pay on watch status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_app_need_to_update, partner app can call this api to go to update samsung pay on watch app methods inherited from class java lang object equals, getclass, hashcode, notify, notifyall, tostring, wait, wait, wait field details device_serial_num public static final string device_serial_num key to represent device serial number to generate the paymentappinstanceid since api level 2 5 see also constant field values error_spay_pin_lock_setup_canceled public static final int error_spay_pin_lock_setup_canceled this error indicates that user canceled the pin lock setup partner app should ask user to setup pin for samsung pay gear since api level 2 5 see also constant field values error_invalid_parameter public static final int error_invalid_parameter this error indicates that the given parameter is invalid this is returned as spaysdk extra_error_reason for spaysdk error_registration_fail error since api level 2 5 see also constant field values error_spay_watch_pin_lock_setup_canceled public static final int error_spay_watch_pin_lock_setup_canceled this error indicates that user canceled the pin lock setup partner app should ask user to setup pin for samsung pay watch since api level 2 5 see also constant field values spay_watch_update_is_ongoing public static final int spay_watch_update_is_ongoing this error indicates that samsung pay watch being updated since api level 2 5 see also constant field values spay_watch_taking_log_for_report public static final int spay_watch_taking_log_for_report this error indicates that samsung pay watch is taking log for error report since api level 2 5 see also constant field values error_spay_watch_pay_progress public static final int error_spay_watch_pay_progress this error indicates that samsung pay watch is in a process of payment since api level 2 5 see also constant field values error_spay_watch_connection public static final int error_spay_watch_connection this error indicates that samsung pay watch plug-in can not connect with samsung pay watch partner app should ask user to check bluetooth connection or pairing since api level 2 5 see also constant field values constructor details watchmanager public watchmanager android content context context, partnerinfo partnerinfo api to get the watchmanager instance the caller should set valid serviceid partnerinfo is passed to samsung pay on watch for caller verification context ct = activity; // or context ct = service; string issuername = "mybank"; // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring watchmanager extra_issuer_name, issuername ; bundle putstring watchmanager partner_service_type, watchmanager servicetype app2app tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; watchmanager watchmanager = new watchmanager ct, pinfo ; parameters context - activity context or service context partnerinfo - partner information throws nullpointerexception - thrown if parameters are null since api level 2 5 method details getsamsungpaystatus public void getsamsungpaystatus @nonnull statuslistener listener api to get the samsung pay on watch status on the device partner issuers applications must call this api to check the current state of samsung pay on watch before doing any operation // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring watchmanager partner_service_type, watchmanager servicetype app2app tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; watchmanager watchmanager = new watchmanager context, pinfo ; watchmanager getsamsungpaystatus new statuslistener { @override public void onsuccess int status, bundle data { // success case if status == spay_ready { log d tag, "samsung pay on watch is ready on the device" ; // perform your operation } else if status == spay_not_ready { // samsung pay on watch is supported but not fully ready // if extra_error_reason is error_spay_app_need_to_update, // call gotoupdatepage // if extra_error_reason is error_spay_setup_not_completed, // call activatesamsungpay } else { // samsung pay on watch is not supported on this device log d tag, "device does not support samsung pay on watch" ; } } @override public void onfail int errorcode, bundle errordata { log e tag, "onfail callback is called, errorcode " + errorcode ; // to get more reason of the failure, // check some extra error codes in the errordata bundle such as watchmanager extra_error_reason if provided } } ; parameters listener - callback through which the result is provided on success, samsung pay on watch status code is provided via statuslistener onsuccess int status, bundle data if samsung pay on watch is ready to be used, #spay_ready will be returned otherwise, #spay_not_ready or #spay_not_supported can be returned with #extra_error_reason from bundle also, partner can get extra information from bundle data bundle keys if provided bundle values spaysdk extra_country_code device country code iso 3166-1 alpha-2 on any failure, the failure code is provided via statuslistener onfail int errorcode, bundle errordata note please refer spaysdk common_status_table in detail throws nullpointerexception - thrown if the callback passed is null since api level 2 5 gotoupdatepage public void gotoupdatepage api to go to samsung pay on watch update page partner app checks the samsung pay on watch status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_app_need_to_update, partner app can call this api to go to update samsung pay on watch app // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring watchmanager partner_service_type, watchmanager servicetype app2app tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; watchmanager watchmanager = new watchmanager context, pinfo ; watchmanager gotoupdatepage ; since api level 2 5 activatesamsungpay public void activatesamsungpay api to bring the samsung pay on watch app to a state in which cards can be added samsung pay on watch might be samsung account is not signed in state partner app checks the samsung pay on watch status with getsamsungpaystatus statuslistener api if the status is #spay_not_ready and #extra_error_reason is #error_spay_setup_not_completed, partner app can call this api to launch samsung pay on watch and user can sign in to the app // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring watchmanager partner_service_type, watchmanager servicetype app2app tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; watchmanager watchmanager = new watchmanager context, pinfo ; watchmanager activatesamsungpay ; since api level 2 5 getwalletinfo public void getwalletinfo list<string> keys, @nonnull statuslistener listener api to get the requested wallet information from samsung pay on watch partner app can use this information to uniquely identify the user and samsung pay on watch app on a particular device // set the serviceid which is assigned by the samsung pay developer during on boarding string serviceid = "sampleserviceid"; bundle bundle = new bundle ; bundle putstring watchmanager extra_issuer_name, "issuer name" ; bundle putstring watchmanager partner_service_type, watchmanager servicetype app2app tostring ; partnerinfo pinfo = new partnerinfo serviceid, bundle ; watchmanager watchmanager = new watchmanager context, pinfo ; // bundle keys added to get wallet information from samsung pay on watch // this information can be delivered to the partner server for eligibility check arraylist<string> keys = new arraylist<> ; keys add watchmanager wallet_user_id ; keys add watchmanager device_id ; watchmanager getwalletinfo keys, new statuslistener { @override public void onsuccess int status, bundle walletdata { // log d tag, "dowalletinfo onsuccess callback is called" ; // for visa, deviceid can be set to "clientdeviceid" as defined by visa string deviceid = walletdata get watchmanager device_id ; // for visa, walletuserid can be set to "clientwalletaccountid" as defined by visa string walletuserid = walletdata get watchmanager wallet_user_id ; } @override public void onfail int errorcode, bundle errordata { log e tag, "onfail callback is called, errorcode " + errorcode ; // to get more reason of the failure, // check some extra error codes in the errordata bundle such as watchmanager extra_error_reason if provided } } parameters keys - key list to get wallet information if the list is empty, all possible key values are returned the possible keys are #wallet_dm_id #device_id #wallet_user_id device_serial_num listener - callback through which the result is provided on success, statuslistener onsuccess int status, bundle data is invoked with wallet information the success code can be one of the following codes with bundle data status bundle keys bundle values usage vts mdes #error_none #wallet_dm_id string device management id n/a paymentappinstanceid = device_serial_num + wallet_dm_id *if you need 'paymentappinstanceid', you can generate it as above #device_id string device id clientdeviceid #wallet_user_id string wallet user id clientwalletaccountid device_serial_num string device serial number n/a on any failure, the error code is provided via statuslistener onfail int errorcode, bundle errordata note please refer spaysdk common_status_table in detail throws nullpointerexception - thrown if parameters are null since api level 2 5 addcard public void addcard @nonnull addcardinfo addcardinfo, @nonnull addcardlistener listener api to add a card from partner app example issuer/bank app to samsung pay on watch partner app uses this api to add card to samsung pay on watch by providing the required card details this helps user to add their cards to samsung pay on watch directly from partner app watchmanager watchmanager = new watchmanager ct, pinfo ; string cardtype = card card_type_credit; string tokenizationprovider = addcardinfo provider_abcd; // get it from issuer app // samsung pay on watch does not provide detailed payload information // generate provisioning payload in accordance with your card network specifications string testpayload = "thisistestpayloadcardinfo1234567890"; bundle carddetail = new bundle ; carddetail putstring addcardinfo extra_provision_payload, testpayload ; addcardinfo addcardinfo = new addcardinfo cardtype, tokenizationprovider, carddetail ; watchmanager addcard addcardinfo, new addcardlistener { @override public void onsuccess int status, card card { log d tag, "onsuccess callback is called" ; } @override public void onfail int errorcode, bundle errordata { log e tag, "onfail callback is called, errorcode " + errorcode ; // to get more reason of the failure, // check some extra error codes in the errordata bundle // such as watchmanager extra_error_reason or watchmanager extra_request_id if provided } @override public void onprogress int currentcount, int totalcount, bundle bundledata { log d tag,"onprogress callback is called " + currentcount + " / " + totalcount ; } } ; parameters addcardinfo - detail card information to add listener - callback through which the result is provided on success, addcardlistener onsuccess int, card is invoked with #error_none status code with added card information on any failure, the error code is provided via addcardlistener onfail int errorcode, bundle errordata the failure code can be one of the following codes with bundle data status bundle keys bundle values #error_registration_fail -104 #extra_error_reason apptoappconstants error_card_already_registered -500 apptoappconstants error_framework_internal -501 apptoappconstants error_invalid_card -502 apptoappconstants error_invalid_cardinput -503 error_invalid_parameter -504 apptoappconstants error_server_reject -505 apptoappconstants error_max_card_num_reached -506 apptoappconstants error_card_not_supported -514 apptoappconstants error_max_pan_provision_num_reached -515 apptoappconstants error_wallet_id_mismatch -516 error_spay_watch_pin_lock_setup_canceled -701 spay_watch_update_is_ongoing -702 spay_watch_taking_log_for_report -703 error_spay_watch_pay_progress -704 error_spay_watch_connection -705 #extra_request_id string value returned from server note please refer spaysdk common_status_table for other error status throws nullpointerexception - thrown if parameters are null since api level 2 17 getallcards public void getallcards @nullable android os bundle cardfilter, @nonnull getcardlistener listener api to get all the cards from samsung pay on watch for the given filter since api level 2 5, partner must define issuer names as a card filter on samsung pay developers while on-boarding bundle cardfilter = new bundle ; watchmanager getallcards cardfilter, new getcardlistener { @override public void onsuccess list<card> cards { // getting card status is success if cards == null || cards isempty { log e tag,"no card is found" ; return; } else { // perform operation with card data for card s cards { log d tag, "cardid " + s getcardid + "cardstatus" + s getcardstatus ; // get extra card data if s getcardinfo != null { string last4fpan = s getcardinfo getstring watchmanager extra_last4_fpan ; string last4dpan = s getcardinfo getstring watchmanager extra_last4_dpan ; string cardtype = s getcardinfo getstring watchmanager extra_card_type ; string cardissuername = s getcardinfo getstring watchmanager extra_issuer_name ; log d tag, "last4fpan " + last4fpan + "last4dpan" + last4dpan + "app2apppayload " + app2apppayload ; } } } } @override public void onfail int errorcode, bundle errordata { log e tag, "onfail callback is called, errorcode " + errorcode ; // to get more reason of the failure, // check some extra error codes in the errordata bundle such as watchmanager extra_error_reason if provided } } ; parameters listener - callback through which the result is provided on success, getcardlistener onsuccess list is invoked with list of cards on any failure, the error code is provided via getcardlistener onfail int, bundle note please refer spaysdk common_status_table in detail throws nullpointerexception - thrown if listener is null since api level 2 13 samsung electronics samsung pay sdk 2 22 00 - nov 19 2024
tutorials mobile
blogsamsung has invested tremendous effort in the digital economy from the very beginning and continuously facilitates millions of people who use samsung wallet. samsung wallet is one of the most used digital wallets right now in the cashless industry. it is a medium that fuels up digital currency transactions by its ease-of-use and security. to support various businesses, samsung has developed the samsung pay sdk which allows you to use samsung wallet’s features effortlessly. the samsung pay android sdk consists of android-based apis to perform transactions using samsung wallet. it helps to implement simple payment solutions, which boost your businesses' growth to the next level. to understand the business and possibilities, visit the samsung pay sdk portal for more information. what is push provisioning? push provisioning is one of the major features of the samsung pay sdk. it allows an issuer bank to push the payment experience to a digital wallet. it simplifies the process of adding a payment card as it can be done with a single tap of a finger. the normal process is time consuming since it involves multiple steps, and the user needs to enter their card information. with push provisioning, the process is easier as it can be done with a single tap, and it's also secure because the process is performed from the issuer application. this tutorial demonstrates how to implement the push provisioning feature in an issuer application with the samsung pay sdk. figure 1: samsung pay push provisioning concept prerequisite to use the samsung pay sdk, you must be an official samsung partner. for information about the partnership process, see the samsung pay member guide. as a samsung pay sdk partner, you can utilize this tutorial while implementing push provisioning. sdk integration to download the samsung pay sdk, go to samsung developers portal > samsung pay > download . when the download is complete, a .jar file called “samsungpaysdk_x.xx.xx_release.jar” can be found under the libs folder. add the samsung pay sdk .jar file to the libs folder of your android project using android studio or file explorer. navigate to the build.gradle file of your application module and enter the following dependency to the dependencies block: implementation files('libs/samsungpaysdk_x.xx.xx_release.jar') if the target sdk version is 30 or higher (android 11 or r-os), include the following <queries> element in androidmanifest.xml. for more information, see declare package visibility needs. <queries> <package android:name="com.samsung.android.spay" /> </queries> since we are using the latest sdk, set the api level to 2.18. we recommend using the updated version of the samsung pay sdk for a better user experience. implement the following code in the <application> element of androidmanifest.xml: <meta-data android:name="spay_sdk_api_level" android:value="2.18" /><!-- most recent sdk version is recommended to leverage the latest apis--> configure the debug or release mode for your project as follows: for testing and qa, set the debug mode value to y. this mode requires the allowed samsung account(s) list to test. for market release to end users, set the debug mode value to n. <meta-data android:name="debug_mode" android:value="n" /><!--set to y if debug mode--> let’s get started since the main functionalities in this tutorial are based on push provisioning, we need to initialize the samsungpay and cardmanager classes first. these two classes take the same parameters to construct, which are context and an instance of the partnerinfo class. the partnerinfo object contains information about partners, which is to validate the request from the issuer application. private val partnerinfo = partnerinfoholder.getinstance(context).partnerinfo private val samsungpay= samsungpay(context,partnerinfo) private val cardmanager = cardmanager(context, partnerinfo) check if samsung wallet is ready since the samsung pay sdk depends on samsung wallet, you need to ensure that samsung wallet is prepared for transactions. check the samsung wallet status before the sdk api call using the getsamsungpaystatus() method. if you get the "spay_ready" status, you can proceed further to call any api. for more details, see the programming guide. samsungpay.getsamsungpaystatus(object : statuslistener { override fun onsuccess(status: int, bundle: bundle?) { if(status == spaysdk.spay_ready){ //enable samsung pay sdk functionalities } else{ //disable samsung pay sdk functionalities } } override fun onfail(status: int, bundle: bundle?) { //disable samsung pay sdk functionalities } }) check if the card is added during development, you may need to know whether the card is already added to samsung wallet or not. to get a list of cards that have already been added to the wallet, use the getallcards() method. for card-related operations, such as getting cards from samsung wallet, the cardmanager class is the responsible one to perform. this means that the getallcards() method is a property of the cardmanager class. this method takes a bundle and an interface as parameters, so it returns the result based on the operation. notethe getsamsungpaystatus() method must be called before the getallcards() method. the getallcards() method cannot return a card list if the getsamsungpaystatus() method responds with a code other than spay_ready. tipone of the most common issues during development is that the getallcards() method returns empty data even though a card has been added. the main reason for this issue is that the card issuer name and issuer name on the samsung pay portal are not the same. for more information, see the faq & troubleshooting page. val getcardlistener: getcardlistener = object : getcardlistener { override fun onsuccess(cards: list<card>) { //show cards } override fun onfail(errorcode: int, errordata: bundle) { //show error } } cardmanager.getallcards(null, getcardlistener) configure your payload the getwalletinfo() method is designed to request wallet information from the samsung wallet application prior to performing the add card operation. wallet information can be mandatory or optional for token providers for payload configuration. for visa, wallet information is mandatory, and you have to use it while building the payload. val keys = arraylist<string>() keys.add(samsungpay.wallet_dm_id) keys.add(samsungpay.device_id) keys.add(samsungpay.wallet_user_id) val statuslistener: statuslistener = object : statuslistener { override fun onsuccess(status: int, walletdata: bundle) { val deviceid: string? = walletdata.getstring(samsungpay.device_id) val walletaccountid: string? = walletdata.getstring(samsungpay.wallet_user_id) //build payload } override fun onfail(errorcode: int, errordata: bundle) { //show error } } samsungpay.getwalletinfo(keys, statuslistener) complete the push provisioning the last command to execute the push provisioning operation in our tutorial is the addcard() method, which is required to perform the push provisioning in samsung wallet. the payload we have created must be delivered with the addcard() method as a parameter. the payload is a tricky part where partners can sometimes get confused or misguided. to be clear, samsung does not provide the payload for push provisioning. the payload is defined between the issuer and the token provider, and it varies based on different issuers and token providers. samsung only delivers the payload to the token provider without consuming anything. the addcard() method also takes a callback as a parameter to return the result based on the operation. tipfor push provisioning of a payment card, samsung pay does not store any card information nor provide any payload for adding cards. so, the issuer needs to provide the payload in a format that is defined in the token provider specification. the issuer and the token provider have their own agreement of data sharing, payload, and encryption. samsung pay is only a medium for this process. val tokenizationprovider = addcardinfo.provider_abcd val carddetail = bundle() carddetail.putstring(extra_provision_payload, payload) var cardtype = card.card_type_credit_debit val addcardinfo = addcardinfo(cardtype, tokenizationprovider, carddetail) val addcardlistener: addcardlistener = object : addcardlistener { override fun onsuccess(status: int, card: card) { //show successful message } override fun onfail(errorcode: int, errordata: bundle) { //show error } override fun onprogress(currentcount: int, totalcount: int, bundledata: bundle) { //extra event for operation count } } cardmanager.addcard(addcardinfo, addcardlistener) summary push provisioning is the powerful experience of sharing information to a digital wallet, and digital wallets transform this experience to the next level by facilitating transactions within seconds. samsung wallet handles these operations and helps the digital payment system to its next step. for more information about the samsung pay sdk, visit the samsung pay developers portal. if you face any issues during sdk implementation, contact the developer support team.
Yasin Hosain
Learn Code Lab
codelabcreate an android automotive operating system aaos app with payments via samsung checkout objective create a shopping app for android automotive os aaos , which uses templates from aaos and ignite store, and processes payments via the ignite payment sdk powered by samsung checkout partnership request to use the ignite payment sdk and have access to development tools and resources, such as ignite aaos emulators, you must become an official partner once done, you can fully utilize this code lab you can learn more about the partnership process by visiting the ignite store developer portal overview android automotive os android automotive os aaos is a base android platform that runs directly on the car and is deeply integrated with the underlying vehicle hardware unlike the android auto platform, users can download compatible apps with aaos directly into their cars, without needing a phone, and utilize an interface specifically designed for the car screen aaos can run both system and third-party android applications as aaos is not a fork and shares the same codebase as android for mobile devices, developers can easily adapt existing smartphone apps to function on aaos the diagram below illustrates the architecture of aaos at the hardware abstraction layer hal level, aaos incorporates additional components such as the vehicle hal vhal , exterior view system evs , and broadcast radio br to handle vehicle properties and connectivity at the framework level, car service and webview modules are included at the application level, the main system applications include car system ui, car launcher, and car input method editor ime additionally, car media and automotive host are incorporated as system apps third-party apps are classified into three categories audio media, car templated, and parked car templates the car templated apps use templates specified by the car app library, which are rendered by the automotive host, customized by original equipment manufacturers oem the library consists of approximately 10 templates list, grid, message, pane, navigation and is utilized in both android auto aa and android automotive os aaos apps to target aaos, you must incorporate an additional app-automotive library that injects the carappactivity into the app the carappactivity needs to be included in the manifest and can be set as distractionoptimized upon launching the application, the carappactivity provides a surface that is employed by the automotive host to render the template models additionally, on the harman ignite store, you can optionally integrate the ignite-car-app-lib, which adds supplementary templates such as explore, listdetails, routeoverview, and poistreaming harman ignite store the harman ignite store is a white-labeled and modular aaos-based automotive app store by connecting app developers with car manufacturers, harman creates unique in-vehicle experiences the ignite store has a rich app ecosystem with unique content, growth opportunities, and long-term partnerships it facilitates future-proof monetization with a payments api powered by samsung checkout after registering at the ignite store developer portal, developers can submit their apps for certification and testing by harman upon approval from the oem, the developer can proceed with publishing their app comprehensive developer documentation and tools are available to support app developers throughout the development process payments api the ignite store comes enabled with payment features empowering developers to monetize their apps developers are now able to offer their apps as paid apps the payment sdk exposes apis for goods and services, in-app purchases, and subscriptions developers can also integrate their own payment service providers psps , to sell goods or services, and receive the money directly in their bank account for a frictionless in-car payment experience, ignite provides a dedicated digital wallet app for end-users to securely store their credit card information the payment processor is powered by the industry proven samsung checkout the developer portal provides additional documentation to allow developers to access ignite aaos emulators, vim3, tablet or cuttlefish ignite images, and additional guidelines set up your environment you will need the following ignite aaos system image running on android emulator or on reference devices android studio latest version recommended java se development kit jdk 11 or later sample code here is a sample code for you to start coding in this code lab download it and start your learning experience! aaos ignite shopping app sample code 11 7 mb prepare your ignite aaos emulator add the ignite aaos emulator to your android studio by following the guide provided in the ignite store developer console open the device manager and start the emulator configure the emulator to use fake data for payments, as instructed in the ignite store developer console under the offline mode tab in the payment sdk section the sample app requires navigation from point a starting location to point b destination location the destination addresses are predefined and near san jose mcenery convention center to shorten the distance between two locations, follow the steps below to set the starting location a open the extended controls in the emulator panel b go to location, search for a location near the destination location, and click set location next, in the emulator, go to the ignite navigation app's settings and enable the following enable navigation simulation enable mock location provider go to settings > system > developer options > location and set ignite navigation as mock location app start your project after downloading the sample code containing the project files, open your android studio and click open to open an existing project locate the downloaded android project igniteautomotivepaymentssdc202488 from the directory and click ok check the ignite payment sdk dependency verify that the ignite payment sdk library is included in the dependencies section of the module's build gradle file dependencies { implementation files 'libs/ignite-payment-sdk-3 13 0 24030417-0-snapshot aar' } add payment permission next, go to the manifests folder and, in the androidmanifest xml file, include the payment_request permission to perform in-app purchases <uses-permission android name="com harman ignite permission payment_request" /> this ensures that the app has the necessary permissions to perform transactions and handle sensitive financial data show the payment screen when an item is added to the cart, the shopping cart screen displays the select store button, selected pickup store address, total amount to pay, and details of each item added the screen also includes the pay button go to kotlin + java > com harman ignite pickupstore > screens > shoppingcartscreen kt in the docheckout function, use the car app's screenmanager to navigate to the payment screen from the shopping cart screen after clicking the pay button getscreenmanager push paymentscreen carcontext, session notethe screenmanager class provides a screen stack you can use to push screens that can be popped automatically when the user selects a back button in the car screen or uses the hardware back button available in some cars instantiate the ignite payment client the ignite payment api provides a singleton class called ignitepaymentclientsingleton, which enables performing and tracking transactions navigate to the paymentscreen kt file and instantiate the ignite payment client private val mipc = ignitepaymentclientsingleton getinstance carcontext define the ignite payment transaction callback the ignite payment transaction provides three callback methods onsuccess, oncanceled, and onfailure after each callback, make sure to set the ispaymentfailed variable to track whether a payment is successful or not update the session which owns the shopping cart screen to reflect the status of the payment transaction call the updatetemplate function to invalidate the current template and create a new one with updated information private val mipctcb = object iignitepaymentclienttransactioncallback { override fun onsuccess requestuuid string?, sessionid string?, successmessage string?, paymentadditionalproperties hashmap<string, string>? { log d tag, log_prefix + "onsuccess rid $requestuuid, sid $sessionid, sm $successmessage" cartoast maketext carcontext, "payment successful", cartoast length_short show ispaymentfailed = false session paymentdone requestuuid, sessionid, successmessage updatetemplate } override fun oncanceled requestuuid string?, sessionid string? { log d tag, log_prefix + "oncanceled rid $requestuuid, sid $sessionid" cartoast maketext carcontext, "payment canceled", cartoast length_long show ispaymentfailed = true session paymenterror requestuuid, sessionid, null updatetemplate } override fun onfailure requestuuid string?, sessionid string?, wallererrorcode int, errormessage string { log d tag, log_prefix + "onfailure rid $requestuuid, sid $sessionid, wec $wallererrorcode, em $errormessage" cartoast maketext carcontext, "payment failed", cartoast length_long show ispaymentfailed = true session paymenterror requestuuid, sessionid, errormessage updatetemplate } } define the ignite payment client connection callback the ignite payment client needs to be connected in order to perform a payment request once the client connects successfully, retrieve the names of the shopping cart items and use them to create an order summary afterwards, construct an ignite payment request containing the total amount, currency code, merchant id, and details of the order summary then, initiate the payment process by invoking the readytopay function of the ignite payment client api private val mipccb = iignitepaymentclientconnectioncallback { connected -> log d tag, log_prefix + "onpaymentclientconnected $connected" if connected { val textsummary = session shoppingcart cartitems jointostring ", " { item -> item name } val ipr = ignitepaymentrequest builder setamount session shoppingcart gettotal * 100 setcurrencycode currencycode usd setpaymentoperation paymentoperation purchase setmerchantid constants merchant_id setordersummary ordersummary builder setordersummarybitmapimage bitmapfactory decoderesource carcontext resources, session shoppingcart store largeicon setordersummarylabel1 "${carcontext getstring r string pickupstore_app_title } ${session shoppingcart store title}" setordersummarysublabel1 session shoppingcart store address setordersummarylabel2 textsummary setordersummarysublabel2 carcontext getstring r string pickupstore_payment_sublabel2 build build try { mipc readytopay ipr, mipctcb } catch e exception { log d tag, log_prefix + "payment exception $e" e printstacktrace } catch e error { log d tag, log_prefix + "payment error $e" e printstacktrace } } } start the payment process and go back to previous screen after the transaction next, in the startpayment function, connect the ignite payment client and the connection callback to start the payment process mipc connect mipccb after the transaction is completed, the updatetemplate function refreshes the template used in the payment screen before calling the schedulegoback function modify the schedulegoback function to navigate back to the previous template screen shopping cart you can use the pop method of the screenmanager screenmanager pop start the navigation to the store to collect the paid pickup the shopping cart screen shows the pickup store location, details of the order, and go to store button after a successful payment go to kotlin + java > com harman ignite pickupstore > pickupstoresession kt modify the navigatetostore geofence geofence function to trigger the navigation to the pickup store when the go to store button is clicked you can use the intent carcontext action_navigate with geo schema rfc 5879 data, containing latitude and longitude e g , geo 12 345, 14 8767 to send the intent, use the carcontext startcarapp api call val geouristring = "geo ${geofence latitude},${geofence longitude}" val uri = uri parse geouristring val navintent = intent carcontext action_navigate, uri try { carcontext startcarapp navintent } catch e exception { log e tag, log_prefix + "navigatetostore exception starting navigation" e printstacktrace cartoast maketext carcontext, "failure starting navigation", cartoast length_short show } run the app on ignite aaos emulator run the pickup-store-app on ignite aaos emulator when the app starts for the first time, it requests for user permissions click grant permissions choose allow all the time for location permission and click the return button 4 browse the pickup store catalog and add items to shopping cart open the shopping cart and click pay you can also change the pickup store by clicking select store check the order summary and billing information then, click confirm and pay to process payment after a successful payment, the app returns to shopping cart screen with the updated transaction information click go to store to start the navigation to the store the app displays a notification when the car is near the store click the notification to show a reference qr code to present to the store upon pick up you're done! congratulations! you have successfully achieved the goal of this code lab topic now, you can create an aaos templated app, which supports payments by yourself! if you're having trouble, you may download this file aaos ignite shopping app complete code 11 7 mb learn more by going to the developer console section of the ignite store developer portal
Develop Samsung Pay
docunderstanding and using the sdk the samsung pay sdk is an application framework for integrating selected samsung wallet features with android-based partner apps on samsung devices the following major operations are supported in-app payment gives customers the option of paying for products and services with samsung wallet push provisioning allows customers add a bank card to samsung wallet from the issuer app by providing the required card details to integrate your partner application with the samsung pay sdk, the following components are included your sdk download samsungpay jar contains classes and interfaces of the samsung pay sdk which need to be integrated to partner apps javadoc provides descriptions of the apis included in the samsung pay sdk, along with sample code showing how to use them sample merchant app and sample issuer app showing how samsung pay apis can be coded in a finished android project all major operations of samsung pay sdk are implemented for demonstration purposes samsung pay sdk architecture the following diagram shows a high-level architecture revealing the general interactions between the samsung pay sdk and a partner app viewed at this level, the partner apps leverage the samsung pay sdk to perform the operations shown ― push provisioning and opening favorite cards for issuers; online payments for merchants ― with samsung pay the key components involved are partner app - merchant- or issuer-developed app for making online/offline payments and provisioning payment cards through samsung wallet samsung pay sdk - sdk integrated into the partner app for direct communication with samsung wallet samsung wallet app - wallet app that the samsung pay sdk communicates with financial network - comprises the payment gateways, acquirers, card associations, and issuers that participate in transaction processing under agreement with the merchant the main classes comprising the samsung pay sdk include samsungpay – used by the partner app to get the samsung pay sdk information and the status of samsung wallet app on the device paymentmanager – provides payment/transaction functionality cardmanager – manages card list get, add, update functionality watchmanager – manages all functions related to samsung pay watch cardinfolistener – interface for requestcardinfo result from samsung wallet customsheettransactioninfolistener – interface for transaction success/failure callbacks from samsung wallet use case in-app payment the most common in-app online payment use cases take the following form merchant app presents user with the option of making payment with samsung wallet upon the user selecting the samsung pay option, the merchant app calls the apis included in the samsung pay sdk to initiate a transaction with samsung wallet app samsung wallet app responds with the tokenized payment information necessary to complete the transaction merchant app forwards this payment information to the designated payment gateway pg , either directly through the merchant's web server, or indirectly via the samsung-pg interface server for normal transaction processing use case app-to-app push provisioning the push provisioning use case ― adding payment cards to samsung wallet from the card issuer’s app ― typically takes this form the user logs into the issuer app the issuer app checks if samsung wallet is activated on the device and ready to use if it is in the ready status, the issuer app displays an add button for cards not currently registered/enrolled with the samsung wallet app if the add card option is selected, the issuer app calls an api to push the proper payload data to samsung wallet while the card is being provisioned, samsung wallet stays in background setting up sdk development environment the importance of maintaining a good development environment cannot be overstated for integrating the samsung pay sdk with your partner app, the following prerequisites and recommendations help ensure a successful sdk implementation system requirements the samsung pay sdk is designed exclusively for samsung mobile devices supporting samsung pay and running android lollipop 5 1 android api level 22 or later versions of the android os the sdk’s in-app payments functionality requires android 6 0 m android api level 23 or later versions of the android os note as of sdk version 1 5, if the device runs android lollipop 5 1 android api level 22 or an earlier version, the getsamsungpaystatus api method returns a spay_not supported status code merchant apps still using samsung pay sdk 1 4 or earlier not recommended must check the android version running their app use the following snippet to determine the os version running on a device and whether or not to display the samsung pay button in your partner app import android os build; // in-app payment supported on android m or above // check android version of the device if build version sdk_int < build version_codes m { //hide samsung pay button } service registration to develop a samsung pay sdk service, merchants and issuers need to register for an account with samsung pay developers in order to create the appropriate service type for their applications here are some helpful links inside the portal become a member https //pay samsung com/developers/tour/memberguide create services https //pay samsung com/developers/tour/svcguide register apps https //pay samsung com/developers/tour/appsguide manage services and apps https //pay samsung com/developers/tour/svcnappsguide add samsung pay sdk to your project be sure to do the following before attempting to use the sdk if not already part of your environment, download and install an ide android studio is recommended download the samsung pay sdk the sdk package has the following directory structure folder contents docs javadoc – api reference documentation libs samsungpay jar sdk java archive file – contains the samsung pay apis to be used by your partner app samples sample apps configure your ide to integrate the samsung pay sdk with your partner app a add samsungpay jar to the libs folder of your android project b go to gradle scripts > build gradle and enter the following dependency dependencies { compile files 'libs/samsungpay jar' } c import the sdk package into your code import com samsung android sdk samsungpay v2; proguard rules if your app s have any issue with proguard, the following rules are recommended dontwarn com samsung android sdk samsungpay ** -keep class com samsung android sdk ** { *; } -keep interface com samsung android sdk ** { *; } when dexguard is employed, the following additional rules apply -keepresourcexmlelements manifest/application/meta-data@name=spay_sdk_api_level android r os targetsdkversion 30 informationfrom android r os if the target sdk version is 30 , you must include the following <queries> element in the androidmanifest <?xml version="1 0" encoding="utf-8"?> <manifest xmlns android="http //schemas android com/apk/res/android" xmlns tools="http //schemas android com/tools" package="xxx xxx xxx xxx"> <queries> <package android name="com samsung android spay" /> <package android name="com samsung android samsungpay gear" /> </queries> configuring api level api level attributes as of sdk version 1 4, enhanced version control management has been introduced to improve backward compatibility and handle api dependency from country and service type for example, if a partner integrates the latest sdk―for instance, api level 2 22―but continues to use apis based in level 1 4, the partner app remains compatible with samsung wallet apps supporting api level 1 4 without the necessity of upgrading the samsung pay app the chief characteristics and properties of the api level include every api starting from version 1 4 has an api level assigned based on the sdk version number in which it is introduced the sdk’s javadoc reference can be filtered by api level so you can determine the minimum api level you need to configure in the metadata section of your app’s androidmanifest file the earliest possible version is 1 4 this lets you use the api level defined in your androidmanifest without having to trigger an upgrade of the samsung wallet app on the user’s device implement the following usage in your androidmanifest <application <meta-data android name="spay_sdk_api_level" android value="2 22" /> // most recent sdk version is recommended to leverage the latest apis but it need to be set to 2 17 for russia </application> partner app verification in partner verification process samsung pay sdk verify your registered app, version in samsung pay portal and service it also determines device and app compatibility your app needs to verify the presence of the samsung wallet app on the device, its status, and whether or not its version is sufficient to support your implementation of the sdk appendix a common terminology terminology description aavs automatic add value service aidl android interface definition language for communication merchant a business entity engaged in retail e-commerce that provides an online checkout service for purchasing its products and/or services to registered end users issuer financial institution empowered to issue credit and/or debit payment cards to qualified consumers and businesses payment gateway pg e-commerce app service provider equipped to authorize credit card payments for e-businesses, online retailers, bricks and clicks, or traditional brick and mortar payment token secure method for payment ensuring that a cardholder’s information is not exploited by unauthorized parties samsung pay samsung’s proprietary mobile wallet app and payment system samsung pay service the server and service components of samsung pay samsung pay watch samsung pay app on samsung galaxy watches to support payment system eligibility check a query by third-party apps to check whether or not samsung pay is supported/activated/ready-to-use on a samsung device mst magnetic secure transmission tui trusted user interface
Learn Code Lab
codelabdevelop a blockchain shopping app objective create a shopping application with samsung blockchain platform sdk and pay using ethereum network overview the blockchain industry is expanding in many ways it is growing the most as a means of payment samsung blockchain platform sdk helps to make payments easily with cryptocurrency you can interact with blockchain through a simple api call to create a transaction in this code lab, you can pay for a product using the ethereum network in a simple shopping app, which is a decentralized application dapp dapps run and store data on the blockchain network instead of a central server set up your environment you will need the following java se development kit 8 or later android studio latest version recommended mobile phone with samsung blockchain sample code here is a sample code for you to start coding in this code lab download it and start your learning experience! platform sdk sample code 3 94 mb enable developer mode to activate developer mode on your mobile device, follow the steps below navigate through settings > biometrics and security > samsung blockchain keystore and click about blockchain keystore tap the samsung blockchain keystore app name quickly, ten times or more if succeeded, developer mode will show import project file open the downloaded sample code containing the shopping app project go to file > open and select the open file or project window every gui resources are already included in the provided project you simply need to fill out the code by following the next steps moreover, it is recommended to go through the documentations of samsung blockchain platform sdk initialize the instance create an sblockchain instance this is the first step since sblockchain is the initial base class of sdk along with that are hardwarewalletmanager responsible for wallet operations accountmanager responsible for account operations msblockchain = new sblockchain ; msblockchain initialize mcontext ; maccountmanager = msblockchain getaccountmanager ; mhardwarewalletmanager = msblockchain gethardwarewalletmanager ; mcoinnetworkinfo = new coinnetworkinfo cointype eth, ethereumnetworktype goerli, rpcurl ; connecttokeystore ; connect to samsung blockchain keystore you can get hardware wallet instance from hardwarewalletmanager hardwarewallettype refers to the type of cold wallet to be connected, such as samsung blockchain keystore and ledger nano s mhardwarewalletmanager connect hardwarewallettype samsung, false setcallback new listenablefuturetask callback<hardwarewallet> { @override public void onsuccess hardwarewallet hardwarewallet { handler post new runnable { @override public void run { log i tag,"hardwarewallet is connected successfully" ; mprogressbar setvisibility view invisible ; setaccountstatus ; } } ; } @override public void onfailure @notnull executionexception e { mprogressbar setvisibility view invisible ; e printstacktrace ; } @override public void oncancelled @notnull interruptedexception e { mprogressbar setvisibility view invisible ; e printstacktrace ; } } ; the second parameter of connect api refers to reset if you do not want to reset the wallet then keep it false, otherwise true manage your account now, your shopping dapp is connected to the keystore it means that if you have your own account with balance, you can now buy using ether or eth let’s create an ethereum account to be used for payment for generating a new account with samsung blockchain platform sdk you need an instance of the accountmanager from sblockchain accountmanager provides methods for fetching, creating, restoring accounts, and other more once you have an instance of accountmanager, you can call generatenewaccount as shown below it has methods regarding accounts such as get, create, and restore refer to the samsung blockchain platform sdk documentations for more details hardwarewallet connectedhardwarewallet = mhardwarewalletmanager getconnectedhardwarewallet ; if connectedhardwarewallet != null { try { maccountmanager generatenewaccount connectedhardwarewallet, mcoinnetworkinfo get ; } catch interruptedexception e { e printstacktrace ; } catch executionexception e { e printstacktrace ; } } if an account is already created, textview is shown at the top of the app and the create account button is disabled to prevent further account creation list<account> accounts = maccountmanager getaccounts null, cointype eth, ethereumnetworktype goerli ; if !accounts isempty { methereumaccount = ethereumaccount accounts get accounts size - 1 ; tvaccountstatus settext methereumaccount getaddress ; btncreateaccount setenabled false ; } get instance for ledger service after creating an account, you can use it for payment in your shopping dapp each coin blockchain ledgers has its own system to be stored in blocks samsung blockchain platform sdk provides abstracted api sets to developers for signing and sending supported cryptocurrency transactions over the blockchain network create coinservicefactory and just use any ledger you want in this scenario, use ethereumservice ethereumservice service = ethereumservice coinservicefactory getcoinservice mcontext, mcoinnetworkinfo ; at this point, your shopping dapp is ready to provide payment methods working on ethereum notebefore the next step, you need at least one valid ethereum account show payment sheet when a user selects an item, the app should show the payment screen it must show “who will pay how much amount of ether to whom” in the blockchain world, ethereum ledgers require more information, such as transaction nonce, to record that transaction into ledgers with samsung blockchain platform sdk, developers can do everything needed to show the payment sheet, intent should be created, which is to call the payment activity on click event of product object fill the parameters required and startactivityforresult to show a payment sheet item item = itemlist get position ; biginteger price = ethereumutils convertethtowei item getprice ; ethereumservice service = ethereumservice coinservicefactory getcoinservice mcontext, mcoinnetworkinfo ; hardwarewallet connectedhardwarewallet = mhardwarewalletmanager getconnectedhardwarewallet ; intent intent = service createethereumpaymentsheetactivityintent mcontext, connectedhardwarewallet, ethereumtransactiontype eip1559, methereumaccount, sample_to_adderss, price, null, null ; startactivityforresult intent, 0 ; get ether from faucet you need money when you buy something a free faucet site is provided to get ether if you have an ethereum account, just go to webview fragment and press send me eth button see the result of transaction if the payment was performed successfully from the payment screen, the result of transaction can be received from onactivityresult if the transaction is performed properly, you can find the result_ok at resultcode from the intent, a txid is shown which can be used to check your transaction’s status call gettransactiondetail txid string api method in ethereumservice and check the block# if there’s any valid countable number, your transaction is stored in blocks successfully and the payment is done if you can’t find it, just wait it’s processing among ethereum nodes alternatively, simply find the txid in goerli testnet explorer run the project you have created and verify that it works properly open the app and select the product from the list in the payment screen, select the fee to pay to the ethereum network and confirm the transaction then, check the result of the generated transaction sample images of the app screen can be seen below you're done! congratulations! you have successfully achieved the goal of this code lab now, you can develop a shopping dapp using samsung blockchain platform sdk by yourself! if you're having trouble, you may download this file platform sdk complete code 3 95 mb to learn more about developing apps with samsung blockchain, visit developer samsung com/blockchain
tutorials galaxy watch, design
blogthese days, distributing digital content is very popular. if you are creative and like to design, then entering into the watch face market would be perfect for you. galaxy watch studio (gws) has a feature, called trial periods, that lets a user try out your watch face before buying it. a trial period is the time when a customer can try a paid product without paying money. samsung in-app purchase (iap) is used to configure this feature. a trial period can be set from 1 minute to 999 days. as a seller, a key metric is to measure and maximize the conversion from free trial period to purchase. however, the most common business model for app purchases for galaxy watch in 2019 was the paid app model—without a trial period. in the majority of cases, the consumer assesses the paid app based on the screenshots and consumer reviews in galaxy store, buys it, and then sees the app on the watch. the try-and-buy model allows the user to test the app risk-free on the watch for a trial period before buying it. a watch face can be free or paid. if it’s your first attempt to upload a watch face in galaxy store, then start with a free watch face. the publication process is fairly easy, and you can become a free seller by registering in seller portal. after registering, you have to become an approved seller in order to publish watch faces. to become an approved seller, submit a watch face for design review. if you want to publish a paid watch face in galaxy store, then you have to be a commercial seller. read commercial seller request guide for details. free watch face create a new project using gws. after developing the watch face, upload it to seller portal. read the build and upload article to learn about this. you can get a clear view about registering an application in the seller portal from the application registration guide. paid watch face a trial period becomes relevant when publishing a paid watch face. integrating this service is easy in gws. a user may not want to buy a watch face based on just seeing some screenshots. he/she might be convinced to buy that watch face after using it for a while. a trial period lets a user do this. before distributing the watch face for sale in galaxy store with a trial period, you have to change the iap settings in gws. iap settings in galaxy watch studio go to gws > project > in app purchase settings or click on the in-app purchase settings icon from the toolbar. check ‘enable in-app purchase’ choose one of the trial options. set the duration of the trial period (at least 1 min). write an item id using english letters, numbers, and certain special characters (. - _). note: use this item id for when registering your watch face. if you write the wrong item id while registering your watch face in galaxy store seller portal, the trial period won’t work in your watch face. now, click ok. select the iap test mode from project > build > iap test mode. there are three types of modes in iap: commercial: real transaction happens in this mode. success test: this mode is for testing the iap for successful purchase. no real transaction occurs in this mode. failure test: this is for failure testing. you can check what happens when a user fails to purchase the watch face. note: to test the trial period, you have to register your watch face in seller portal first. then, you can test the trial period on your device. upload the watch face if you want to test your trial period, follow the steps below: open the project in gws. go to build. set the iap test mode as ‘success test’ while building the watch face. after building the project, go to seller portal or click on the ‘upload’ button in gws and log in. follow the steps which are described in the build and upload section for uploading your watch face to seller portal. if you forget to enter information in the in-app purchase section, then the trial period won’t work in your watch face. so be mindful about it. if your watch face is paid and it has a trial period, you have to set the price in the in-app purchase section. go to the country/region & price section and set the price as ‘free’. otherwise, customers might have to pay money for both the trial version and after the trial version has expired. when you upload the binary of your watch face, your watch face will be registered. do not submit your watch face, just save it. after registering, you can test the trial period of your watch face. refer to "test the trial period" in trial periods. when you are ready to sell your watch face, do the following steps: in gws, go to build. set the iap test mode as ‘commercial’ and then build the project. after building the project, go to seller portal or click on the ‘upload’ button and log in. if you have uploaded your watch face for testing already then find your application and click on ‘registering’. delete the binary from ‘binary’ section and upload the new one. tip: you can mention that your watch face is "try and buy" in the description box in the app information section. this may create interest to download your watch face and use the trial version. if everything is done, click ‘submit’ to upload your watch face for validation and publication. it may take 2 - 3 weeks to publish your watch face in galaxy store. you can check the status of your watch face from seller portal in the application status tab. you can check the sale status of your watch face from home > statistics. for more information about trial periods, see the related article on the samsung developers site. if you have any questions, visit the gws forum.
Jakia Sultana
Learn Developers Podcast
docseason 1, episode 2 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 dan appelquist samsung internet developer advocacy in this episode of pow, i interview dan appelquist, director of developer advocacy for samsung internet dan first got involved with web browsers way back when the internet first got started, and he was heavily involved with the web standards movement that was established at that time soon after, dan relocated to london, england, and remains there today, working out of the samsung uk office listen download this episode topics covered the beginning of mobile web web standards and user experiences the benefits of samsung internet browser privacy and security web developer ecosystem progressive web apps samsung internet and ar/vr augmented reality / virtual reality android developers 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! podcast of wisdom from the samsung developer program, where we talk about the latest tech new trends and give insight into all of the opportunities available for developers looking to create for samsung i sat down with dan appelquist, director of developer advocacy for samsung internet dan first got involved with internet browsers way back when the internet first became a thing and he was heavily involved with the web standards movement that was established at that time soon after dan relocated to london, england and remains there today working out of the samsung, uk office hey, dan, thanks for coming on to the podcast i'm going to start with a real simple question who exactly is dan appelquist? dan appelquist 00 47 well, first of all, thanks for having me on the podcast i really appreciate it so i am director of developer advocacy for samsung internet, which is samsung's web browser i'm also somebody who's been working on the web since before there was a web so i have a background i started working in startups in the early nine, early and mid 90s, that were kind of working on web sites and web services for the publishing industry i went on and became a com, cto, being sent over to the uk from new york, to be cto for the street com at uk, which was this the uk arm of the street com i became a com refugee and because i was here in europe at the time in the early 2000s, i became involved in a lot of projects that were helping to bring the web to mobile, and were happening to helping to create digital mobile services, which was something where europe at that time was a lot farther ahead than the us so it's very interesting and exciting time to kind of be working with companies like vodafone, later telefonica to help build these kinds of services, emerging services for emerging devices and handsets and that kind of thing tony morelan 02 10 yeah, that must have been pretty exciting to have been, you know, working on technology, really, at the very beginning of something that was going to, you know, honestly, change our world forever so why is it that you would say that europe is further along than the us when it came to the start of the whole mobile web? dan appelquist 02 25 well, when in say 2001 2002, there were already color web phones that were coming onto the market here in the uk and elsewhere in europe that we're delivering digital services, like very simple digital services, but still digital services, news and online information on that kind of thing whereas i still had to really explain to my parents what it is that i was doing you know, people at that time in the us who really didn't think of their mobile phone as being for anything besides calling, even text messaging was not very well understood as a medium because the interoperability wasn't there between the different carriers around text messaging and it was only later that mobile digital services started to really develop and then the mobile internet came out of that whereas in europe, i would say my experience of it anyway has been was that with the standardization of gsm, across the continent, you had a much stronger base for delivery of mobile services across a standard range of handsets, standard range of networks, all that all that kind of thing all the technology was pretty, it was pretty standard tony morelan 03 36 and gsm is global system for mobile communications that's right dan appelquist 03 39 yeah yeah tony morelan 03 41 so the samsung internet, what exactly is samsung internet? dan appelquist 03 44 right so first of all, samsung internet is a web browser and for those who are familiar with web browsers, immune to other commonly known commonly used web browsers, especially on desktop computers, include google chrome, mozilla firefox, internet explorer from microsoft, which is increasingly being subsumed by microsoft's new browser, which is edge and then apple's safari browser probably are the biggies, the ones that people most people have heard about when it comes to market share, and especially on mobile samsung internet is also a browser that has a very strong market position and that's because we ship by default with every samsung device we're also part of the chromium project we're a browser that's built on top of the chromium, open source, project and code base that is the same code base at google chrome is built on top of it's also the same code base that microsoft edge is built on top of so there's a community of companies and organizations that are contributing into that into that open source project, including samsung and what we're doing is we're taking that and we're delivering samsung internet for android which is our kind of premium browser for the provides what we think of as the best user experience for the web on definitely on samsung devices, but we are also available across all android devices so any android device, you can download and install samsung internet and use it as your as your primary browser tony morelan 05 21 you know, of course, my android phone is a samsung phone so i didn't know that that a samsung internet browser is available for all android phones that's pretty cool yeah do you have an idea of how many people use the sampling internet browser? dan appelquist 05 34 on samsung devices? we're very high on other devices we're not that high but part of the point of being on other devices is that we it's it was very much a developer play to get it was a minimal extra effort i shouldn't say that because our engineering team it's probably gritting their teeth and saying are you kidding me? this was not minimal effort but anyway, it was it was it was definitely worth the effort? because one of the key things that we go out to developers and talk about is testing and the importance of testing on samsung internet one of the things that we're hearing very early on when we started work in 2016, on developer advocacy for samsung internet was, well, we can't test we don't have a samsung device can you lend us a samsung device? well, being available on non-samsung devices really made that conversation a lot easier, because we could just say, look, just download samsung internet and run it on whatever device you have and you'll get the get that experience and you'll be able to test and testing across browsers is so important when you're building any kind of application or any kind of web application tony morelan 06 41 and that was the reason why the whole web standard movement started, wasn't it? because we had so many different browsers that, you know, often developers were having to create different versions of their website just to be compatible with the different browsers dan appelquist 06 51 yeah, certainly the adherence to web standards has been a constant issue across the web i think that things are a lot better now than they used to be there are still differences in, in how the in the user experience of the browser itself, it can cause issues i'm going to be one example like, we have a feature on our browser, which is a scroll to the top of screen, which is a little button that appears over overlaid on top of the web content that allows the user to wherever they are to scroll right back up to the top of the screen now, if the web developer didn't test their application in samsung internet, they might put a key piece of ui underneath that section of screen where we overlay the button so it you know it things like that are these little micro issues that testing really helps and that is not necessarily about web standards compliance it's more about how you make sure that your web application runs correctly and all the ui is correct for the ui choices that that browser has made and how it displays it to you you know, tony morelan 08 01 i actually have a lot of experience with designing watch faces for samsung watches and the same is true yeah, it's best to design around the system icons that may appear under certain circumstances so that you don't have any, you know, usability issues 08 13 yeah tony morelan 08 15 so what is samsung internet done to drive awareness for developers? dan appelquist 08 19 so a lot of the work that we started off with when we started the team in 2016, was trying to drive market awareness of something and we already knew that, because we had some stats that we had strong usage numbers so we are roughly 10% of all mobile browsing in europe, for instance, the issue was actually driving awareness amongst developers that they really needed to, to understand those numbers and therefore pay attention to testing and you basically why they should pay attention to us as a browser so we started off by working with people like stat counter, that actually is one source that people use recordable stats of different browsers we then went on to work with google analytics so we after we've gotten counter to kind of separate us off from google chrome, we then went to google analytics and we got them to separate us off from google chrome and amazingly, after that happened, we started to get all these calls from different people uk government was one example where they started to say, hey, we've just had this amazing jump in usage from samsung internet, while they didn't actually have a jump they had, they always had very high usage of samsung internet but they just never knew it because google analytics was lumping us together with google chrome so and that's the problem with a lot of these stats keeper sites is that they weren't if they were just if they were not paying attention to that your specific browser, they were lumping you together with the particular engine that the browser based on so getting that right was like a key element and then we can take those numbers to other places and we can say like, look, this is how many of your users or what percentage of users using samsung internet, we really think you would benefit from talking to us or you would benefit from testing on samsung internet would you like to come do some joint projects with us all that kind of stuff we also have been working with places like mdn so mozilla developer network, or mdn, has recently or within the last few years has changed from a very mozilla specific website into basically a documentation website for the web, across browsers and what's underpin that is that they now have a product advisory board, which includes people from microsoft, samsung, mozilla, obviously google they also have people from a couple of smaller organizations such as boku, which is the north kind of open source development shop so they have been doing a lot to, to kind of create, and to reinforce the understanding that developers have it that's a cross platform development site so as part of our work there, we made sure that when there's a documentation page about a particular api, and they have a list of browsers underneath that documentation, that is the listed, supported browsers, versions for that particular api that said, some internet appears in that list can i use comm is another example of a website that people use when they want to find out if they can use a particular api and a particular browser, they were also not separating yourself from chrome so actually working with them, and then working with them through mdn we actually got them to use all of the mdn compatibility data, which is data that we update, that's data that our team goes in the background and updates through github, through an open source procedure, so that all that data is up to date both on mdn and on can i use so that developers have up to date information about which api's they can use and which versions of which browser and then in general, we've been doing a lot of things like writing blog posts, we write a lot of technical blog posts about the use of different api's, the use of different technologies, opinion pieces about topics on the web, we tend to focus on things where samsung has some kind of engineering investment so things like progressive web apps, that's one area where we've done a lot of work recently we've also done a lot of work on web xr and the immersive web and things like web payment, that kind of thing we also sponsor conferences, and we go out and speak at conferences and events these days, we're obviously we're doing a lot of virtual events and we're really trying to play a leadership role in how the developer advocacy community deals with the current situation with a lockdown by showing how you can very effectively engage with the developers and create conversation with developers using virtual needs tony morelan 13 04 you know, i couldn't agree with you more, you know, the timing with the launch of our new podcast here is actually right in line with probably what's going to be a huge change for all of the industries as we move forward in this new world of information sharing virtually, yeah, you know, i actually attended one of your virtual office hours and it was nice, because, you know, you brought in some outside people, some industry people to participate dan appelquist 13 28 and that's, and that's something that we that's the kind of ethos that we have had from the beginning we actually ran a two-day event in san jose a couple years ago, called samsung create and the whole idea of that was to feature samsung people yes, but at least half the speakers that we had were front were third party speakers that we brought in from the industry and we had an mdn speaker we had a microsoft speaker, later google speaker you know, it also fits together with the fact that our team besides doing the developer advocacy and outreach we're also doing a lot of industry work so we do work in w three c, i co-chair, a group in w three c, which is the world wide web consortium that sets standards for the web, i co-chair a group there called the technical architecture group, which is a kind of technical steering group for web standards my colleague, ada co-chairs, the immersive web working group, which is working on technologies that bring ar and vr to the web so we're not only playing a role in terms of getting the word out about these technologies, but we're also playing a role in terms of setting the standards tony morelan 14 40 is simply internet just for android dan appelquist 14 42 the work that we're doing is on samsung internet for android and the team that we're attached to a samsung internet for android if you have a samsung tv or if you have a samsung watch, you may also know that there are other versions of samsung internet they have the same logo and they are also based on chromium, but they're actually built by different teams within samsung divisions so there's some cross working between those different groups, especially because they're all using the chromium base and so they share a lot of knowledge and they share a lot of information but actually, the work that we're doing, we focus on samsung internet for android, tony morelan 15 20 when you have improvements that you want to make to the samsung internet browser are those released at the same time when new devices are released dan appelquist 15 28 so one of the things that we did very early on, and i think this was right around the time when i started in 2016, is we unlinked browser releases from device releases, we're now rolling out on a regular cadence, new releases of the browser that are released through play store and also through galaxy store and we do sometimes do releases that are timed to device releases, but those are still in the in the context of our of our regular software release schedule so and that's really important for the web, because the web needs to be evergreen when there's a security vulnerability, or some kind of new feature that web developers want to use, they don't want to have to wait for a new device to come out in order to be able to use that feature likewise, when there are features or technologies that are deprecated, from the web stack, you really want to, either because they're vulnerable, or they're, they're difficult to use, or they're just not very performant or however, you want to be able to make sure that you can update all the browsers to remove that feature tony morelan 16 31 and that's great to hear that, that the updates are not tied to new device releases, you know, because i'm sure that developers are wanting to get those updates just as soon as soon as possible and you can get those features out to the to the developer community that's right yeah, yeah so tell me what is the benefit of using samsung internet over another browser, like say google chrome, dan appelquist 16 51 one of the things that we pride ourselves on is a focus on user privacy so we think that we have better privacy features than google chrome and that's certainly a goal that we have and something that you can see, as evidenced through a lot of the features that we ship with the browser so for instance, we have secret browsing mode, which is secured by knox and also linkedin to our to biometrics on the device, so that you can secure it with your fingerprint or your face id or however, we also integrated into samsung pay currently, that's only in the us but there's a web feature called web payment, which integrates into samsung pay for us customers that allows you to pay directly from your web page using samsung pay using the on-device payment technology, we integrate into one ui so that's the samsung specific ui across the device, which our browser is based on top of as also as part of the whole privacy consideration we allow our users to download and install ad blockers we allow to download and install extensions, which can be privacy helping or can be other things like shopping related for instance, we also allow you to choose your own default search engine so we have for a while now allowed you to choose duckduckgo is a search engine, which is a very privacy focused search engine but with the release 11 2, that's about to come out we've actually even increased that list for and we have way more search engines that you can choose as your default search engine you can't do that with google chrome and we have our own built in smart anti tracking technology that uses machine learning on the phone to in a very privacy focused way shield your browsing activity from an unwanted tracking on the web, which is a major issue right now, for a lot of users tony morelan 18 49 you know, it's pretty safe to say that just about everybody at some point has had something hacked whether it's you know, a credit card or maybe it's an online account, so always happy to hear about, you know, new technologies that will definitely help keep the internet safer tony morelan 19 03 can we talk a little bit about revenue? tony morelan 19 04 how does samsung internet create revenue? dan appelquist 19 07 well, we are getting revenue from search referral that's the same as every other browser that's out there i mean, how do browsers make money browsers usually make money from search referral we also have opportunities for business development when it comes to our quick access bar, which is region specific so when you first load the browser, you're going to see a number of links that show up, you know, on your kind of quick access screen, that all of that is user configurable, and the user can change those whenever they want to it's about what the defaults are those are really how samsung is making money i think the other part of it is more of a strategic play there are billions of users using the web why would samsung want to see to that territory to somebody else? instead of being able to control that user experience and provide the best user experience, and we can, that's great so how does the web developer ecosystem differ from other developer ecosystems? one thing that is important to think about what the web developer ecosystem is that it's inherently cross browser, cross device and cross ios, and that's true of the web in general, the web needs to be able to exist across different browsers across different classes across different form factors you need to be able to bring up your web page and have it work on your television as well as your laptop screen as well as your phone responsive design and progressive enhancement have been some of the key technologies that web developers have been using to ensure that that can be the case, feature detection these kinds of things are really important when it comes to building websites you're not just building for one particular device you're not just building for one particular vendor you're you've really got to be listening to and paying attention to a lot of different voices, when you enroll in a developer program for a specific platform, you tend to be focusing on one particular device or one particular brand, one particular os and that also provides some clarity, you know, which can be a good thing however, when you're developing for the web, you need to pay attention all these different platforms and devices that's where something where mdn can come in, and why we're putting so much energy into that because it can be a place where developers can come and find out information across different platforms tony morelan 21 36 you had mentioned a little bit about progressive web apps for new developers out there can you explain what exactly is a progressive web app? dan appelquist 21 42 so a progressive web app is i mean, i mentioned technologies like progressive enhancement and responsive web design, which help developers build web applications that can that can work well across different browsers, different oss, different devices, different form factors the idea of progressive web apps brings that to the next level where we try and learn a little bit from the success of native applications on the mobile platform in particular, and are able to provide a very app like user experience for the web application itself so a really good example of a progressive web app, probably one of the best ones out there is the twitter pw a lot of people are removing twitter from their phones entirely and simply using you're removing the native app, i should say, from their phones entirely and just using the progressive web app, because it provides almost all of the same features, but in a much more lightweight and much more privacy centric kind of kind of way because when you're using the twitter progressive web app, it's been saved from the browser, and therefore it runs inside of the browser even though from a user perspective, it appears like any other application on the phone, it's actually running inside of the browser so it's running in the same context, as saw the other browser tabs that you have going so it's a bit like, i've called it having your cake and eating it too in terms of being able to build something really easily build something cross platform, but also be able to enjoy that real estate on the phone home screen push notifications that keep bringing the user attention back ability to have through a service worker kind of offline experience, all the kind of features that users expect from a regular native application they can begin to expect from these kinds of progressive web apps tony morelan 23 35 yeah talk a little bit about ar and vr as they relate to samsung internet can you share a little bit about what you were doing in those areas? dan appelquist 23 42 so samsung internet was one of the first browsers to launch the web vr api that api has actually been recently deprecated in favor of the web xr api, which is the api that my colleague ada has been sharing working group to create webex r is a way to bring ar and vr into the browser now, if you are familiar with kind of ar and vr, in a kind of game, console type environment or scenario, or with various specialized equipment, then you might be scratching your head and thinking, well, why? why do i need ar and vr in my browser is the target it's because the target audience for these kinds of ar and vr applications in the web are a little bit more like casual games are to the gaming industry we fully expected we have seen the development of web applications in the gaming space and also in the kind of enterprise space where they take advantage of the technology in the browser to enable you to deliver a kind of virtual environment, a shared virtual environment that provides a lot of those kinds of advantages to a rm vr experience, but you don't have to download any software, you don't have to make sure that your, your whole set of download software is correct and it works progressively across different environments so a couple years ago, we worked with bbc here in london to deliver a doctor who gave that was coming out alongside of the launch of one of their seasons of doctor who it's basically like a very simple navigating the tardis it was called the time vortex, navigating the tardis along a vortex and avoiding obstacles and that kind of thing but the reason they were they were so interested in web vr at the time, was that it's available across multiple browsers they have a public service mandate where they're trying to get that application into as many hands as possible into the hands of kids that may have like a, you know, an older phone that aren't going to have the latest up to date technology and an ar headset or a vr headset those are the kinds of use cases that i'm interested in how do we get these tools have ar and vr into everybody's hands? and i think the web is well positioned to be that platform definitely tony morelan 26 08 let's talk a little bit about success and challenges can you first tell me about some of the challenges that samsung internet has faced? dan appelquist 26 14 i think one of the challenges and i alluded to it before maybe is just recognition recognition of samsung internet as a as a key browser we know we are, we are increasingly driving that awareness amongst the developer community but we still run a cross a lot of people who just never heard of us or if they heard of us that kind of dismissed us alongside of all the other oem browsers we like to say we're not actually like any of the other oem browsers because first of all, we have enormous market share compared to our market share it doesn't even near mcateer doesn't compare to ours second of all, we put a lot back into the web platform and that's extremely important to us we put a lot back into the open source side of it and we put a lot back into the and standard cipher so driving that has been a challenge and continues to be a challenge but it's something that we took on and we understand that and i think we're turning that corner on that one tony morelan 27 11 sure and there's a huge value when there are multiple browsers out there i mean, if you go back to when internet explorer dominated the market, and then firefox came on board, that's when we started to see a much better browser experience correct? dan appelquist 27 23 yes and in fact, that's another kind of philosophical point that drives the work of our team is that we strongly we strongly believe in browser diversity it's not a web where one browser dominates, is not actually going to be a healthy web ecosystem we are based on top of chromium but we have made different ui decisions and different decisions in terms of browser features than chrome and that's something that we think is important and helps drive the ecosystem forward we also work with people through standards and through web developer advocacy in companies that are competitors, i mean, i work with people from apple in the context of web standards, and wcc quite often and choices that they make in safari help to drive the web forward in different areas than the choices that we make in samsung android, the choices that google makes in chrome it's a good example tony morelan 28 23 definitely so what are some of the areas of success for samsung internet? dan appelquist 28 28 so from the beginning, when we started things off in 2016, we, we started off with some ideas around how we were going to treat developer advocacy differently one decision that we took was to ensure that our team is attached to the engineering group that is producing samsung internet and so we have a strong connection to our own engineering team and we work very closely with them and we do joint work and when we've done our own events, for instance, we've had members of our engineering team come over from korea and speak at those events and we have a strong relationship with them and we see ourselves as primarily web developer engineers that are also doing advocacy so that's one element and i think the other thing that we're very keen on is promoting diversity and inclusion in the tech community in general and in the web developer community specifically so for instance, we have a diversity inclusion statement about conference participation many organizations have these now i'm very glad to see that many do we started rs in 2016 when we put that in place, i actually used as a template, a statement that the uk government digital service had come up with which so we were basically using, what they had put in place and adapting it for our needs with reference to their work, obviously, where we will not participate in an event that doesn't have good diversity credentials that isn't doesn't have a code of conduct an enforcement policy, that kind of thing that's why very often, if you attend any of our virtual meetings and meetups, you'll always see me at the beginning talking about the code of conduct and just reinforcing the enforcement procedure for it so we take that very seriously and we also put energy into events and activities that are specifically focused on driving better diversity and inclusion in tech so there's something called global diversity cfp day, which is a yearly event that happens across the world where you were people who are new to speaking on tech conferences can come and get mentorship from people who have more experience speaking in tech conferences about how to submit their proposals for tech conferences, and it's specifically focusing on getting more diverse speakers out there, and driving more diversity and inclusion into the tech conference circuit in general so that's something we participate in and we also sponsor events that are focused on particular on inclusion queer js is a very good example where we were we sponsored that and then we, we sponsored that in berlin and then we were very happy to see that it grew into a bigger thing after that, yeah, that's something that we're putting a lot of energy into and we've seen that come back to us in the form of, i think people really appreciate that anyway, the kind of developers that we want to work with appreciate that and we really appreciate that kind of feedback cycle tony morelan 31 31 that's great so what advice do you have for developers looking to build for samsung internet? dan appelquist 31 36 sure, you can follow us on twitter, first of all, at samsung internet you can also follow us individually i'm at torgo always talking about i'm torgo on twitter, to our geo and i'm always talking about web standards and other web technologies you can go to our developer hub, which is samsung inter dotnet and then links off to all kinds of places like our blog, we actually repost articles from our blog onto samsung into dotnet our blog is on medium so you can follow us on medium at samsung internet dev, you can attend an office hours event so if you go to meetup calm, and you subscribe to our meetup group, so we're running a series of events through that meetup group other than that, the best way to kind of keep tabs on what we're doing is to pay attention to our twitter and we're also by the way posting all of those events on the samsung developer platform on developer samsung com and you can pay attention to our linkedin page, we have a linkedin page, we search for samsung internet, you'll find it on linkedin and we're actually posting all of those blog posts and event notifications and all that kind of stuff there as well trying to engage with that community tony morelan 32 50 that's excellent but hey, dan, i really appreciate you taking the time to sit down and do this podcast with me, you know, yeah, it was a lot of fun to not only learn about you, but also learn about samsung internet dan appelquist 33 00 thank you really appreciate it outro 33 03 looking to start creating for samsung? download the latest tools to code your next app, or get software for designing apps without coding at all sell your apps to the world on the samsung galaxy store check out developer samsung com today and start your journey with samsung the pow! podcast is brought to you by the samsung developer program and produced by tony morelan
announcement web
blogthe web doesn’t have a marketing team. it doesn’t have a single developer program you can sign up to. and it doesn’t have a manual. that’s by design. like the internet, the web isn’t controlled by any single entity. but this decentralisation can also be a pain for web developers and designers. the web has lots of documentation, but it’s often an issue for developers to find documentation that is not written from a perspective of one web product — for example, a browser or a framework. the web needs a place where people can go to get the ground truth. over the last decade, mdn has become that trusted source of information — a place where developers know they can get the documentation they need about how to build for the web. that’s because, even though it’s a project run by mozilla, it documents the web across all browsers. cross-browser compatibility is one of the key pain points of web development, and good documentation is one of the ways we can mitigate that pain. ask any developer where they go first for documentation and they will likely cite mdn. that’s why, in 2017, i jumped at the chance of joining the product advisory board of mdn. i saw it as an opportunity to give back, and also to be a part of a project to reinforce this cross-browser message. by the way, i started my career as a technical writer, so i have opinions on the importance of good technical writing when it comes to the developer experience. the product advisory board was an experiment from mdn to bring in an external advisory group — including members from microsoft, google and w3c. these organisations were all already investing time in building and maintaining mdn. the pab gave them a way to advise on product direction and hear about future planning. open web docs fast forward to 2020. mozilla restructured and mdn took a hit. as a response, the same organisations (and people) who had come together to support mdn via the product advisory board came together again, with others, to launch something called open web docs. open web docs is a new open source project, set up to help support and maintain documentation on the web — via mdn. in practice, this means that open web docs will be paying writers to help write documentation and build the tools that are required to produce high-quality web documentation (for example, to maintain browser compatibility data), in collaboration with mozilla. open web docs will help to ensure the stability of mdn and will focus the activities of the multiple stakeholders in good web documentation. i’m proud to have been a part of the planning for this effort. i’m also glad that samsung internet will be investing our time and energy, both through our continued participation in the mdn product advisory board and via open web docs, in helping to document the web platform. a beautiful library at trinity college, dublin. photo by alex block on unsplash
Daniel Appelquist
We use cookies to improve your experience on our website and to show you relevant advertising. Manage you settings for our cookies below.
These cookies are essential as they enable you to move around the website. This category cannot be disabled.
These cookies collect information about how you use our website. for example which pages you visit most often. All information these cookies collect is used to improve how the website works.
These cookies allow our website to remember choices you make (such as your user name, language or the region your are in) and tailor the website to provide enhanced features and content for you.
These cookies gather information about your browser habits. They remember that you've visited our website and share this information with other organizations such as advertisers.
You have successfully updated your cookie preferences.