Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/SaadAhmed1122/Kids_learnig_App/llms.txt

Use this file to discover all available pages before exploring further.

The mode selection screen (Select_act) is the first truly interactive screen a child encounters after the splash sequence completes. Presented in landscape orientation with the same immersive fullscreen treatment as the splash, it offers exactly two choices: enter the Learning Hub to explore quiz categories, puzzles, and a gallery, or jump straight into the Game Hub for HTML5-powered play. Both options are represented by large, tappable image views that animate in on arrival, making the decision tactile and visually clear.

​
Modes at a Glance

Learning Hub

Tapping the Learning image view launches FinalmainScreen, which hosts seven quiz categories, a puzzle activity, and an image gallery. This is the educational core of the app.

Game Hub

Tapping the Game image view launches GameMainAct, which serves a curated collection of HTML5 games inside a WebView-based game hub designed for young players.

​
How the Screen Works

When Select_act is created, both image views — R.id.learningimgview and R.id.gameimageview — are loaded from the activity_select layout and immediately receive a zoom3 animation so they pop onto the screen with a playful scale-in effect. Click listeners are then attached to each view to handle navigation. 
learning.setOnClickListener(new View.OnClickListener() {
    @Override
    public void onClick(View view) {
        startActivity(new Intent(Select_act.this, FinalmainScreen.class));
    }
});
game.setOnClickListener(new View.OnClickListener() {
    @Override
    public void onClick(View view) {
        startActivity(new Intent(Select_act.this, GameMainAct.class));
    }
});
Neither click handler calls finish(), so the mode selection screen remains on the back stack. A child can press Back from either destination to return here and switch modes without restarting the app.

​
Immersive Fullscreen

Select_act applies the same hideSystemUI() / showSystemUI() immersive fullscreen pattern used on the splash screen.
The system bars are hidden by default via hideSystemUI() in onCreate. If the user swipes to reveal the navigation or status bar, showSystemUI() surfaces them temporarily — the activity then re-hides them to keep the interface distraction-free for young users. This pattern is consistent across all primary screens in the app.
When adding new top-level destinations to the app, register a third ImageView in activity_select and follow the same zoom3 + setOnClickListener pattern used for the Learning and Game views to keep the entry point consistent.

Build docs developers (and LLMs) love

Get started for freeTalk to us