All Projects → Trendyol → Medusa

Trendyol / Medusa

Android fragment stack controller

Programming Languages

kotlin
9241 projects

Projects that are alternatives of or similar to Medusa

Animatedbottombar
A customizable and easy to use BottomBar navigation view with sleek animations, with support for ViewPager, ViewPager2, NavController, and badges.
Stars: ✭ 797 (+101.77%)
Mutual labels:  navigation, bottombar
Material Bottomnavigation
Bottom Navigation widget component inspired by the Google Material Design Guidelines at https://www.google.com/design/spec/components/bottom-navigation.html
Stars: ✭ 1,375 (+248.1%)
Mutual labels:  navigation, bottombar
Material Bottom Nav
A bottom navigation bar adhering to the Material Design specification.
Stars: ✭ 41 (-89.62%)
Mutual labels:  navigation, tab
Chip Navigation Bar
An android navigation bar widget
Stars: ✭ 491 (+24.3%)
Mutual labels:  navigation, bottombar
Navigator
Android Multi-module navigator, trying to find a way to navigate into a modularized android project
Stars: ✭ 131 (-66.84%)
Mutual labels:  navigation, fragment
Navigationtabbar
Navigation tab bar with colorful interactions.
Stars: ✭ 4,907 (+1142.28%)
Mutual labels:  navigation, tab
Lottiebottomnavbar
A Customisable bottom navbar with Lottie animation
Stars: ✭ 76 (-80.76%)
Mutual labels:  navigation, bottombar
Chromeliketabswitcher
Provides a tab switcher similar to the one, which is used in Google Chrome on Android
Stars: ✭ 1,177 (+197.97%)
Mutual labels:  navigation, tab
Flowr
FlowR is a wrapper class around the Fragment Manager.
Stars: ✭ 123 (-68.86%)
Mutual labels:  navigation, fragment
Nativescript App Templates
Monorepo for NativeScript app templates
Stars: ✭ 108 (-72.66%)
Mutual labels:  navigation, tab
Expandablebottombar
A new way to implement navigation in your app 🏎
Stars: ✭ 467 (+18.23%)
Mutual labels:  navigation, bottombar
React Router Native Stack
A stack navigation component for react-router-native
Stars: ✭ 171 (-56.71%)
Mutual labels:  stack, navigation
Readablebottombar
Yet another material bottom bar library for Android
Stars: ✭ 977 (+147.34%)
Mutual labels:  tab, bottombar
Androidnavigation
A library managing navigation, nested Fragment, StatusBar, Toolbar for Android
Stars: ✭ 636 (+61.01%)
Mutual labels:  navigation, fragment
Fragnav
An Android library for managing multiple stacks of fragments
Stars: ✭ 1,379 (+249.11%)
Mutual labels:  navigation, fragment
Navigationtabstrip
Navigation tab strip with smooth interaction.
Stars: ✭ 2,234 (+465.57%)
Mutual labels:  navigation, tab
Smooth-Navigation
提供流畅的 Jetpack Navigation 转场体验。并解决 GitHub 上 Navigation Add Hide 修改版普遍存在的致命缺陷。
Stars: ✭ 204 (-48.35%)
Mutual labels:  navigation, fragment
Handycontrols
Contains some simple and commonly used WPF controls based on HandyControl
Stars: ✭ 347 (-12.15%)
Mutual labels:  navigation
Docker Stacks
DECK is a powerful and high performant local web development studio unlike any other.
Stars: ✭ 376 (-4.81%)
Mutual labels:  stack
Byr Navi
A Light-Weight and Configurable Navigation Website Framework (for BYR)
Stars: ✭ 349 (-11.65%)
Mutual labels:  navigation

Fragment manager for your Single Activity - Multi Fragment app.

License

Medusa is smart enough to handle fragment attachment/detachment or hiding/showing fragment. No more memory handling. No more fragment stack logic.

Why?

Single activity and Multi Fragment structure is a new trend and reasonable to choose. Most of the popular apps like Instagram, Youtube, Spotify etc. are using Single Activity with bottom bar and controlling multiple fragments in that single activity.

In our Trendyol.com android application, we are also using Single Activity- Multi Fragment UI Structure. Everything seems fine when you decide using Single Activity- Multi Fragment, except fragment stack and controlling them.

It was always hard to manage fragment manager in our application. We are using bottom bar and user have his history in every bottom bar tab. For instance, In Home tab, user can goes 4-5 fragments deep in home tab. And then user switches to the another tab and goes 3-4 fragment in that tab too.

So what happens when user switch back to home fragment? Which fragment should be visible to user? What happens when user starts going back? Which fragments will be visible to user in which order while user is pressing back button? What should happen? Yes this is confusing.

This is why we create Medusa. It is not confusing anymore. Medusa keeps track of fragment history of every tab and you only call start, goBack to navigate your fragments.

Wiki

Check out our wiki!

Setup

allprojects {
    repositories {
	    maven { url 'https://jitpack.io' }
    }
}
dependencies {
    implementation 'com.github.trendyol:medusa:0.9.2'
}

Icon Credits

All credits goes to Tatiana

License

Copyright 2018-2019 Trendyol.com

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.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].