Non-responsive mobile view during AI training

hmm okay - the user experience for them wont be great in your dev env preview on lovable editor. Publishing indeed would make this behave a lot better. Have you considered protecting access to the entire site via password protection, letting the expert view and interact with the site without it being open to the public? Also just as a side note, the chance of someone finding your projectname.lovable.app domain by chance is very very low. You are also able to publish a project to the people in your workspace. This means it wont be visible to the public, but only to your workspace accounts as a viewer, he should be able to use this function (edited)

yes, as a viewer

@AnaGSY understood - does the expert have access to your project on lovable?

@AnaGSY trying to fully understand your goal here. Are you trying to optimize for mobile?

You are also able to publish a project to the people in your workspace. This means it wont be visible to the public, but only to your workspace accounts

hmm okay - the user experience for them wont be great in your dev env preview on lovable editor. Publishing indeed would make this behave a lot better. Have you considered protecting access to the entire site via password protection, letting the expert view and interact with the site without it being open to the public? Also just as a side note, the chance of someone finding your projectname.lovable.app domain by chance is very very low.

Hey @Jon : Thanks for checking in — let me clarify I've built an agent that needs to be trained by a domain expert. This expert only uses mobile (no desktop). The issue is that inside the Lovable environment, even when switching to mobile view, the interface still behaves like a desktop web view and isn't truly responsive. The only workaround I see would be to publish the project and use the live website for training — but I don't want to publish yet because the project is still in development. So my goal is not to optimize the final product for mobile for now, but to enable mobile-only training before publication. Hope that clarifies!

as a viewer, he should be able to use this function (edited)

thanks a lot, will try this!

Hey @Jon : Thanks for checking in — let me clarify I've built an agent that needs to be trained by a domain expert. This expert only uses mobile (no desktop). The issue is that inside the Lovable environment, even when switching to mobile view, the interface still behaves like a desktop web view and isn't truly responsive. The only workaround I see would be to publish the project and use the live website for training — but I don't want to publish yet because the project is still in development. So my goal is not to optimize the final product for mobile for now, but to enable mobile-only training before publication. Hope that clarifies!

Hey @Jon 🇩🇪: Thanks for checking in — let me clarify I've built an agent that needs to be trained by a domain expert. This expert only uses mobile (no desktop). The issue is that inside the Lovable environment, even when switching to mobile view, the interface still behaves like a desktop web view and isn't truly responsive. The only workaround I see would be to publish the project and use the live website for training — but I don't want to publish yet because the project is still in development. So my goal is not to optimize the final product for mobile for now, but to enable mobile-only training before publication. Hope that clarifies!

@AnaGSY understood - does the expert have access to your project on lovable?

hmm okay - the user experience for them wont be great in your dev env preview on lovable editor. Publishing indeed would make this behave a lot better. Have you considered protecting access to the entire site via password protection, letting the expert view and interact with the site without it being open to the public? Also just as a side note, the chance of someone finding your projectname.lovable.app domain by chance is very very low.

yes, as a viewer

You are also able to publish a project to the people in your workspace. This means it wont be visible to the public, but only to your workspace accounts