Welcome to the OneUI Design Library documentation. In this wiki page, you will find all the infos regarding the library and how to use all its components. Do not mind to contact us in case you need any clarification, we will update the documentation if needed.

Samsung's OneUI apps are created by using an heavily modified version of Google's Jetpack and Material Components libraries, internally named "sesl-appcompat" (Sesl stands for Samsung Experience Software Library; iirc). Those modifications include a different styling of the UI, hover/S Pen support, new features and much more. The intent of this library is to make those Samsung UX elements available to everyone for study, modding or whatever feels right for you. Any form of contribution, suggestions, bug report or feature request will be welcome.

In general, most of the views are styled automatically when you apply the theme in AndroidManifest.xml, the usage of the custom views in the library however is needed to achieve the best results. If you're building apps specifically for Samsung devices, also check this out.

• Main: android:theme="@style/OneUITheme"
• Splash: android:theme="@style/OneUISplashTheme"
• About: android:theme="@style/OneUIAboutTheme"

• Main: android:theme="@style/OneUI3Theme"
• Splash: android:theme="@style/OneUI3SplashTheme"
• About: android:theme="@style/OneUI3AboutTheme"

To change the theme color (statically and/or dynamically) see ThemeUtil.

• ToolbarLayout
• DrawerLayout
• SwitchBarLayout
• SplashView
• AboutPage
• Preferences

• NestedScrollView
• RecyclerView
• SwipeRefreshLayout
• ViewPager
• ViewPager2
• SwitchBar
• TabLayout

• Button
• Switch
• ProgressBar
• SeekBar
• RelatedCard
• Round-Layouts
• OptionButton
• OptionGroup

• AlertDialog
• ProgressDialog
• ColorPickerDialog
• PopupMenu
• Snackbar
• Spinner
• Tooltip
• TipPopup

• OnSingleClickListener
• ThemeUtil
• Icons
• AppIcon

For further customization or if you need something which isn't implemented in the custom views yet (I can't think of all possible uses), you can always access the views inside it with findViewById(int id) and change them directly. For the Ids please refer to the source code.

If you encounter problems with Proguard (missing classes), see this Issue by AlirezaIvaz.

Some custom views might not render in the preview, because this library is using a font (sec-roboto-light), which Android Studio (and other IDEs probably too) don't know. To temporarily bypass this problem you can simply add

<string name="sesl_font_family_regular">sans-serif</string>

to your strings.xml. But don't forget to remove it afterwards for your release. Thanks to roynatech2544, for reporting this issue.

Even if the library is complete, there are still some UI elements that are enforced in system frameworks. If your app is intended for Samsung devices, we suggest you to enable them manually:

1. AndroidManifest.xml flag (apply it under the application tag):

<application>
    <meta-data android:name="SamsungBasicInteraction" android:value="SEP10"/>
    ...
</application>

This will style:

• Dialogs (Gravity.BOTTOM, already set in library)
• android.widget.Switch (OneUI styled)
• android.view.View (Vertical padding in Scrollbar)
• DecorView (Bottom rounded corners for every activity)

2. DeviceDefault theme: To enable this you need to manually decompile your app with apktool; in the following files:

res/values/styles.xml
res/values-v25/styles.xml

Replace the parent Theme.Material theme in Platform.V21.AppCompat and Platform.V25.AppCompat with Theme.DeviceDefault.

This will style android.* views but also enable:

• OneUI EdgeEffect style
• PopupWindow clipToOutline (already set in library)
• OneUI EditText Action mode