Such a question, I have a project that is NOT executed on fragments and in which I want to implement a navigation drawer , do I have to redo the whole project into fragments to make the navigation drawer work correctly for navigation drawer ?

Since I heard that if you implement a navigation drawer without fragments, it will slow down when opened and work incorrectly.

But I tried to create several actions with the navigation drawer "out of the box, so to say," when creating, the studio itself offers this feature, and I normally switch between them and everything works.

Who understands tell me whether everything will work correctly if you execute a navigation drawer without fragments and in general how much is it connected?

    1 answer 1

    All this has nothing to do. Nothing prevents you from making a few activites and from activating to launch activations instead of changing fragments.

    Perhaps, under the decrease in speed, they had in mind only that changing a fragment is faster than changing an activation.

    • OK understood. But why in almost all examples such manipulations are made using fragments? - Aleksey Timoshchenko
    • @AlekseyTimoshchenko, well, I think, because usually on fragments they display similar information and there is no point in activating them. But it is more logical to make any settings for the thread and / or launching the camera in another activity, because This, usually, is weak to the infe with the main activity. Type is divided by type of content / action. - Yuriy SPb ♦