Roadmap

Enable users to import existing designs and layouts directly from Figma files to serve as a starting point or structure for their App

The concept: Buy digital products cheaply from wholesalers, put them on my own website, and resell them to my customers. Product categories. Licenses; Subscriptions; Software etc..

Problem Statement: Currently, the portal builder lacks visibility into active user sessions. When two developers (e.g., my co-worker and I) work on the same project simultaneously, we face a high risk of race conditions. Changes made by one user can be overwritten by the other upon saving, leading to lost work, configuration drift, and general frustration. Proposed Solution: We need a mechanism to manage concurrent editing. This could be approached in two ways, listed in order of preference: Option 1: Resource Locking (Session Blocker) Exclusive Edit Access: When a user opens a project or specific page, the system "locks" it for others. Presence Indicators: A visual badge showing "User X is currently editing this." Read-Only Mode: Other users can view the project but cannot save changes until the lock is released or a timeout occurs. Option 2: Real-Time Syncing (Collaboration Mode) Live Updates: Changes made by User A are reflected instantly on User B’s screen (similar to Google Docs or Figma). Granular Locking: Instead of locking the whole project, lock specific components or sections while they are being edited. User Stories: As a developer, I want to know if my teammate is already working on a specific page so I don't start making conflicting changes. As a project lead, I want the system to warn me if I’m about to overwrite someone else's more recent save. Success Criteria: Zero "Save Conflicts" reported during team builds. Visible UI indicators showing who is active in a project. A "Force Release" option for admins if a session lock gets stuck.

Let us upload CSV files, which are useful for populating databases.

Let us edit a previous prompt/message and “rewind” from that point, without the whole chat / history feeling confusing. Key parts: Editing an earlier message creates a new branch/timeline from that stepKeep the original timeline intact (so nothing is “lost”)Show the timelines clearly (A/B, or simple number indicator under the message), with a one-click switch This is a super common workflow in AI builders that I like a lot.

Leverage a Multi-Streamable architecture to enable the simultaneous execution of multiple AI agents and UI updates within a single session, preventing execution bottlenecks. This allows for server-side persistence where complex tasks (like building multiple pages or running background scripts) continue independently of the user's browser state, ensuring a non-blocking, high-efficiency workflow

Connect your applications to n8n to enable powerful, low-code automation workflows and sync data with over 400 external services. This integration allows users to trigger complex background tasks, process data via AI agents, and bridge the gap between their Sticklight UI and enterprise software without writing custom backend logic

Implement clear, interactive UI buttons for actions requiring user consent (such as triggering Sticklight Cloud) to prevent users from waiting on a "hidden" chat request. This ensures the interface remains communicative and prevents project stalling by visually signaling when the system is awaiting a user’s "Go" or "Approve" signal.

Hi, I have a feature request regarding user management. I would like the ability to create and manage users inside Vibe Coding, including assigning roles and permissions. Ideally, there would also be an admin panel for user management where I can: Create and delete users Edit user information and access levels Assign roles and permissions Control what parts of the project each user can access View user activity and login history This would allow me to build applications with multi user access, team dashboards, client areas and more without needing to build the entire system from scratch. Is this something you plan to support in the near future? If possible, please consider adding this to the roadmap. Thank you.

the ability to clone platforms from base44/loveble/bolt into sticklight

Implement integration with GitHub, allowing users to clone the generated app/website code, maintain two-way synchronization for seamless code edits, and enable unlimited export and self-hosting of their projects. This provides full ownership and flexibility for developers.

Implement a dedicated non-production environment (staging/sandbox) that allows users to test major updates, design changes, and feature integrations privately and thoroughly before deploying them live to the production website/app.

I have an idea for how we can make using Sticklight even easier and more efficient for teams or friends. It would be fantastic if we could share a personal link or code that would allow, for example, a colleague, a team, or even a good friend to share the Sticklight page. This would allow us to test projects together, try out products, or evaluate features – without everyone needing a separate login. This kind of "shared testing" would not only facilitate collaboration but also encourage the exchange of experiences and feedback. I'm convinced that this feature would make working together with Sticklight even more attractive and practical – both for teams in their professional lives and for private users who enjoy discovering new things together.

Allow topping up an account with a bank of credits, as an addition to the monthly plan. This way a user could purchase as many credits as needed when more intensive work is required for a particular project.

This is a feature that will differentiate you from competitors and deliver clear added value. Credit management should be per project, not per account as it is today. Each project should be able to purchase and manage its own credits. For example: Project 1: I need 100 credits, so I’ll buy the $25 package for that project. Project 2: I need 200 credits, so I’ll buy the $50 package for that project. This would give users much better control and visibility. In addition, there should be an option to transfer credits from one project to another. Another topic - also a strong differentiator that would give your customers a major advantage: At the end of a project, when there is no longer a need for the minimum 100 credits package, there should be an option to purchase a package that includes: hosting, a custom domain, and removal of the Sticklight watermark. Today, the only way to get these benefits is through the 100 credit package, which means customers are paying for credits they no longer need.

Add option to add new users (like customers or colleagues) to join existing project so they can also edit the project.

Implement an intelligent suggestion engine that offers relevant UI elements, animations, and functional enhancements based on the user's current project and prompts. By allowing users to select and apply multiple suggested improvements simultaneously, the platform eliminates the need for manual copy-pasting from external tools and streamlines the creative process.

Implement a dedicated, cloud-based Media Library where users can upload, manage, organize, and retrieve all visual and digital assets (images, videos, PDFs, custom fonts, etc.) used across their generated Sticklight applications and presentations. The library should include features like tagging, searching, and automatic optimization of assets for web delivery.

Implement deep, native integration to use WordPress as a Headless CMS by leveraging Rest API options. This allows users to manage content (posts, pages, products, etc.) through the familiar, powerful WordPress dashboard while leveraging Sticklight's output for a modern, high-performance, and secure front-end application.

Implement an integrated tool that analyzes and grades the generated app based on key performance metrics, such as Core Web Vitals (LCP, FID/INP, CLS) and general Page Speed. The feature will provide clear, actionable suggestions and optimizations (e.g., image compression, asset minification, and caching improvements) to ensure fast loading times and a smooth user experience.

Implement a foundational Design System that governs all generated UI components. The core of this feature is a dedicated Theme Editor which provides granular control to users. This editor allows users to define, customize, and manage global styling variables, including color palettes, typography scales, spacing tokens, and component sizing, effectively allowing them to create and apply custom Brand Themes across the app for comprehensive visual consistency.

Implement a dedicated, intuitive visual editor (e.g., drag-and-drop or WYSIWYG) that allows users to manually adjust, refine, and customize the layout, styling, and content of the generated website/app without relying solely on the original prompt.

It would be very useful to have a user-level preference .md file that applies across all projects. Right now, I often have to repeat the same instructions over and over again, such as coding preferences, design principles, project structure, naming conventions, accessibility requirements, and general workflow rules. A persistent preference file on user level would save time, reduce friction, and improve consistency across projects. This could include things like: • preferred coding style • preferred frameworks or implementation patterns • design and UX standards • do’s and don’ts • content and tone preferences • accessibility and SEO defaults It would make the system feel much more personalized and reduce the need to re-explain the same context in every new project.

Allow deleting elements through the visual editor.

Make an option in the control panel to delete a project

Allow users have the option to clone an existing project in sticklight

Implement a native, ready-to-use authentication module that allows users to easily add features like sign-up, login, password reset, and user management to their generated app, supporting common methods like email/password and potentially third-party OAuth providers (Google, GitHub, etc.).

Implement a robust suite of tools providing full control over Search Engine Optimization and discoverability. This toolkit will include an Automated On-Page SEO Audit (checking titles, descriptions, headers, and alt tags), a Manual Editor for customizing Page Titles & Meta Descriptions, and Automation for generating and managing the robots.txt file and sitemap.xml.

Implement full support for a Dark Mode theme across the entire Sticklight platform UI, including the dashboard, editor, and settings. Users can enable this feature in their preferences to reduce eye strain and match their operating system settings.

Implement page navigation, eliminating the need to manually track or type AI-generated filenames. This improves workspace discoverability by providing a clear visual overview of the entire site structure, ensuring users can seamlessly switch contexts and never lose track of pages.

In the opening screen where is all the project, make a mokeup to the first page not only he name

Allow editing existing API keys, instead of having to delete and recreate a new one in cases where the user needs to change the API key.

Give the option to unpublish projects

Please add proper SPA routing support at the server/CDN level. Right now, valid pages on multi-page sites can load correctly in the browser but still return HTTP 404 instead of 200. This breaks SEO, because Google treats those pages as “not found” and does not index them.

Allow unused credits rollover to following billing period, similar to Loveable.

Idea for improvement: Instead of relying on a single detailed prompt to generate an entire SaaS app, Sticklight could introduce a Planning Mode powered by domain-specific agents. Before execution, users collaborate with agents focused on product logic, app architecture, UX/UI flows, user management, and performance. Each agent helps clarify requirements, highlight risks and trade-offs, and propose options within its domain. The process is sequential and approval-based: define scope → review structure and flows → validate decisions → only then move to implementation. This shifts Sticklight from prompt-driven generation to a structured, professional SaaS planning workflow that reduces rework and improves build quality.

Please add the planing option in the main dashboard, not only after asking for the main idea. I tried to build a new website and i was planning that this would be with some pages at first before starting the system to work. The plan option is only in the builder. I think that if this option for planning before building and designing will be more functional and maybe less code and system operation.

Provide dedicated, secure integrations with leading transactional email service providers (such as Resend and SendGrid). This feature allows users to easily configure their generated app to handle mission-critical emails like user authentication flows (password resets, account verification), notifications, and order confirmations with high deliverability.

Allow users to connect a custom domain to their generated Sticklight application/website for a more professional and branded online presence.

This will enable users to provide sensitive secrets and keep them safely inside our platform - this is something our competitors lack in.