Convert Figma logo to code with AI

jfeinstein10 logoSlidingMenu

An Android library that allows you to easily create applications with slide-in menus. You may use it in your Android apps provided that you cite this project and include the license in your app. Thanks!

11,079
5,045
11,079
305

Top Related Projects

DrawerLayout-like ViewGroup, where a "drawer" is hidden under the content view, which can be shifted to make the drawer visible.

The flexible, easy to use, all in one drawer library for your Android project. Now brand new with material 2 design.

Side menu with some categories to choose.

swipe display drawer with flowing & bouncing effects.

This library provides a simple way to add a draggable sliding up panel (popularized by Google Music and Google Maps) to your Android application. Brought to you by Umano.

Quick Overview

SlidingMenu is an Android library that allows developers to easily create applications with sliding menus like those made popular in the Google+, YouTube, and Facebook apps. It provides a customizable sliding menu that can be attached to the left or right side of the activity.

Pros

  • Easy to implement and integrate into existing Android projects
  • Highly customizable with various configuration options
  • Smooth animations and gestures for a polished user experience
  • Compatible with ActionBarSherlock for older Android versions

Cons

  • No longer actively maintained (last update was in 2014)
  • May not be fully compatible with newer Android versions and Material Design guidelines
  • Limited documentation and examples available
  • Potential performance issues on older devices

Code Examples

  1. Basic implementation of SlidingMenu:
SlidingMenu menu = new SlidingMenu(this);
menu.setMode(SlidingMenu.LEFT);
menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
menu.setShadowWidthRes(R.dimen.shadow_width);
menu.setShadowDrawable(R.drawable.shadow);
menu.setBehindOffsetRes(R.dimen.slidingmenu_offset);
menu.setFadeDegree(0.35f);
menu.attachToActivity(this, SlidingMenu.SLIDING_CONTENT);
menu.setMenu(R.layout.menu_layout);
  1. Toggling the SlidingMenu programmatically:
SlidingMenu menu = getSlidingMenu();
if (menu.isMenuShowing()) {
    menu.showContent();
} else {
    menu.showMenu();
}
  1. Customizing the SlidingMenu appearance:
menu.setBehindWidth(300);
menu.setFadeEnabled(true);
menu.setBehindScrollScale(0.5f);
menu.setSecondaryShadowDrawable(R.drawable.secondary_shadow);

Getting Started

To use SlidingMenu in your Android project:

  1. Add the following to your build.gradle file:
repositories {
    maven { url "https://jitpack.io" }
}

dependencies {
    implementation 'com.github.jfeinstein10:SlidingMenu:master-SNAPSHOT'
}
  1. In your Activity, initialize and configure the SlidingMenu:
public class MainActivity extends Activity {
    private SlidingMenu menu;

    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);

        menu = new SlidingMenu(this);
        menu.setMode(SlidingMenu.LEFT);
        menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
        menu.setFadeDegree(0.35f);
        menu.attachToActivity(this, SlidingMenu.SLIDING_CONTENT);
        menu.setMenu(R.layout.menu_layout);
    }
}

Competitor Comparisons

DrawerLayout-like ViewGroup, where a "drawer" is hidden under the content view, which can be shifted to make the drawer visible.

Pros of SlidingRootNav

  • More recent and actively maintained project
  • Supports RTL layouts out of the box
  • Offers more customization options for the sliding menu

Cons of SlidingRootNav

  • Slightly more complex implementation compared to SlidingMenu
  • May require more setup code for basic functionality

Code Comparison

SlidingMenu:

SlidingMenu menu = new SlidingMenu(this);
menu.setMode(SlidingMenu.LEFT);
menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
menu.setFadeDegree(0.35f);
menu.attachToActivity(this, SlidingMenu.SLIDING_CONTENT);

SlidingRootNav:

new SlidingRootNavBuilder(this)
    .withMenuLayout(R.layout.menu_left_drawer)
    .withDragDistance(140)
    .withRootViewScale(0.7f)
    .withRootViewElevation(10)
    .withRootViewYTranslation(4)
    .inject();

Both libraries provide sliding menu functionality for Android applications. SlidingMenu offers a simpler implementation but is no longer actively maintained. SlidingRootNav, while requiring more setup, provides additional customization options and is actively developed. The choice between the two depends on the specific requirements of your project and the level of customization needed.

The flexible, easy to use, all in one drawer library for your Android project. Now brand new with material 2 design.

Pros of MaterialDrawer

  • More modern and actively maintained, with regular updates and improvements
  • Extensive customization options and Material Design support
  • Better integration with Android's navigation patterns and components

Cons of MaterialDrawer

  • Steeper learning curve due to more complex API and features
  • Potentially higher resource usage and overhead for simpler applications
  • May require more setup and configuration for basic implementations

Code Comparison

SlidingMenu:

SlidingMenu menu = new SlidingMenu(this);
menu.setMode(SlidingMenu.LEFT);
menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
menu.setShadowWidthRes(R.dimen.shadow_width);
menu.setBehindOffsetRes(R.dimen.slidingmenu_offset);

MaterialDrawer:

DrawerBuilder()
    .withActivity(this)
    .withToolbar(toolbar)
    .addDrawerItems(
        PrimaryDrawerItem().withName("Home"),
        SecondaryDrawerItem().withName("Settings")
    )
    .build()

Summary

MaterialDrawer offers a more modern and feature-rich approach to implementing navigation drawers, with better Material Design support and customization options. However, it may be overkill for simpler applications and requires more setup. SlidingMenu provides a simpler, lightweight solution but lacks active maintenance and modern Android integration. The choice between the two depends on project requirements and complexity.

Side menu with some categories to choose.

Pros of Side-Menu.Android

  • More visually appealing with smooth animations and customizable design
  • Lightweight and easy to integrate into existing projects
  • Actively maintained with recent updates and bug fixes

Cons of Side-Menu.Android

  • Limited functionality compared to SlidingMenu's extensive features
  • Less documentation and community support
  • May require more custom code for advanced implementations

Code Comparison

SlidingMenu:

SlidingMenu menu = new SlidingMenu(this);
menu.setMode(SlidingMenu.LEFT);
menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
menu.setShadowWidthRes(R.dimen.shadow_width);
menu.setBehindOffsetRes(R.dimen.slidingmenu_offset);

Side-Menu.Android:

ResideMenu resideMenu = new ResideMenu(this);
resideMenu.setBackground(R.drawable.menu_background);
resideMenu.attachToActivity(this);
resideMenu.addMenuItem(menuItem1, ResideMenu.DIRECTION_LEFT);
resideMenu.addMenuItem(menuItem2, ResideMenu.DIRECTION_RIGHT);

Both libraries offer easy-to-use APIs for implementing sliding menus, but Side-Menu.Android focuses more on visual appeal and simplicity, while SlidingMenu provides more extensive customization options and features.

swipe display drawer with flowing & bouncing effects.

Pros of FlowingDrawer

  • More visually appealing with smooth, flowing animations
  • Supports both left and right drawer positions
  • Customizable menu content and background

Cons of FlowingDrawer

  • Less mature and potentially less stable than SlidingMenu
  • Fewer configuration options and features
  • Limited documentation and community support

Code Comparison

SlidingMenu:

SlidingMenu menu = new SlidingMenu(this);
menu.setMode(SlidingMenu.LEFT);
menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
menu.setShadowWidthRes(R.dimen.shadow_width);
menu.setBehindOffsetRes(R.dimen.slidingmenu_offset);

FlowingDrawer:

mDrawer = (FlowingDrawer) findViewById(R.id.drawerlayout);
mDrawer.setTouchMode(ElasticDrawer.TOUCH_MODE_BEZEL);
mDrawer.setOnDrawerStateChangeListener(new ElasticDrawer.OnDrawerStateChangeListener() {
    @Override
    public void onDrawerStateChange(int oldState, int newState) {
        // Handle state changes
    }
});

Both libraries offer easy-to-use APIs for implementing sliding menus, but FlowingDrawer focuses more on visual appeal, while SlidingMenu provides more configuration options and has been around longer, potentially offering better stability and community support.

This library provides a simple way to add a draggable sliding up panel (popularized by Google Music and Google Maps) to your Android application. Brought to you by Umano.

Pros of AndroidSlidingUpPanel

  • More modern and actively maintained (last update in 2022 vs 2016 for SlidingMenu)
  • Supports vertical sliding panels, which is more common in current app designs
  • Easier integration with modern Android development practices and libraries

Cons of AndroidSlidingUpPanel

  • Limited to vertical sliding panels, while SlidingMenu offers horizontal sliding
  • Less customization options compared to SlidingMenu's extensive feature set
  • Smaller community and fewer resources available due to lower popularity

Code Comparison

AndroidSlidingUpPanel:

mLayout = (SlidingUpPanelLayout) findViewById(R.id.sliding_layout);
mLayout.addPanelSlideListener(new PanelSlideListener() {
    @Override
    public void onPanelSlide(View panel, float slideOffset) {
        // Handle panel slide
    }
});

SlidingMenu:

SlidingMenu menu = new SlidingMenu(this);
menu.setMode(SlidingMenu.LEFT);
menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
menu.setShadowWidthRes(R.dimen.shadow_width);
menu.attachToActivity(this, SlidingMenu.SLIDING_CONTENT);

Both libraries offer relatively simple implementation, but AndroidSlidingUpPanel focuses on vertical sliding, while SlidingMenu provides more options for horizontal sliding and customization.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

SlidingMenu (Play Store Demo)

SlidingMenu is an Open Source Android library that allows developers to easily create applications with sliding menus like those made popular in the Google+, YouTube, and Facebook apps. Feel free to use it all you want in your Android apps provided that you cite this project and include the license in your app.

SlidingMenu is currently used in some awesome Android apps. Here's a list of some of them:

If you are using SlidingMenu in your app and would like to be listed here, please let me know via Twitter!

Here's an older video of the example application in this repository : http://youtu.be/8vNaANLHw-c

Also, you can follow the project on Twitter : @SlidingMenu

Setup

  • In Eclipse, just import the library as an Android library project. Project > Clean to generate the binaries you need, like R.java, etc.
  • Then, just add SlidingMenu as a dependency to your existing project and you're good to go!

Setup with ActionBarSherlock

  • Setup as above.
  • Checkout a clean copy of ActionBarSherlock and import into your Eclipse workspace.
  • Add ActionBarSherlock as a dependency to SlidingMenu
  • Go into the SlidingActivities that you plan on using make them extend Sherlock___Activity instead of ___Activity.

How to Integrate this Library into Your Projects

In order to integrate SlidingMenu into your own projects you can do one of two things.

1. You can wrap your Activities in a SlidingMenu by constructing it programmatically (new SlidingMenu(Context context)) and then calling SlidingMenu.attachToActivity(Activity activity, SlidingMenu.SLIDING_WINDOW | SlidingMenu.SLIDING_CONTENT). SLIDING_WINDOW will include the Title/ActionBar in the content section of the SlidingMenu, while SLIDING_CONTENT does not. You can check it out in the example app AttachExample Activity.

2. You can embed the SlidingMenu at the Activity level by making your Activity extend SlidingActivity.

  • In your Activity's onCreate method, you will have to call setContentView, as usual, and also setBehindContentView, which has the same syntax as setContentView. setBehindContentView will place the view in the "behind" portion of the SlidingMenu. You will have access to the getSlidingMenu method so you can customize the SlidingMenu to your liking.
  • If you want to use another library such as ActionBarSherlock, you can just change the SlidingActivities to extend the SherlockActivities instead of the regular Activities.

3. You can use the SlidingMenu view directly in your xml layouts or programmatically in your Java code.

  • This way, you can treat SlidingMenu as you would any other view type and put it in crazy awesome places like in the rows of a ListView.
  • So. Many. Possibilities.

Simple Example

public class SlidingExample extends Activity {

	@Override
	public void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setTitle(R.string.attach);
		// set the content view
		setContentView(R.layout.content);
		// configure the SlidingMenu
		SlidingMenu menu = new SlidingMenu(this);
        menu.setMode(SlidingMenu.LEFT);
		menu.setTouchModeAbove(SlidingMenu.TOUCHMODE_FULLSCREEN);
		menu.setShadowWidthRes(R.dimen.shadow_width);
		menu.setShadowDrawable(R.drawable.shadow);
		menu.setBehindOffsetRes(R.dimen.slidingmenu_offset);
		menu.setFadeDegree(0.35f);
		menu.attachToActivity(this, SlidingMenu.SLIDING_CONTENT);
		menu.setMenu(R.layout.menu);
	}
    
}

XML Usage

If you decide to use SlidingMenu as a view, you can define it in your xml layouts like this:

<com.jeremyfeinstein.slidingmenu.lib.SlidingMenu
    xmlns:sliding="http://schemas.android.com/apk/res-auto"
    android:id="@+id/slidingmenulayout"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent"
    sliding:viewAbove="@layout/YOUR_ABOVE_VIEW"
    sliding:viewBehind="@layout/YOUR_BEHIND_BEHIND"
    sliding:touchModeAbove="margin|fullscreen"
    sliding:behindOffset="@dimen/YOUR_OFFSET"
    sliding:behindWidth="@dimen/YOUR_WIDTH"
    sliding:behindScrollScale="@dimen/YOUR_SCALE"
    sliding:shadowDrawable="@drawable/YOUR_SHADOW"
    sliding:shadowWidth="@dimen/YOUR_SHADOW_WIDTH"
    sliding:fadeEnabled="true|false"
    sliding:fadeDegree="float"
    sliding:selectorEnabled="true|false"
    sliding:selectorDrawable="@drawable/YOUR_SELECTOR"/>

NOTE : you cannot use both behindOffset and behindWidth. You will get an exception if you try.

  • viewAbove - a reference to the layout that you want to use as the above view of the SlidingMenu
  • viewBehind - a reference to the layout that you want to use as the behind view of the SlidingMenu
  • touchModeAbove - an enum that designates what part of the screen is touchable when the above view is showing. Margin means only the left margin. Fullscreen means the entire screen. Default is margin.
  • behindOffset - a dimension representing the number of pixels that you want the above view to show when the behind view is showing. Default is 0.
  • behindWidth - a dimension representing the width of the behind view. Default is the width of the screen (equivalent to behindOffset = 0).
  • behindScrollScale - a float representing the relationship between the above view scrolling and the behind behind view scrolling. If set to 0.5f, the behind view will scroll 1px for every 2px that the above view scrolls. If set to 1.0f, the behind view will scroll 1px for every 1px that the above view scrolls. And if set to 0.0f, the behind view will never scroll; it will be static. This one is fun to play around with. Default is 0.25f.
  • shadowDrawable - a reference to a drawable to be used as a drop shadow from the above view onto the below view. Default is no shadow for now.
  • shadowWidth - a dimension representing the width of the shadow drawable. Default is 0.
  • fadeEnabled - a boolean representing whether or not the behind view should fade when the SlidingMenu is closing and "un-fade" when opening
  • fadeDegree - a float representing the "amount" of fade. 1.0f would mean fade all the way to black when the SlidingMenu is closed. 0.0f would mean do not fade at all.
  • selectorEnabled - a boolean representing whether or not a selector should be drawn on the left side of the above view showing a selected view on the behind view.
  • selectorDrawable - a reference to a drawable to be used as the selector NOTE : in order to have the selector drawn, you must call SlidingMenu.setSelectedView(View v) with the selected view. Note that this will most likely not work with items in a ListView because of the way that Android recycles item views.

Caveats

  • Your layouts have to be based on a viewgroup, unfortunatly this negates the <merge> optimisations.

Developed By

  • Jeremy Feinstein

License

Copyright 2012-2014 Jeremy Feinstein

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.