New answers tagged

1

I have found a good way to access navigation drawer and bottom navigation both, addressing both at same time val toolbar: Toolbar = findViewById(R.id.toolbar) setSupportActionBar(toolbar) val drawerLayout: DrawerLayout = findViewById(R.id.drawer_layout) val navView: NavigationView = findViewById(R.id.nav_view) val navBottomView : ...


1

You are not going to get penalized for implementing material on iOS. However, if you are doing it just to keep your product consistent across the two platforms, I would review the reasons behind that. Just like on any other platform, users on iOS are accustomed to specific interactions. Unless the interface brings some unique value to the product, it's ...


0

It is a subjective and business decision whether to use material design on iOS apps or not. Here are some facts supporting it : Material Design, did prove to have a fairly good usability acceptance. There is no reason users don't want it on iOS. There is ample of design documentation, code support made available by Material Design team from Google. It must ...


1

We call this icon "fling" icon...


0

Add a blank section to the bottom of the list, so that the last entry scrolls to and sits above the navigation.


1

This is the Android Vector Drawable top-left arrow. I mirrored ic_call_made from material icons, as suggested by @Stephen C. <vector xmlns:android="http://schemas.android.com/apk/res/android" android:width="24dp" android:height="24dp" android:viewportWidth="24.0" android:viewportHeight="24.0"> <path ...


Top 50 recent answers are included