I want a transition between my splashscreen and my "home" activity.
The splashscreen consists in two images (the same image with mirror effect). The upper image translate to the top, the lower one translate to the bottom. The home is appearing behind.
It's like a curtain which is opening.
I don't find a solution to have two separate activities for this animation.
If I make only one activity, the problem is that the "home" has an actionbar whereas the splashscreen doesn't have one.
Do you see a solution?
Related
I'm developing an app for Wear OS.
It has 2 screens, both extending from AppCompatActivity, both havingandroid.support.wear.widget.BoxInsetLayout as the root of their layouts.
From the first one i can navigate to the second one and in the second screen use left-right swipe to navigate back without problems, i didn't need to do anything for this to work.
For the first screen the same left-right swipe is not doing anything, and i can't understand why, as the documentation says:
An activity automatically supports swipe-to-dismiss. Swiping an activity from left to right results in dismissal of the activity, and the app navigates down the back stack.
Witch makes sense after seeing the default behaviour of my 2nd screen.
I've tried to put a SwipeDismissFrameLayout as the root element of that screen, that make the swipe work, but, instead of showing the watch face that is below, it's showing a gray screen and it's also not finishing the activity (unless i explicitly do it implementing the callback)
From what i can understand in the docs this should be working without having to do anything, but for some reason it's not...
Both activities have the same style and same layout root element.
Is there something i'm missing to make this work?
Not sure how to explain this better, but it's mostly implemented by chat applications for Gallery picker fragments and alike. Best example is Google Allo, for which I posted GIF below. I'd like to know how is that implemented and how I could replicate the feature.
As you can see, the map fragment first transition animates from bottom to half of the screen, but then it can be dragged by finger to the top of the screen, when it actually fills the whole screen and even creates it's own toolbar. Most of all, I tested it, and this also works on API 16.
I have fitted my app with a NavDrawer following the Android Material Design spec.
But initially the idea I had for my App's Navigation Drawer was different, I would like to maintain that design, but I need advice with the approach.
I have uploaded an image of what I would like to achieve.
http://i.stack.imgur.com/uzRBe.jpg
The user can click on button 2 and due to the nature of button 2, only that portion of the NavDrawer will slide out, or the user can slide the drawer out manually using a finger, and the drawer slides out and snaps to the edge of the screen just like the Android notification menu that u can slide from the top of your device.
Clicking on button four will slide the entire Group of buttons (due to the nature of content on button 4), button two would remain on the right if it were already there to start with.
Button 1 which would be the home button would check that all other buttons are in place (to the left) otherwise it draws them in then loads the home content into the main view.
I am not sure which way to approach this, using the Material Spec NavDrawer, or I custom design multiple linear layouts that follow the user's Xposition gestures.
Currently, I have a Material Spec NavDrawer, so the code is standard
Better to use the default Android Drawer Actvitity that comes with Android studio 2.0 and modify it.
it will save you allot of bugs
if you still want to create a cosutm one
you can either use what was suggested here >
http://simonvt.github.io/android-menudrawer/
or you can just choose one from this site >
https://android-arsenal.com/search?q=Drawer
it has some open library drawer helpers to help you write one.
i woul'd suggest against writing everything from scrach, it looks like allot of works and introduce allot of bugs, as to what needs to be on top of what every time, that you can fix by either using a library or taking the default one.
I have big background image, I want use it for two activity, like my image when the button pressed, I want to slowly moving activity 2 from left to right the background look like moving from left to right, like android home screen when you swipe your screen, what I need to do ?
You should use fragments instead of activities.
In this way you can have a single activity with the fixed background and two fragments with transparent background.
I have a source code to do (Slider menu)..
But I want to do like it to just open a specific content, meaning that I want the second content to appear over the current content from right to left by pressing a button.
Hint: I'm not want to open activity totally by
overridePendingTransition(R.anim.animation, R.anim.animation2);
I just want the second content opens over the current content like what sliding menu acts.
(sliding menu appears from left to right by moving my finger from left to right, I want my second content opens from right to left and appears partially by pressing a button and back to hide my passing my fingers over it and move from left to right)
example: https://play.google.com/store/apps/details?id=com.wunderkinder.wunderlistandroid
Sorry if I could not explain, and hope anyone got my mean.
I think you got the "Activity" concept wrong.
I understand, you can never show 2 activities at the same time. An activity is not a "screen", "view" or something like that... it is a context itself. It covers a whole state in your application. If you want to do something like a slider, you can play with views, animations or even better, fragments.