https://youtu.be/YhMerfA2D9Y

CODE Propmt: 

Build a Modern Mobile Web Browser with Multi-Profile Support

Project: A fully functional, mobile-first web browser inspired by Google Chrome, with advanced multi-profile management similar to desktop browsers.

1. Core Objective

Build a modern, fast, secure, and feature-rich mobile browser application designed primarily for Android smartphones.

The browser should offer a smooth browsing experience with a clean, premium interface, advanced tab management, and a multi-profile system that works similarly to desktop browser profiles.

This should be a real, functional browser, not just a UI prototype or a website that looks like a browser.

Important: First determine the appropriate technology for building a genuine mobile browser. If the environment supports Android app development, use Android WebView or an equivalent browser engine. If generating a web-based prototype, clearly separate browser simulation from genuine native browser functionality.

2. UI/UX Design

Create a premium, minimal, modern interface inspired by Chrome, Safari, and other popular mobile browsers.

Design requirements:

• Mobile-first responsive layout.
• Clean, modern interface with smooth animations.
• Light mode and dark mode.
• Rounded corners, subtle shadows, and carefully balanced spacing.
• Bottom navigation and thumb-friendly controls.
• Modern icons with consistent styling.
• Smooth transitions between screens.
• No unnecessary buttons or clutter.
• A professional interface suitable for everyday use.

Main Browser Screen

The main screen should include:

Top section:

• Profile avatar button on the top-left.
• Browser logo or application name.
• Tab counter button.
• Three-dot menu button.

Search and address bar:

• A combined search and URL input field.
• Search engine selection.
• Website security indicator (HTTPS lock).
• Reload button.
• Voice search button, if supported.
• Automatic URL detection.
• Search suggestions and browsing history suggestions.

Main content:

• Customizable homepage.
• Search bar.
• Frequently visited websites.
• Custom website shortcuts.
• Recently visited pages.
• Optional news or discovery feed.
• Customizable background or wallpaper.

Bottom navigation:

• Back.
• Forward.
• Home.
• Tabs.
• Menu.

Keep the bottom controls accessible with one hand.

3. Advanced Multi-Profile System

This is one of the most important features.

Implement a desktop-style multi-profile system that allows users to create, manage, and switch between multiple completely separate browser profiles.

Profile Creation

Users should be able to:

• Create unlimited profiles, subject to device resources.
• Set a custom profile name.
• Choose a profile avatar from predefined icons.
• Select a profile color.
• Optionally upload a custom profile image.
• Set a profile-specific homepage.
• Choose a default search engine for each profile.

Example profiles:

• Personal
• Work
• Business
• Study
• Social Media
• Private

Profile Isolation

Each profile must have its own separate:

• Browsing history.
• Bookmarks.
• Open tabs.
• Cookies.
• Website login sessions.
• Saved website permissions.
• Search preferences.
• Homepage settings.
• Download history, where supported.
• Theme preferences.

Critical requirement: Profiles must be genuinely isolated. Switching profiles must not expose another profile's browsing sessions, cookies, or website login credentials.

Use separate browser storage contexts or isolated WebView data directories wherever the selected platform allows it.

Do not implement fake profiles that simply change the avatar while sharing the same browser storage.

Profile Switching

When users tap the profile avatar:

• Open a polished profile switcher.
• Display all existing profiles.
• Highlight the currently active profile.
• Show profile names and avatars.
• Provide a quick-switch option.
• Include an Add Profile button.
• Include a Manage Profiles option.

When switching profiles:

• Preserve the previous profile's open tabs.
• Restore the selected profile's previous browsing session.
• Keep browsing data and settings separate.
• Provide a smooth transition between profiles.

Profile Management

Create a dedicated profile management screen.

Features:

• Add profile.
• Edit profile.
• Change avatar.
• Change profile color.
• Rename profile.
• Set a default profile.
• Delete profile.
• Clear individual profile data.
• Optionally protect profiles with a PIN or biometric authentication, if supported.

Before deleting a profile, show a confirmation dialog explaining that its local browsing data may be permanently deleted.

4. Advanced Tab Management

Create a powerful tab management interface.

Features:

• Open multiple tabs.
• Display tabs in a modern grid layout.
• Show website thumbnails or favicons.
• Display website titles.
• Switch between tabs instantly.
• Close individual tabs.
• Close all tabs.
• Duplicate tabs.
• Reopen recently closed tabs.
• Group tabs by category, if supported.
• Search open tabs.
• Keep selected tabs open when restarting the application.

Each profile must maintain its own independent tab collection.

Include a tab counter showing the number of open tabs in the active profile.

5. Private Browsing Mode

Add an incognito or private browsing mode.

Features:

• Open private tabs.
• Use a visually distinct private browsing interface.
• Do not save private browsing history.
• Do not retain private session cookies after the private session ends.
• Keep private tabs separate from regular tabs.
• Provide a clear option to close all private tabs.

Private browsing should be separate from normal profile browsing data. Clearly explain that private mode does not make browsing anonymous to websites, internet providers, or network administrators.

6. Browser Settings

Create a comprehensive settings page with the following categories.

General

• Default homepage.
• Default search engine.
• Startup behavior.
• Default profile.
• Language selection.
• Theme selection.
• Toolbar customization.

Privacy and Security

• Clear browsing history.
• Clear cookies.
• Clear cache.
• Manage website permissions.
• Block pop-ups.
• Safe browsing options, where supported.
• Do Not Track preference.
• Private browsing settings.

Downloads

• Download location, if supported.
• Download history.
• Pause and resume downloads, where supported.
• Delete downloaded files.
• Download notifications.

Appearance

• Light mode.
• Dark mode.
• System default.
• Custom accent colors.
• Homepage customization.
• Compact or comfortable layout.

Search Engine

Include configurable options such as:

• Google.
• Bing.
• DuckDuckGo.
• Yahoo.
• Custom search engine URL.

Advanced

• JavaScript settings.
• Desktop site toggle.
• Text scaling.
• Site-specific settings.
• Experimental features, if supported.

7. Bookmarks and Browsing History

Bookmarks

• Save the current page.
• Edit bookmark title and URL.
• Organize bookmarks into folders.
• Search bookmarks.
• Import and export bookmarks, where supported.
• Display bookmarks on the homepage.
• Maintain separate bookmarks for every profile.

Browsing History

• View browsing history chronologically.
• Search browsing history.
• Filter by date.
• Remove individual history entries.
• Clear history by time range.
• Maintain separate history for each profile.
• Provide a recently closed tabs section.

8. Website Compatibility and Browser Engine

The browser must support real website navigation and rendering.

Implement:

• Standard HTML, CSS, and JavaScript rendering.
• HTTPS navigation.
• Website redirects.
• Responsive websites.
• Back and forward navigation.
• Page reload.
• Download handling, where supported.
• File upload.
• Website permissions.
• Desktop site mode.
• Full-screen video playback, where supported.
• External link handling.
• Basic error pages for unavailable websites.

Use a suitable native browser engine such as Android System WebView for an Android application.

Do not build a fake browser that only loads predefined pages or displays URLs without actually rendering websites.

Be transparent about engine limitations and any features that require native Android integration.

9. Additional Advanced Features

Implement the following features wherever the chosen platform supports them:

• QR code scanner for opening URLs.
• Share current page.
• Copy current URL.
• Find text on page.
• Translate page using an available translation service.
• Reader mode, if technically feasible.
• Website notifications with permission controls.
• Picture-in-picture video support.
• Password manager integration, where supported.
• Autofill integration.
• Text-to-speech for webpage content, if supported.
• Custom homepage shortcuts.
• Browser data backup and restore.
• Import and export bookmarks.
• Battery-conscious background tab management.

10. Navigation and Menus

Design a three-dot menu containing:

• New tab.
• New private tab.
• New profile.
• Switch profile.
• Bookmarks.
• History.
• Downloads.
• Find in page.
• Translate.
• Desktop site.
• Share.
• Settings.
• Help and feedback.

Use appropriate icons and organize related actions into clear groups.

Show contextual options based on the current screen.

11. Technical Architecture

Before implementation, identify the best architecture for a real Android browser.

Preferred approach:

• Native Android application.
• Kotlin.
• Android WebView or another appropriate rendering engine.
• Jetpack Compose for a modern native interface, if available.
• Room database for structured local data.
• DataStore for user preferences.
• Android Keystore for sensitive credentials.
• Proper Android lifecycle management.

For multi-profile isolation, investigate the storage isolation capabilities of the chosen engine. If Android WebView is used, do not assume that simply creating separate WebView instances provides independent cookie and storage environments. Use supported profile or data-directory isolation mechanisms where available, and document any limitations.

If complete isolation cannot be reliably implemented with the chosen engine, explain the limitation and propose a suitable alternative rather than presenting shared storage as genuine multi-profile support.

Keep the architecture modular, with separate components for:

• Browser engine.
• Profile management.
• Tab management.
• Navigation.
• Bookmarks.
• History.
• Downloads.
• Settings.
• Private browsing.
• Data persistence.

12. Performance and Security

Optimize the application for everyday mobile use.

Requirements:

• Fast application startup.
• Efficient memory usage.
• Smooth tab switching.
• Background tab suspension where appropriate.
• Proper handling of Android lifecycle events.
• Secure HTTPS navigation.
• Safe handling of downloaded files.
• No unnecessary collection of browsing data.
• No hardcoded API keys.
• No unnecessary third-party trackers.
• Clear permission requests.
• Protection against accidental data loss.

Avoid automatically granting sensitive website permissions.

13. Screens to Build

Create and connect all of the following screens:

1. Splash screen.
2. First-launch onboarding.
3. Main browser homepage.
4. Browser webpage view.
5. Search suggestions screen.
6. Tab switcher.
7. Profile switcher.
8. Create profile screen.
9. Edit profile screen.
10. Profile management screen.
11. Bookmarks screen.
12. Browsing history screen.
13. Downloads screen.
14. Private browsing screen.
15. Browser settings.
16. Privacy and security settings.
17. Search engine settings.
18. Homepage customization.
19. Website permissions manager.
20. About browser screen.

Every screen should be connected through functional navigation.

14. Development and Testing

Build the application incrementally.

Phase 1:

• Establish the project architecture.
• Build the main browser interface.
• Implement actual website rendering.
• Implement address bar and navigation.

Phase 2:

• Implement multi-profile creation.
• Implement profile switching.
• Establish profile-specific storage isolation.
• Test cookies, login sessions, local storage, and browsing history across profiles.

Phase 3:

• Implement tab management.
• Implement bookmarks and history.
• Implement private browsing.
• Implement settings and themes.

Phase 4:

• Implement downloads and additional features.
• Optimize performance.
• Add error handling.
• Test on different Android screen sizes.

Critical testing scenarios:

• Open a website and sign in under Profile A.
• Create Profile B and visit the same website.
• Verify that Profile B cannot access Profile A's login session or local browsing data.
• Switch back to Profile A and verify that its tabs and sessions are restored.
• Restart the app and verify that profiles and tabs persist.
• Test private browsing and confirm that private session data is cleared when the session ends.
• Test browser navigation, downloads, bookmarks, and settings.

15. Final Deliverables

Generate:

• Complete project source code.
• A working mobile application.
• All required configuration files.
• A clean and organized project structure.
• Instructions for building and running the application.
• Android APK generation instructions, if native Android development is supported.
• A list of implemented features and any platform limitations.

Do not stop after creating the UI or a basic demo. Prioritize a working browser engine, genuinely isolated profiles, stable tab management, and a polished mobile experience.

Final instruction: Start by analyzing the available Google AI Studio development environment and selecting the most suitable implementation strategy. Then build the application in functional stages, testing each core feature before proceeding. If a requested native capability is outside the environment's capabilities, explain exactly what is missing and provide the closest technically sound implementation instead of simulating functionality. 

  end