Visily Feature Requests

I think we could consider to have a PC or Android - iOS aplication to solve the web lagging issue when we have many elements on the board.

purpose of the app is to help users search for and rent tools (construction, home repair, etc.) from nearby providers. Main features to include in the wireframe: Homepage: Header with logo, search bar, login/sign-up buttons. Hero section with a call to action: "Find the right tool for your next job". Categories grid (Construction, Electrical, Plumbing, Gardening, etc.). Section for featured/popular tools. Footer with links (About, Contact, Terms, etc.). Tool Search Results Page: Search bar at top. Filters sidebar: category, location, availability, rating, price. Tool cards showing: image, name, price per hour/day, rating, availability. Pagination or infinite scroll. Tool Details Page: Large tool image and gallery. Tool name, detailed description. Price (per hour/day). Availability calendar or scheduler. Provider info and location map. Button: "Rent This Tool". Rental Booking Flow: Date/time picker for rental period. Delivery address input (auto-locate or manual). Cost summary. Payment method selection. Button: "Confirm Rental". Confirmation screen after booking. User Dashboard (after login): Tabs: My Rentals, Payment Methods, Addresses, Profile Settings. View of active/upcoming/past rentals with status. Option to cancel upcoming rentals. Optional: Tool Owner Dashboard (if users can also list tools) Button: “List My Tool” Upload photo, add description, set pricing, set availability. Design Guidelines: Clean, modern web layout. Clear CTAs: Rent, Search, Confirm. Responsive design (desktop + mobile-friendly). Use construction-themed palette (e.g., yellow, dark gray, white). The wireframe should include all the above sections across multiple pages (not a single long page).

✈️ Landing Page Structure for Sideflight 🔹 1. Hero Section (Top fold) Purpose: Instantly capture interest and explain the concept. Include: Bold headline: “Meet brilliant minds at 35,000 feet.” Subtext: Connect with professionals on your flight. Discover, book, and network while you travel. CTA buttons: Join Now / View Demo Visual: Hero image or mockup (like people networking on a plane) 🔹 2. How It Works Purpose: Quickly educate users about the steps. Use 3–4 clear steps with icons or illustrations: Enter Flight Details – Sync or input your flight info. Discover Experts – Browse professionals on your flight. Connect or Book – Send a message or schedule time. Network Mid-Flight – Meaningful conversations in the sky. 🔹 3. Why Sideflight? / Value Propositions Purpose: Show benefits and build trust. Use a 2–3 column grid of key benefits like: ✈️ Make Every Flight Count 👔 Meet Investors, Mentors, or Peers 🧠 Learn from Experts on Demand 🔒 Secure & Private Matching 🔹 4. User Scenarios / Target Personas Purpose: Help users see themselves using the product. Include illustrated personas like: Startup Founder → Meets VCs Solo Traveler → Finds co-founders Coach/Speaker → Books clients in-flight Consultant → Monetizes expertise during flights 🔹 5. Featured Expert Previews (like Airbnb cards) Purpose: Show real or mock profiles of people you could meet. Include: Expert name, title, expertise tags, price, rating Profile photo View Profile / Book CTA 🔹 6. Testimonials / Social Proof Purpose: Build credibility and show early traction. Include: Short quotes from users (“Met my co-founder flying to Singapore!”) Logo strip (if partners or used by companies) Star ratings or Trustpilot style UI (optional) 🔹 7. FAQ Section Purpose: Handle objections or hesitations. Example questions: Is this available on all flights? What if no one is on my flight? Can I charge for sessions? Is my flight info safe? 🔹 8. Newsletter Signup or Early Access CTA Purpose: Grow your waitlist or user base. Include: Simple form: Name + Email + Upcoming Airline (optional) CTA: Get Early Access 🔹 9. Footer Include: About | Blog | Privacy Policy | Terms Social media links Contact Email Light version of logo

To take full usage of content filling to mockup designs and the ease to change color system in visily.

One of the most powerful and appreciated features of Visily is the ability to export components from Visily to Figma. This greatly supports downstream design workflows. However, the reverse—importing components from Figma into Visily—is currently not supported. Introducing this capability would significantly expand Visily’s usefulness and integration within existing design ecosystems. Example Use Case: We have a set of screens designed in Figma. To rebuild those in Visily, we currently rely on the PNG import feature. Unfortunately, this lacks precision—text layers become flattened, components lose structure, and styles must be reapplied manually. With direct Figma import, we could preserve the component hierarchy and save hours of work. Enable users to copy and import components (or even full design files) from Figma into Visily. This could be achieved through a plugin, a copy-paste mechanism via Figma API, or direct .fig file import. Benefits: -Migrate legacy design files into Visily without rebuilding from scratch. -Access to Figma Community Assets: Tap into Figma’s vast community resources and bring high-quality UI kits, templates, and components into Visily seamlessly.

Request for a "Copy and Replace Components" feature to reduce rework and maintain layout integrity when updating designs. I would like to request a "Copy and Replace Components" feature, similar to the one available in Figma. This feature would significantly reduce the effort needed to rework designs when changes are required. By allowing us to quickly update all screens without disturbing the existing layout and structure, it would streamline our design process and enhance efficiency.

I use Visily’s comment feature extensively for feedback and collaboration. However, I often find myself repeating the same comments manually when I duplicate screens or templates. Is there a way to duplicate comment threads to accompany duplicated screens or frames? This would significantly streamline my workflow by retaining context when reusing wireframes. If this feature doesn’t exist yet, would it be possible to support it in a future update? Thanks for considering this. I appreciate all the hard work you put into Visily!