Multiple Mobile UI Issues: Missing Menu, Poor Placeholder, and Broken CTA

[Dharmiksarvaiya24]

What's happening?

In the mobile view of lingo.dev, several UI issues are observed after login. The hamburger menu is missing it overlaps the main content instead of behaving correctly , input placeholders on auth pages look unprofessional, and the “Talk to Localized Expert” button is partially cut off. These issues negatively impact usability and visual quality.

Exact Reproduction Steps

1. Navigate to https://lingo.dev on a mobile device

2. Observe the top-right corner:

   • The button is not properly visible/aligned

3. Navigate to https://lingo.dev/login

4. Navigate to https://lingo.dev/signup

5. Inspect input fields (Name, Email, Password):

   • Observe placeholder styling (not professional)

6. Log in with valid credentials

7. On the main page:

   • Open the menu
   • Observe that it overlays over the main content instead of proper layout behavior

Expected

1. Navigate to https://lingo.dev on a mobile device

   • The top-right button should be fully visible, properly aligned, and responsive

2. Navigate to https://lingo.dev/login and https://lingo.dev/signup

   • Input fields (Name, Email, Password) should have simple, clear, and professional placeholders (e.g., Username, Email, Password)

3. Log in with valid credentials

4. On the main page:

   • A hamburger menu should be visible in the header
   • Opening the menu should not overlap the main content improperly
   • The menu should display with proper layout, spacing, and responsiveness

Actual

• The menu overlaps the main content instead of displaying properly - hamburger menu is missing
• The top-right button is partially hidden and not properly aligned
• Input placeholders (Name, Email, Password) appear unprofessional

Screenshots/Videos

[Dharmiksarvaiya24]

I would like to work on this issue. I have reviewed the problem and understand the required fixes for the mobile UI, including the menu behavior, button visibility, and input styling. Kindly assign this issue to me so I can proceed with the implementation.

[vinaykn07]

hey i would like to work on this issue i have seen the this behaviour in my repo also .
kindly assign this issue me so that i can resolve it effectively