smartthings integrate your devices, automate interactions, and extend capabilities with connected services. get started get started do more with smartthings smartthings is one of the largest open ecosystems of connected devices, including over a billion galaxy devices and samsung appliances, millions of customers, and an ever increasing number of partners. smartthings provides a cohesive platform for iot devices to interoperate and communicate, enabling smarter living solutions that enrich our world. developers can access a comprehensive set of features, an instant mobile ui, and leverage voice control with bixby and others. documentation learn how to build new and innovative user experiences. community forum share ideas, ask questions, get support, and connect with customers and developers. developer console seamlessly integrate your iot products into the smartthings ecosystem. partner with us connect with hundreds of brands and thousands of devices. inviting you to an ecosystem of smarter living solutions the smartthings platform connects with the largest coverage of samsung and partner devices available. check out the current list of compatible brands and explore possible integrations. discover brands & devices get your devices ready for matter we truly believe that matter is the foundation and future of iot. we are thrilled that samsung smartthings will be accelerating smart home adoption and bringing users more convenient connected home experiences wherever they are. - michelle mindala-freeman, head of marketing , connectivity standards alliance. learn more explore the ecosystem local control with smartthings edge smartthings edge allows wifi, zigbee, and z-wave device manufacturers to automate and control smart homes devices faster than ever. mobile connected devices integrate your bluetooth devices with over 100m smartthings find nodes and help your customers locate their devices offline. cloud connected devices managing your own cloud? smartthings schema is the easiest method of integrating your cloud connected devices. smartthings cloud integrations use the smartthings cloud as the backend for your mqtt projects. connected services link your apps and services with millions of smartthings users. we have multiple options, depending on what platform you are looking to use. get your device certified works with smartthings certification offers professional, comprehensive testing for your product. smartthings community get help, learn, and share experiences using smartthings. join our community to connect with customers and developers. finding resources on writing for the new platform writing smartapps finding the official tutorials on edge topics writing edge drivers faq: getting started with the new rules api rules api custom capability and cli developer preview tutorials latest blog posts go to blog find in-depth technical content written by smartthings developers.

discover and create with samsung developers using our tools and services, you can provide an exceptional experience to samsungusers around the world new emulator skins for tab s9 get the latest emulator skins for galaxy tab s9 devices. download now! remote test lab for tv use the remote test lab service for tv to test and verify your tizen tv app on a real device. add to samsung wallet learn how to integrate the 'add to samsung wallet' functionality into your services. latest blog go to blog find in-depth technical content written by samsung developers {{pagetype}} {{pagecategorydisplay}} {{title}} {{shortdesc}} {{authorname}} explore more learn code lab code lab is an education platform that engages anyone to understand, through a series of topics, all sdks and tools powered by samsung. learn more > test remote test lab don’t have a samsung device to test your app? no problem! test your apps on the latest samsung galaxy devices in our remote test lab. learn more > distribute galaxy store are you a first timer? haven’t built an app for a samsung device yet? no problem. find everything you need to create your apps, products, and solutions. learn more > support developer support need developer technical support? login with your samsung account to submit a support request ticket and our team will respond within 1 business day. learn more > featured videos go to youtube video video oct 7, 2023 sdc23 highlight open up the world of samsung developer conference 2023 (sdc23) all over again. discover the future of innovation. oct 7, 2023 video video mar 21, 2023 quick and easy: using a galaxy emulator skin watch this youtube shorts to quickly learn how to make your android virtual device look like a galaxy device using the galaxy emulator skin. mar 21, 2023 video video oct 12, 2022 watch face studio with dark mode create a beautiful watch face that is refined and provides a more comfortable viewing experience in low-light situations. oct 12, 2022 newsletter monthly newsletter for samsung developers if you don't currently receive the newsletter, you can subscribe here. i agree that samsung developers may use the data given by me for the newsletter. detail subscribe

samsung dex is a new way to launch your android application in a desktop like environment. upon opening samsung dex mode, every app that stayed open in phone mode, undergo certain changes before launching in samsung dex. in this blog i will be telling you what exactly happens when we switch mode from phone mode to samsung dex mode or vice versa. switching between phone and samsung dex mode. by default, applications are automatically killed when they switch between mobile mode to samsung dex mode or vice versa. you can assume that behaviour is like pressing the home button. when user moves from phone mode to samsung dex mode, then all the opened application will move to taskbar. once you click application from taskbar, it will launch again. before kill process, the status of application is changed to "stopped". after complete switching, shortcuts on taskbar has only tasks (application) information and when we select shortcut, application would be newly created. now the question comes how to prevent application from killing during mode switch i.e. phone to dex or vice versa? to prevent killing process, application could use "keepalive" declaration. declare the keepalive attribute to true in your manifest file like below: <meta-data android:name="com.samsung.android.keepalive.density" android:value="true" /> in case of application declaring "keepalive", application would be not killed on switching after application’s status changing to "stopped". but, if the application does not add the android:configchanges flag to the activity's manifest, application would be destroyed and recreated like the case of resizing the window. during mode switch, screen size i.e. screen width, screen height, and screen layout, smallest screen size, screen orientation, ui mode, density are changed. to prevent applications from recreating after switching the mode, android:configchanges flag to the activity's manifest is required. we need to add the following configuration changes in manifest file for your activity. <activity android:configchanges="orientation | screensize | screenlayout | smallestscreensize | uimode | density"> so, if we declare both keepalive and android:configchanges flag to the activity's manifest then there will be no killing of the application. in this case when we re-launch app via shortcut in taskbar, the functions are invoked according to the following sequence. onconfigurationchanged(), onrestart(), onstart(), onresume() callbacks are sequentially called. for more information about how the android life cycle works in samsung dex mode, you can refer to: android life cycle blog here.

marketing and monetization are a key part to every developer’s journey. we're created a set of resources to help you succeed when it’s time to start promoting your new apps, games, themes, and watch faces. the blog posts, articles and guides, videos, and downloadable content provide easy-to-follow instructions and access to powerful promotional tools that aid you in achieving your desired goals. get tips for executing social promotions, managing your brand on the seller portal, and using galaxy store badges.

we at samsung internet care a lot about progressive web apps (pwas), this is why we decided to feature some awesome pwas that we found online. firstly, what are pwas? progressive web app (pwa) is a concept created by frances berriman and alex russel to describe apps taking advantage of new features supported by modern browsers that are built using including html, css, and javascript (yes, just web technologies ❤). this is the introduction to laura’s blog post. i recommend reading her blog post if you are interrested in making a pwa: progressive web apps: making app-like experiences in the browser context i discovered make me cocktail, thanks to dan (the director of web advocacy at samsung internet) during a conversation about pwas that he was using. i found the web app particularly useful, especially the “my bar” feature which is just doing the job and making it easier to find nice recipes using only what we have at home. also, very convenient for noobs like me. we thought why not reach out, learn more about why they choose to develop a pwa for their platform and write a blog post about it! make me a cocktail an interview with nick wilkins from make me a cocktail make me a cocktail was founded in 2010, by nick, with the goal of becoming the best online platform related to cocktail and drink recipes. all of this started because nick became annoyed of browsing the web trying to find a decent cocktail recipes, and so he decided to create his own platform! since then the platform evolved and became more popular with more functionalities and design improvements. why did you decide to make the website a pwa? we originally floated the idea of making the site a pwa when we were investing in a small rewrite of some core underlying structures on the site, and seeing what new technologies had emerged and were emerging in the dev world. at this time we were also investing heavily in performance and trying to understand how we could make our fairly image- and dynamic- rich site, fast and performant for all our users. we were also really keen to explore the possibilities or porting our site over to an app — and this seemed like a great emerging option for this. did you encounter any technical challenges during the process? we decided early on to not make our site a pure fully-works-offline pwa, but to utilise all of the technologies and opportunities a pwa gives you to give the best experience to the user. obviously the service worker was a large part of this, and that was the core technical challenge we encountered. good documentation and tutorials were sparse when we first started to utilise it. browser dev tools weren’t quite as slick for service workers as they are now, so the core hurdles were dealing with understanding the service worker lifecycle and how to test new ones efficiently and cleanly. our knowledge of dev tools and the network pane specifically, really increased here. how did the pwa help you, and how did you utilise the service worker power? ultimately the pwa has helped us in two areas. one is speed and performance. the service worker caching mechanisms and thus serving up assets quickly to users is just a win-win situation. but, we also like to think, and this is a little less tangible, that we’ve given users more accessibility and a better user-experience / option to find data quicker. things like the manifest, the add to home screen options and the like have helped create quicker avenues to data for the end-user. thoughts it really is fairly easy now to create a base pwa without offline capability. depending on your app size and complexity, and your stack, adding full or partial offline capability can be harder and more of a technical challenge. dynamic user based data that you can’t cache upfront (or can’t cache up to date data) comes at a price if you want to go down that route, and it's important to explore all those avenues. there are little cons to implementing the base pwa experience, the cons really come with time and knowledge that you may need to invest. but ultimately it is all worth it. conclusion as said by nick above, creating pwas is the way to give better experiences to users. this is why at samsung internet, we do care a lot about pwas, and we are currently seeking for pwas with good user experience to share with the community or even write about! please contact us by email browser@samsung.com or twitter if you are working on a pwa or know a good pwa ! thank you, kevin (@kevinpicchi, picchi.ch)

previously, in order to use custom fonts in existing xamarin.forms applications, you had to add the font asset in each platform project and use the fontfamily property to apply the fonts. this was very cumbersome, because each platform required a different syntax for referencing a font file. as we introduced in a previous blog post, using custom fonts in your tizen .net applications was not so simple, either. xamarin.forms 4.5.0 introduced a new uniform way to specify custom fonts across platforms. you could define custom fonts on each platform and reuse them by including them as application resources, which was a feature available in xamarin.forms 4.5.0 pre release 1. we've added tizen support to this feature, so you don't need to write code to use custom fonts. note: this change is effective as of xamarin.forms 4.5.0 pre release 2 and higher. this blog explains how to use custom embedded fonts in xamarin.forms tizen applications. add the font file to your project in visual studio to add fonts as resources, perform the following steps in the visual studio. 1. create a folder to store the font files to create a folder for storing the font files, right-click the project folder and select add > new folder. let's call it resource. 2. add a font file to your project to add a font file to your project, right-click the resource folder you just created and go to add > existing item..., or drag the file from file explore (on windows) or finder (on mac) and drop it into the resource folder. you can add truetype font (.ttf) and opentype font (.otf) files. you can obtain sample font files here. note: be sure to add the font file with build action: embeddedresources. otherwise, the font file will not be distributed as part of your app. in addition, you should register the font file with the assembly, in a file such as assemblyinfo.cs, using the exportfont attribute as follows: using xamarin.forms; [assembly: exportfont("cutefont-regular.ttf")] [assembly: exportfont("ptm55ft.ttf")] [assembly: exportfont("dokdo-regular.ttf")] [assembly: exportfont("fa-regular-400.ttf")] after you add the font file to your project as a resource, you can begin assigning the font to visualelement items that have the fontfamily property, such as label, entry, and so on. font name can be specified in xaml or in c# code. as mentioned, you no longer need to know platform-specific rules for specifying fontfamily attributes. it works whether you use the full path and font name separated by a hash (#) as the font name (as in android) or just the font name (as in ios). note: the font file name and font name may be different. to discover the font name on windows, right-click the .ttf file and select preview. you can then determine the font name from the preview window. use your custom font in xaml <label text="custom font 한글" /> <!-- custom fonts --> <label text="custom font 한글" fontfamily ="cutefont-regular" /> <label text="custom font 한글" fontfamily ="dokdo-regular" /> <label text="custom font 한글" fontfamily ="ptm55ft.ttf#ptmono-regular" /> <label text="custom font 한글" fontfamily ="fa-regular-400.ttf#fontawesome5free-regular" /> <!-- system fonts --> <label text="custom font 한글" fontfamily ="breezesans-thin" /> <label text="custom font 한글" fontfamily ="breezesans-bold" /> use your custom font in c# new label { text = "custom font 한글", }; // custom fonts new label { text = "custom font 한글", fontfamily = "cutefont-regular" }; new label { text = "custom font 한글", fontfamily = "dokdo-regular" }; new label { text = "custom font 한글", fontfamily = "ptm55ft.ttf#ptmono-regular" }; new label { text = "custom font 한글", fontfamily = "fa-regular-400.ttf#fontawesome5free-regular" }; //system fonts new label { text = "custom font 한글", fontfamily = "breezesans-thin" }; new label { text = "custom font 한글", fontfamily = "breezesans-bold" }; all the examples above are also found here. screenshot now that you've reviewed the simple steps in this blog, check out the sample font files, see the many truetype and opentype fonts that are out there, and try custom fonts in your own xamarin.forms tizen applications.

this blog is the third in a series of posts about remote test lab. in previous blogs, we covered what is remote test lab and its new features. next, we are going to take a deep dive into some useful features of remote test lab. the remote test lab service lets you install and test your applications on real devices. in this blog, we are going to install an application and test it on remote test lab devices with auto repeat. auto repeat is a tool that lets you create a test scenario automatically, repeat the same test several times, and reuse the test later. information: the auto repeat feature is supported on a java-based client only. install your application to get started, launch a remote test lab client, then go to remote test lab and reserve one of the available mobile devices. you can install your application on the remote device by dragging and dropping the application package from your computer into the remote test lab client. through the client, you can watch how the application behaves on the device. you can also install applications by going to management > application manager or selecting test > install application in the device context menu. install your application in any of the ways described above. record and play events recording and playing back events is one of the ways to test your applications automatically. when you record events for repeated testing, we recommend that you start and finish recording at the same screen on the remote test lab client. the following figure shows the most commonly used buttons in the auto-repeat window. ① the add button lets you add more actions manually. ② the record button starts recording actions on your device screen. ③ the play button starts playing a test. ④ the stop button stops playing a test. to start recording a test scenario, proceed as follows: click test > auto repeat in the context menu on the remote test lab client. in the auto repeat window, click the record button. once the record button is clicked, all events on the rtl client are recorded. the recorded events are added to the event list in the auto repeat window. click the stop button when you want to stop recording. the number of events and how long the test took to run appear under the event list. to run the test repeatedly, enter a number into the test repeat field in the test option section. click the play button. monitor the progress of your test in the auto repeat window. you can check the completion progress as well as which step is currently running. click file > save. an xml file is saved to your computer. you can reuse the xml file to test your application on other devices with the same resolution. the following video shows each step of recording events and playing back the test procedure. create test sequences manually you can also create a test scenario by adding events manually. this method can be more complicated but it lets you insert a wide variety of events to your scenario. to add an event to your test scenario, proceed as follows: click the add button in the auto repeat window. select a desired event. the selected event is added to the event list section. fill in the related information in the event properties section. every event has its own properties. properties you do not need to fill in are marked with n/a in the event list section. if a mandatory property is missing, the test isn't performed. click the play button. the following video shows each step of adding events manually. you can create complete test scenarios by recording events or manually add more events to make the test scenarios more sophisticated. remote test lab article series get started with remote test lab for mobile app testing what's new in remote test lab run and test applications with remote debug bridge in android studio (coming soon) web-based client preview (coming soon) go to remote test lab

watch face studio (wfs) is an intuitive graphical tool that provides designers a means to design watch faces for the wear os smartwatch ecosystem without the need for coding. basic information on a watch face is typically presented as text, and watch face studio enables you to customize how the text is displayed. this article introduces three features you can use to enhance the text on your watch face design: tag expressions curved text bitmap fonts you can follow along with the demonstrations in this blog by downloading the sample project. tag expressions tag expressions enable you to create watch face components for which the rotation, placement, and opacity changes based on tag values. the tag values represent watch data, such as the date and time, battery status, sensor and health data, moon phase, and mathematical operations. for example, you can create a watch face that shows the date and time, and a progress bar that fills up each minute. this section describes how to implement this using tag expressions. to implement the dynamic watch face: create a text component. in the "properties" panel, select the text field text box. select the tags button that appears. figure 1: tags button to add the hour text, from the tag list, select [hour_0_11], then select done. figure 2: tags list similarly, to add the minutes text, create a text component with the [min] tag. to implement the progress bar for the seconds display: a. create a progress bar component. b. define its value as the [sec] tag and set its maximum value to 60. create text components for the date-related elements: [day_week_f] (day of the week), [mon_f] (name of the month), and [day_1_31_z] (day of the month). note : you can also display the weekday and month information as numbers, by using different tags. keep in mind that in watch face studio, sunday is the first day of the week. the following figure shows the progress bar on the watch face after some visual adjustments. figure 3: seconds progress bar on watch face for more examples of tag expression implementation, see the tag expressions code lab for watch face studio. curved text you can place text around a curve by selecting from predefined angular ranges, or by defining a specific start position and distance. you can also easily set the text direction. to place curved text around the top of the watch face: create a text component and define the text you want to display. in the "properties" panel, select apply curved-text. select ok. the curved text settings appear. in the "curving" fields, define the width and height of the circle or oval around which the text is to be placed. the width and height values are in pixels. for this demonstration, set both the width and height to 436. to place the text around the top of the watch face, in the "range" section, select the upper half circle. figure 4: configuring the curved text the following figure shows the curved text on the watch face after some visual adjustments. figure 5: curved text on a watch face note : you can also implement curved text on complications. bitmap font bitmap fonts enable you to replace information on the watch face, such as digits, symbols, and day of the week, with customized images. use different icons and images in the bitmap font to make your watch face more interesting. to implement icons for the am/pm tag: create a text component. in the "properties" panel, select the text field text box. select [ampm] from the tags list, and select done. figure 6: am/pm tag in the "text appearance" section, select bitmap font. open the "bitmap font setting" dialog. figure 7: bitmap font configuration in the "bitmap font setting" dialog, select the other tab. to add an image for a specific string, select + and browse to the image on your computer. do this for both the "am" and "pm" strings. to close the dialog, select ok. figure 8: adding a bitmap font image the watch face displays the selected images in place of the "am" and "pm" text strings. a watch face can have multiple bitmap fonts. you can add another bitmap font from the dropdown menu and apply different bitmap fonts to different text elements. figure 9: creating another bitmap font note : the sample project contains two bitmap fonts. conclusion watch face studio provides various text options for the watch face. the text customization features described in this blog can help you create an eye-catching watch face. resources for more information about watch face studio, see the watch face studio documentation. you can also visit the samsung developers forums, an active and friendly community where you can ask for and receive help with your application development. the samsung developers site has many resources for developers looking to build for and integrate with samsung devices and services. stay in touch with the latest news by creating a free account and subscribing to our monthly newsletter. visit the marketing resources page for information on promoting and distributing your android apps. to learn more about customizing your watch face, see also the design complications using watch face studio blog.

the key to successful marketing is building your brand and creating a loyal customer base that returns to your store to purchase again. you want consumers to recognize your brand, trust the quality, and anticipate new releases. building your brand takes time and effort. from designing compelling consumer marketing assets to expanding your customer reach, in this blog series, i offer suggestions to help grow your customer base and ultimately reach your marketing goals. selling your apps success is generally measured by sales, and knowing how to price your apps can drastically help your revenue. free vs paid offering free apps is a great way to create brand awareness on galaxy store. consumers get to see your style and experience the quality of your apps without purchasing. however, if you intend to generate revenue, you should limit the availability of free apps. at any given time, i would suggest only having one or two apps available for free. these could be "legacy" apps that have been on the market for an extended amount of time. or, a free app offered for a limited amount of time as part of a marketing campaign. what i would not do, though, is flood the market with freebies. consumers will grow accustomed to receiving your apps for free and content knowing that they simply do not have to pay for your products. try and buy a great way to promote your app is to offer a free trial. once the trial has expired, users are allowed to purchase and continue using the app. for theme designers, apps are set by default to be offered on a trial basis. once 15 minutes have elapsed, users are allowed to pay for the theme. if not, the theme will return to the default ui. for watch face designers, trials can be set within galaxy watch studio. developers are given the ability to set a trial period from 1 minute to 999 days. you can learn how to add the try & buy feature to your watch face designs by reading the blog, "galaxy watch face: try and buy". price there is no magic price to sell your app. simple apps may be priced cheaper than more complex apps. popular apps may cost more than lesser-known apps. newer apps could command a higher price than older apps. however, all apps have value and it is up to you to determine what value your apps have. a few suggestions would be: don't offer .99 apps. this amount conveys "cheap", both in price and in quality. price "new releases" higher, then reduce the price after a certain amount of time. offer different price ranges to see which sell best. marketing info and resources additional reads: strategies for success look for new releases of my blog series, strategies for success, where i continue to deep-dive into the many areas that can influence your market growth. additional topics to include: brand names building your fan base consumer trends selling your apps (this post) samsung galaxy store: tips for marketing your apps check out my video, samsung galaxy store: tips for marketing your apps to learn more about creating brands, designing marketing graphics, social media tips, badges, and banner promotions. marketing resources looking for even more info about promoting your apps? our marketing resources page contains helpful information on promoting your apps. you can view lists of relevant hashtags to use on social media, learn more about discounts and coupons, as well as download guidelines and kits to help you get started. developer forums post questions, search for answers, or just see what are the latest topics for discussion. visiting our developer forum is an excellent way to stay up-to-date on all things related to the galaxy ecosystem. to see the latest marketing topics, be sure to view the marketing thread.

foldable technology for mobile is a groundbreaking experience not only for users but also for developers. the presence of many form factors like immersive display, app continuity, flex mode and ux optimization challenge developers to think outside of the box to adapt to this technology. in this blog, we discuss a checklist to provide a better understanding about the adaptation, modification and design changes that are required. so, let's go through each point, one-by-one. large screen optimization samsung foldable devices have two different physical screens: the cover display and the main display. as the cover display is much smaller than the main display, large screen optimization is one of the key areas of designing ux for foldable devices. in a nutshell, your app can utilize the extra space in the main display by showing more information. just having a different ui design with the same information can do the trick of optimization as well. large screen optimization of a note app to implement this scenario, define different layout files for each display using the alternate resources option. for example, if you want to define a different ui for the main display, create a new directory named layout-sw600dp under the res directory and then create an xml file named activity_main. then add the layout code as required. ui is designed separately for the main display and the cover display flex mode optimization in galaxy z series devices, samsung introduced a new mode called flex mode. this mode allows users to use apps while the book-like phone is partially folded. creative design can really make your app stand out from others in flex mode. google duo app in flex mode in galaxy z series devices using google’s new jetpack library, windowmanager, you can detect the current posture of a galaxy z series device and update the ui accordingly by following these steps: step 1: add the dependencies in the build.gradle. implementation "androidx.window:window:1.0.0-alpha01" step 2: define a windowmanager instance. val windowmanager = windowmanager(this, null) step 3: register the devicestate change listener. the listener notices changes in the device state (for example closed, opened, half_opened). windowmanager.registerdevicestatechangecallback( mainthreadexecutor /* executor */, callback /* consumer<devicestate> */ ) step 4: write a callback function to check devicestate.posture to get the current posture of the device. if the posture is posture_half_opened, the app ui gets updated for flex mode. val callback = consumer<devicestate> { devicestate -> if (devicestate.posture == devicestate.posture_half_opened) { // display is folded, show split ux } else { // display is not folded, show full screen ux } } check out the codelab challenge on flex mode for a more hands-on experience. app continuity while folding and unfolding the device, the app must prevent data loss thus ensuring its continuity. this is achievable by using the onsaveinstancestate() method. first, save the data to retain the current state with onsaveinstancestate(). @override public void onsaveinstancestate(bundle savedinstancestate) { //save the current state } then, restore the data in the oncreate() function. @override protected void oncreate(bundle savedinstancestate) { if (savedinstancestate != null) { //restore the previous state } } stopwatch app continuity while unfolding device to have a better understanding of implementing app continuity, see the codelab challenge on app continuity. responsive ui layout to adapt to new form factors such as a diverse aspect ratio, flex mode, multi-window, and pop-up window, utilize the following guidelines : design a responsive ui layout for your app using constraintlayout. define the activity of your app as resizable, to ensure the maximum compatibility of your app with both the cover display and the main display of the device. set the resizableactivity attribute to true in manifest.xml. <activity android:name=".mainactivity" android:resizeableactivity="true"> … </activity> responsive layout of the spotify app cutout and punch hole of the main display the main display of a galaxy z fold is covered by an area on the top-right side called the “l-cut” whereas the galaxy z fold2 and fold3 have a punch hole in the upper right side and the galaxy z flip devices have a punch hole in the middle. some portion of your app’s ui could be covered by the l-cut or the punch hole. content is covered by the l-cut in a galaxy fold device in landscape mode to avoid such a scenario, depending on your ui content style, define a display cutout mode. for example, the content is letterboxed in landscape mode whereas it is rendered into the cutout area in portrait mode by default. define the display cutout mode in the style.xml as shortedges so that your content is rendered into the cutout area in both portrait and landscape modes. <item name="android:windowlayoutindisplaycutoutmode">shortedges</item> display cutout in the default mode and the shortedges mode, respectively last but not the least, you can test your app on our device cloud, samsung remote test lab, to make sure you have implemented all the checkpoints discussed in this blog. you can also participate in our codelab challenges to have a clear understanding of the implementation details. in this blog we have discussed about how to adapt your app for foldable devices. we hope it is a good guide for you to start with. you can also check out samsung’s official documentation and reach out to our developer community if you have any queries.