SPA Visibility Fix

@arbu1499

Hi, I understand this is a state-conflict issue inside your Bubble SPA — especially the reusable Hamburger menu not properly triggering visibility on the main page due to custom state separation. I can audit the Element Tree (Z-index/stacking), properly sync yes/no states between Mobile_Header_New and Mobile_Home1, resolve the “Welcome Screen” blocking logic, and fix any collapsing from “Align to Parent” containers. I’ve handled similar SPA state conflicts in Bubble before and can jump in immediately to stabilize the workflow cleanly without breaking your Native wrapper. Looking forward for your positive response in the chatbox. Best Regards, Arbaz T

@toriquldev123

Hello Dear! I write to introduce myself. I'm Engineer Toriqul Islam. I was born and grew up in Bangladesh. I speak and write in English like native people. I am a B.S.C. Engineer of Computer Science & Engineering. I completed my graduation from Rajshahi University of Engineering & Technology ( RUET). I love to work on Web Design & Development project. Web Design & development: I am a full-stack web developer with more than 10 years of experience. My design Approach is Always Modern and simple, which attracts people towards it. I have built websites for a wide variety of industries. I have worked with a lot of companies and built astonishing websites. All Clients have good reviews about me. Client Satisfaction is my first Priority. Technologies We Use: Custom Websites Development Using ======>Full Stack Development. 1. HTML5 2. CSS3 3. Bootstrap4 4. jQuery 5. JavaScript 6. Angular JS 7. React JS 8. Node JS 9. WordPress 10. PHP 11. Ruby on Rails 12. MYSQL 13. Laravel 14. .Net 15. CodeIgniter 16. React Native 17. SQL / MySQL 18. Mobile app development 19. Python 20. MongoDB What you'll get? • Fully Responsive Website on All Devices • Reusable Components • Quick response • Clean, tested and documented code • Completely met deadlines and requirements • Clear communication You are cordially welcome to discuss your project. Thank You! Best Regards, Toriqul Islam

@techsty2014

Hi there, I will fix the visibility conflicts in your DiveBook SPA so the hamburger menu correctly triggers the Menu Group on the main page, the Welcome Screen no longer persists and blocks other views, and all Align to Parent containers hold their layout properly. The core issue is likely that the Reusable Element (Mobile_Header_New) is setting its own internal state but that state change is not being relayed to the parent page (Mobile_Home1) through a Custom Event or URL parameter. I will audit the Element Tree for z-index conflicts, then wire a proper state sync between the Reusable and the page-level current_view logic so every visibility toggle fires in the correct order. For the Welcome Screen persistence, I will check whether its conditional visibility is bound to a state that defaults to "yes" on page load and never gets reset when the current_view value changes. Questions: 1) Is the Welcome Screen supposed to show only on first launch, or every time the app opens? 2) Are you using Custom Events or URL parameters to communicate between the Reusable Header and the main page, or is it purely custom states? 3) Do you have editor access ready to share, or will you need to add me as a collaborator first? Ready to start whenever you are. Faizan

@Hubready

Hello!, I am a Florida-based senior software engineer with extensive experience in mobile app development and debugging, particularly with platforms like Bubble.io. I carefully read your project description regarding the visibility logic issue in DiveBook and I am confident that my 15 years in software development will help resolve this emergency bug efficiently. To ensure I fully understand the problem, could you please clarify the following questions to help me better grasp the project? 1. What specific visibility conflicts are you encountering in the app? 2. Are there any particular devices or OS versions where this issue is most prominent? My approach would involve first replicating the issue to identify the root cause, followed by implementing tactical fixes while ensuring stability across the application. I have worked on several similar projects, including a mobile app for a local travel agency and a budgeting app that streamlined user experiences, which might help in addressing your needs. I’m committed to delivering a solution that not only fixes the immediate issue but also enhances the overall functionality of your app. Let’s connect and discuss how I can help you resolve this swiftly! -James

@jeric5g

Hello, I’ve reviewed the Bubble SPA issue with DiveBook’s native wrapper. I’ll audit the Element Tree for Z-index conflicts, then align the yes/no states between Mobile_Header_New and Mobile_Home1. I’ll fix Welcome Screen persistence on load and ensure containers with Align to Parent stay stable, so the Menu Group triggers reliably from the Hamburger inside the Reusable. I’ll deliver a minimal, testable patch and verify on Android wrapper, with a quick round of regression tests to prevent new blocking states. Best regards Jeric

@venplura

Hi there! Are there any other reusable elements interacting with the menu visibility that might be affecting the state sync? Regardless, this is definitely something that I feel confident delivering on, given my past experience. I would love to discuss your project further! Looking forward hearing from you. Kind Regards, Corné

@eduards8

Hello. I can jump in today to debug your Bubble SPA (DiveBook) visibility/state conflict between page custom states and reusable states. I’ll audit z-index/stacking in the element tree, then unify state flow between Mobile_Header_New and Mobile_Home1 (single source of truth for current_view / menu_open). I’ll fix the Welcome Screen group showing on load and blocking other views, and verify “Align to Parent” groups don’t collapse across breakpoints/native wrapper. I’ll deliver a tested fix on your staging version and a short note of what changed. Timeline: within 24 hours once I have editor access and steps to reproduce. Best regards. Eduard.

@vasylklymiu

Hi, I would like to grab this opportunity and will work till you get 100% satisfied with my work. I just applied after read your job posting carefully and I believe that I am good fit to your project. I'm a serious bidder. I will satisfy you with my high skills! I am an expert which have 8+ years of experience on Mobile App Development, Android, HTML5, Debugging, PhoneGap, Software Development, Web Development, Mobile Development I am looking forward to meet you to discuss the further detail about this project. Looking forward to hearing from you. Warm Regards

@glennc30

Hello, Greetings , Good morning! I am professional mobile software engineer with skills including HTML5, Mobile Development, Android, Web Development, Software Development, Mobile App Development, Debugging and PhoneGap. "Align to Parent" Please contact me to discuss more regarding this project. Thanks for giving opportunity

@imranhaider2018

Hey , I just went through your job description and noticed you need someone skilled in PhoneGap, HTML5, Android, Software Development, Web Development, Mobile Development, Mobile App Development and Debugging. That’s right up my alley. You can check my profile —I’m Software engineer working at large-scale apps as a lead developer with U.S. and European teams. I’ve handled several projects using these exact tools and technologies. Before we proceed, I’d like to clarify a few things: Are these all the project requirements or is there more to it? Do you already have any work done, or will this start from scratch? What’s your preferred deadline for completion? Why Work With Me? 1) Over 230 successful projects completed. 2) I have not received a single bad feedback since the last 5-6 years. 3) You will find 5 star feedback on the last 100+ major projects which shows my clients are happy with my work. 4) Long-term track record of happy clients and repeat work. I prioritize quality, deadlines, and clear communication. Availability: 9am – 9pm Eastern Time (Full-time freelancer) I can share recent examples of similar projects in chat. Let’s connect and discuss your vision in detail. Kind Regards, Imran Haider

@osmelt5

Hello , Thank you for posting your project. I am an experienced software developer with strong expertise in PhoneGap, Web Development, Debugging, Software Development, Android, HTML5, Mobile App Development and Mobile Development. I have successfully completed similar projects and can deliver high-quality, scalable, and reliable solutions tailored to your requirements. I am confident I can help you achieve your goals efficiently and within your timeline. Let’s connect to discuss the project details, expectations, and next steps. Looking forward to working with you. Best regards, Osmel

@fakhara1ha

Hey , I just finished reading the job description and I see you are looking for someone experienced in Web Development, PhoneGap, Mobile Development, HTML5, Mobile App Development, Software Development, Debugging and Android. This is something I can do. Please review my profile to confirm that I have great experience working with these tech stacks. While I have few questions: 1. These are all the requirements? If not, Please share more detailed requirements. 2. Do you currently have anything done for the job or it has to be done from scratch? 3. What is the timeline to get this done? Why Choose Me? 1. I have done more than 250 major projects. 2. I have not received a single bad feedback since the last 5-6 years. 3. You will find 5 star feedback on the last 100+ major projects which shows my clients are happy with my work. Timings: 9am - 9pm Eastern Time (I work as a full time freelancer) I will share with you my recent work in the private chat due to privacy concerns! Please start the chat to discuss it further.

@sagarr1999

Don't worry, Sir. I can start immediately. This looks like a classic state sync + visibility hierarchy conflict in Bubble SPA setups — especially when mixing Page Custom States with Reusable Element states inside a native wrapper. Here’s how I’ll fix it: • Audit Element Tree + Z-index stacking to ensure the Menu Group isn’t hidden behind another layer. • Properly synchronize the yes/no state between Mobile_Header_New and Mobile_Home1 (move to a single source of truth if needed). • Fix the Welcome Screen persistence by correcting default visibility + conditional logic on page load. • Check all Align to Parent containers to prevent collapsing or layout conflicts. • Test inside Android native wrapper to confirm behavior matches browser preview. I’ve handled similar Bubble SPA state conflicts before, especially with hamburger-triggered menus and reusable components. I can begin right away and resolve this quickly. Let’s fix DiveBook today.

@tommasog3

⭐⭐⭐Reusable state conflicts in Bubble? I’ll untangle it fast.⭐⭐⭐ I’ve debugged Bubble SPAs with heavy custom state logic similar to DivvyUp and Qoins-style builds — especially where reusable elements and page states collide. Native wrapper quirks on Android don’t scare me. Here’s my structured fix plan: - Element Tree Audit – Inspect z-index + stacking context, ensure Menu Group isn’t trapped under a persistent layer. - State Synchronization – Replace conflicting yes/no states with a single source of truth (either lift state to page level or convert to URL parameter-driven state for SPA stability). - Welcome Screen Fix – Correct default visibility + workflow trigger timing (likely “on page load” not resetting state). - Align to Parent Debug – Check min-height, conditional collapse, and parent container shrink behavior. Most critical issue: Bubble evaluates reusable states in isolation. If the Hamburger is toggling inside Mobile_Header_New but the page listens to Mobile_Home1, they’re not inherently synced. I’ll centralize that logic so visibility flows properly. You’ll get a clean, stable state architecture — no ghost overlays, no blocked views, no collapsing containers. Ready to start immediately. Fixed price is fine. Best Luck