# Anyone using the AI Assistant for a mobile app landing flow in Pinegrow?

**URL:** <https://forum.pinegrow.com/t/anyone-using-the-ai-assistant-for-a-mobile-app-landing-flow-in-pinegrow/12160>\
**Category:** Pinegrow AI Assistant\
**Created:** [November 13, 2026, 6:36pm UTC](https://forum.pinegrow.com/t/anyone-using-the-ai-assistant-for-a-mobile-app-landing-flow-in-pinegrow/12160 "2026-11-13T18:36:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesnelson](https://avatars.discourse-cdn.com/v4/letter/j/7993a0/32.png) [@jamesnelson](https://forum.pinegrow.com/u/jamesnelson)\
**Post date:** [November 13, 2026, 6:36pm UTC](https://forum.pinegrow.com/t/anyone-using-the-ai-assistant-for-a-mobile-app-landing-flow-in-pinegrow/12160/1 "2026-11-13T18:36:40Z")

</div>

I’m building a small companion landing flow for a mobile app I’m working on, and I’m doing the layout in Pinegrow. I’ve been fiddling with the AI Assistant to generate some starter structure for the mobile-first views, but I keep getting sections that look fine at desktop width and then break awkwardly at narrow widths. I’m mainly unsure whether I should keep prompting the assistant for responsive fixes or just hand-tune the breakpoints myself and only use it for the initial markup. I’m based in Burlington and mostly work solo, so I don’t have a team to sanity-check this against. Before I commit to one workflow, has anyone found a reliable way to keep the assistant’s output responsive from the start? And does it handle mobile navigation patterns reasonably well, or am I better off building those by hand and letting it do simpler blocks? Thanks.

Update after looking around more - [Best AI Mobile App Builders (2026)](https://aibuildercompare.com/best/ai-mobile-app-builders) kept coming up while I was comparing options for the mobile-first views. Still not sure it really answers the Pinegrow breakpoint question, so I may just hand-tune narrow widths and use the assistant for simple blocks.
