This project is a continuation of the existing SMOX audit and production readiness review currently in progress. The objective is to continue working with the current auditor and transition from audit findings into implementation planning and execution. Current priorities include: • Review completed audit findings • Verify repository structure and production readiness • Implement 30-Day Smox Pro Trial functionality • Review Stripe Connect subscription management • Review Stripe webhook handling and payment events • Resolve subscription and payment-related issues • Correct booking timeline and client visibility issues • Resolve calendar history and scrolling issues • Improve notification reliability • Address production-impacting defects identified during the audit • Establish a milestone-based implementation roadmap Existing repositories, AWS access, Stripe access, audit documentation, and project assets will be provided as needed. This is not a new application build. The project already exists and is currently deployed. The goal is to continue the audit engagement and execute the highest-priority production readiness improvements identified during the review process.

Custom iPad Client Closeout, Feedback & Review Automation Platform Developer Project Overview We are a high-end residential design-build firm seeking a developer to create a custom iPad-based client closeout platform. The system will be used during final project walkthroughs to conduct a structured satisfaction survey, capture referrals and testimonials, generate personalized AI-powered review content, and guide homeowners through the Google Review submission process. Our goal is to create a seamless, professional experience that increases client engagement, captures valuable feedback, improves our online reputation, and strengthens long-term client relationships. This project will be used by our team in homeowners' residences during project closeout meetings and should be designed to be simple, intuitive, and completed in just a few minutes. Desired Workflow 1. Team member conducts an in-person closeout survey with the homeowner. 2. Responses are entered into the iPad application. 3. The system evaluates client satisfaction and identifies highly satisfied clients. 4. AI generates a personalized review draft based on the client's actual responses. 5. The client reviews and edits the review if desired. 6. The client enters or confirms their Google account information. 7. The system directs the client to our Google Review page and facilitates the review submission process. 8. Survey results, testimonials, referral opportunities, and review data are stored in a database and/or Google Sheets. Survey Questions The application should allow us to customize and modify survey questions over time. Initial questions may include: Overall Satisfaction * How satisfied are you with your overall experience? * Did the completed project meet or exceed your expectations? * Would you hire us again for future projects? Communication * Were we responsive to your questions and concerns? * Did you feel informed throughout the process? Design & Construction Experience * Were you satisfied with the design process? * Were you satisfied with the quality of workmanship? * Did our team effectively solve challenges that arose during the project? Referrals & Advocacy * Would you recommend us to friends or family? * Would you be willing to provide a referral? * Would you be willing to participate in a future case study or testimonial? Marketing Permissions * May we use photos of your project in our marketing materials? * May we use portions of your testimonial or review in our marketing materials? AI Review Generation Based on survey responses, the application should generate a natural, authentic review draft. Example: "Working with Marvista Design + Build was a wonderful experience. Their team was responsive, professional, and highly organized throughout the entire process. We especially appreciated their communication, attention to detail, and commitment to quality. The finished project exceeded our expectations, and we would gladly recommend them to anyone considering a remodeling project." The generated reviews should vary in language and structure so they feel authentic and personalized. Additional Features Testimonial Capture * Collect written testimonials * Optional voice-to-text testimonial entry * Store testimonials in a searchable database Referral Capture * Identify clients willing to refer others * Capture referral contact information * Track referral opportunities Net Promoter Score (NPS) * Include NPS scoring * Flag dissatisfied clients for internal follow-up * Prevent unhappy clients from being directed toward public review requests Reporting Dashboard * Review completion statistics * NPS tracking * Referral tracking * Testimonial tracking * Historical reporting Data Storage Preferred integrations include: * Google Sheets * Google Workspace * Airtable * Cloud database solutions We are open to recommendations. Technical Requirements We are open to the developer's recommendation regarding architecture and technology stack. Potential solutions include: * Native iPad application * React Native * Flutter * Progressive Web Application (PWA) * OpenAI API integration * Google Workspace integration * Airtable integration The solution should be easy to maintain and scalable for future enhancements. Future Vision This is intended to become Phase 1 of a broader client experience platform that may eventually include: * Automated review campaigns * Referral management * Client for Life program tracking * Testimonial library management * CRM integration * Marketing automation We are looking for a developer who can help us think strategically about the long-term roadmap, not simply build the initial application. Ideal Freelancer We are looking for someone who: * Has experience building custom business applications * Has experience with AI integrations * Has experience with survey platforms and workflow automation * Understands user experience and interface design * Can recommend the best technical approach * Can build scalable solutions that can evolve over time When Applying, Please Include 1. Examples of similar applications you have built. 2. Experience with AI-generated content and OpenAI integrations. 3. Experience with Google Workspace, Airtable, or CRM integrations. 4. Your recommended technical approach for this project. 5. Estimated timeline and budget range. 6. Any suggestions for improving the workflow described above. We are less concerned with a specific technology stack and more interested in finding the right development partner who can help us create an exceptional client experience.

We are seeking a skilled developer to create a baby registry platform similar to babylist.com. The platform should allow users to create and manage baby registries, add items, and facilitate gift-giving. The project involves developing a user-friendly interface, ensuring smooth functionality, and delivering a reliable solution. We are looking for someone who can work independently and communicate effectively throughout the project.

I'm seeking a consultant to guide me in building a social media app. The ideal candidate will have experience in social media marketing and app development, providing strategic guidance and technical expertise throughout the project. Responsibilities include advising on platform selection, feature development, and ensuring the app aligns with market trends. The consultant should be able to lead the project from inception to launch, ensuring a competitive and user-friendly product.

We're looking for a senior US-based developer to review our product architecture, codebase, and technical setup before launch. This is a short-term consulting role (~6–10 hours total) focused on scalability, performance, maintainability, security, and overall product readiness. Current stack includes React Native / Expo, Supabase, API integrations, web development frameworks, and automation workflows. We're looking for someone who can: • Review mobile and web application architecture
 • Evaluate backend structure, database design, and API integrations
 • Identify potential issues, bottlenecks, and security concerns
• Suggest improvements for scalability and long-term maintainability 
• Review automation workflows and system reliability
 • Assess launch readiness and best practices
 • Provide actionable technical feedback and recommendations
 • Communicate clearly and collaboratively This is not a full development role—it's a senior technical review and advisory engagement. Requirements: • US-based only
 • Senior-level experience in mobile and web application development
 • Experience shipping and scaling production products 
• Strong understanding of modern backend systems, APIs, and automation tools
 • Excellent communication skills Please include: • Relevant projects and products you've worked on 
• Years of experience
 • Areas of expertise (mobile, web, backend, automation, etc.) 
• Hourly rate 
• Availability (ASAP or within the next week)

We are interested in developing a web app that will allow us to automate a lot of the administrative tasks we need to do to carry out our work. The app will serve three main functions: 1) Provide a simple and easily accessible interface that will allow users to submit expense information that will be automatically stored in our organization's Google Drive. 2) Allow for admin to review this information and engage in a dialogue with the user if necessary. 3) Track all expense data in an organized way to a) allow users to view project expense summaries and b) allow admin to create and generate expense reports. Attached is an overview of how each interface should articulate with the others as well as a detailed summary of what each interface could look like. Note that the details here are not comprehensive and questions are expected, but the general shape is there. Note that these interfaces will need to effectively and seamlessly articulate with one another as well as external systems like Quickbooks.

I am working through a design agency on an application for their end client. I think the agency will need you to contract with them directly, but I will manage the project for them. I have scoped out the project already, and our plan is to internally perform a design phase with the client to produce a prototype with Lovable. There may be minor changes to scope after that design phase. The purpose of the app is to create bespoke wedding gown concept images for potential customers of an online wedding dress store. I have provided the details below and attached as a PDF 1. Customer opens an AI dress/gown design experience from a link in their separate e-commerce site. - This can be presented in its own page, we don't want a chat window to be present on any other page - This will be a chat-based interface built into the content area of the page, instead of a popup - The design must be elegant, and match the theme of the e-commerce site - The top navbar and footer don't need to be exactly recreated in this subdomain site, but should look similar enough to create a seamless experience - There will be no integration with the e-commerce site, we need to keep these web apps completely separate 2. The customer must sign up for an account and purchase one credit to begin the AI session - We will need to set up the subdomain site with its own payment processing system and login system - The payment integrations are Stripe to facilitate credit card and Apple pay, and a basic Paypal integration 3. The customers should be able to use a magic link to sign into their accounts, instead of having to remember a password - The account should automatically remember the browser to reduce friction for future access to the app 4. When an AI session begins, we will ask the customer a series of questions programmatically to prime the AI agent so that it can deliver better results - The questions will need to use conditional logic, such that the first question which determines one of 3 main conditional tracks: What type of gown are you looking for? Wedding Gown, Evening Gown, Cocktail Dress - If Wedding Gown is selected, the AI should suggest for the customer to take go to a bridal store and pictures of themselves in different dresses they like and upload the pictures, and describe what they do and don’t like about each dress. It can ask this in the freeform chat, since it may make the most sense to let them fill out the entire questionnaire to stay engaged, and we should reduce the costs of development for the questionnaire by omitting any unnecessary UI that the freeform chat can provide. - It may be best to always just prompt for them to upload the inspirational image at the beginning of the freeform chat so we can omit unnecessary programmatic UI, but in the case of the Wedding Gown it will specifically ask the customer to peform the above task. - We may have other specific questions to add to the questionnaire depending on what conditional track the customer chooses, though only the 3 main branches of conditional logic based on dress type will be required. - Examples of general questions it will need to ask are as follows: -- silhouette -- neckline -- sleeves -- fabric -- embellishments -- color -- train -- length -- closure -- lining -- structure -- inspiration -- event type -- I didn’t get the exact list of questions yet from my client that we should ask in the initial questionnaire. Let me know if you will need this information to accurately provide a price for the development of this application 5. We should not display a concept image after the programmatic questionnaire, the customer will be taken directly into the freeform chat from the questionnaire. - The AI agent may start with an overview of the selected choices from the questionnaire, then can generate concept images at its discretion. 6. The AI should guide the customer through a freeform conversation - The conversation should begin with the AI asking the customer to subjectively describe their dream dress 7. The AI should also make a suggestion near the beginning of the conversation for the customer to upload at least one inspirational photo, but photo upload is optional - If the customer uploads an initial inspiration image, the AI agent should not attempt to figure out body type, measurements, or any other information that we can gather programmatically. - It should treat the inspirational image the same way it would treat any image the customer uploads during the freeform chat, to reduce the cost of development as much as possible. 8. Customer can proceed with a freeform conversation description - The customer should have the option to type in a chat and to upload images - The purpose of the conversation is for the customer to describe the desired dress or gown in an open-ended way 9. AI generates one or more concept images based on the conversation, as soon as it can once it has enough information - The AI model we select should be very good at generating these types of images, this is probably the most important quality the AI model needs to have - The concept images should have the same quality as the final image 10. It is acceptable to generate the gown on a mannequin or a real human model, however the dress must be photorealistic, not a sketch or cartoonish rendering. 11. The concept images that the AI generates and the final image should portray the body type and skin color which the customer specifies - It is very important for us to render the image of the garment on the correct body type - ex. Hourglass, pear-shaped, thin, plus sized, etc. -- Specific body measurements do not need to be factored into the rendering of the body type, it just generally needs to be able to render the garment on different body types. - It is also very important for us to render the garment on a human model or mannequin which has the same or similar skin color as the customer inquiring -- This is important for the customer to judge the garment color and fabric type that will look best on them -- This is also important to make the app inclusive for people of all racial backgrounds who might use the app -- It may be best not to display the face, or if human models are used, to use pictures of models with different racial backgrounds, to avoid bizarre mismatches between facial characteristics and skin tone - The AI agent should ideally prioritize pictures of garments from our client’s website to use as inspiration when it generates renderings in the freeform conversation, along with the customer’s description of what they want. However this is not a hard requirement, so it could be eliminated from the requirements if it greatly increases devlopment effort. - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to build the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application. 12. AI asks whether the generated concept is generally what the customer wants - Customer can revise the concept conversationally 13. AI can regenerate or refine images after customer feedback 14. The tone of the conversation the AI has with the customer is important. - We will want it to speak like a friendly expert seamstress. - This requirement will be somewhat subjective and so we will need to budget time for our client to request revisions to this tone based on their review of the system. 16. We ideally want the agent (both chat and image generation) to have deep expertise about fabrics and these types of garments in general, so it can guide the user through prompts, and render the chosen fabrics correctly - I think freeform chat will be necessary for the customer to explain which fabrics should be used where on the garment, instead of gathering this informaton in the programmatic questionnaire - The customer will likely revise the fabric selections after they see the initial renderings of the garment - We would like to avoid the costs of training an AI for this, so ideally we should use commercially available AI models which have been trained for this purpose, instead of having to train our own model. Prompting the AI with this information might be a cost-effective way to teach it this expertise 17. There will be certain restrictions on what types of colors or fabrics can be used in the dress designs - So, the agent should know these restrictions when it has the freeform conversation with the customer. - For example, the store owner will not be able to produce dresses with neon colors, tie dye colors, etc. - Our client will articulate a list of restrictions for us before we begin the project. 18. AI should never display links to other websites, or suggest for the customer to navigate to other websites 19. This AI might not need to be trained specifically for this industry, but we should at least use prompting to direct it to gather this kind of information, and to give it some background about what each of these things mean, so it can describe them to the customer. We basically need to make it as knowledgable as possble while keeping costs low. 20. The AI system the system should remember their active conversation - Since the customer will be required to have an account to use the AI system we can use that to automatically save the AI conversation - The saved conversation should preserve all the information that the customer input since the beginning of the AI session - A customer can only have one active AI session at a time - The customer cannot resume an AI session that has been completed - We don't need to provide a way for the customer to see the details of completed AI sessions 21. AI should have a fallback/human-help option if the customer gets stuck or the AI fails. - The fallback should collect enough information for an admin to follow up manually, so it should present a form in order to ensure that all the necessary information gets collected - A message should be displayed above the form, or somewhere on the page, to inform the customer that the entire conversation will be sent along with the form submission, so they know that they do not have to type all the details of the AI conversation - The app must present a button outside of the chat prompts after 3 - 5 chat messages have been sent, so the customer knows they have the option to terminate the AI conversation and manually ask for help. - That button would display the form - We don't want to display the button before any conversation has happened because we don't want customers to skip the chat altogether. -- One of the business goals of this app is to allow custom inquiries without overwhelming the support staff - Site admins must have the ability to adjust how many messages the button will display after, so they can control this threshold after they observe the results of real conversations - After the button initially displays, it should remain present in the view so the customer can easily access it at any point in the conversation 22. The freeform chat must be limited to something like 50 to 75 messages, in order to avoid excessive charges from the 3rd party AI services - This threshold should be adjustable from an admin portal - If this threshold is reached during the conversation, then we should force the customer to use the fallback form from requirement #21 to submit their inquiry 23. Customer can submit the completed design inquiry when satisfied. - During the submission process, the chat must ask for the following information, and present the following pre-written messages. This doesn't actually need to be executed by the AI model, but it can just be programmatically presented to the customer: - Ask for customer contact info, including name, email, and phone number. - Ask for requested event/date, while making clear the date is not guaranteed. - Ask for seamstress-relevant measurements, including bust, waist, hips, hollow-to-hem, shoulder width, bust point, underbust, waist-to-floor, arm length, bicep, wrist, back width, torso length, height, shoe height, and preferred fit. -- I still have to refine this list with the client, I am not sure if it needs to ask for all these things, or if there are some different things that I haven't listed here which it needs to ask for -- When it asks for this information it should display links under each measurement type to articles which describe how to produce each of the measurements. We can hardcode these links or allow the admin to specify each, they don't need to be generated by AI. - Prewritten disclaimer text should display. 24. The final submission should notify a list of email addresses set by a site admin. 25. The final submission will completely consume the credit used to purchase this AI session - The AI conversation cannot be resumed after the final submission - Another credit must be purchased to start a new AI conversation - New AI conversations will not have any memory of the previous conversations, any new AI conversations will start from a clean slate 26. Admins must have the ability to manually reset a credit, or assign a credit for free and cancel a current session, so the customer can start a new AI conversation. - This doesn't need to be very user friendly for the admin. If a session is reset this way, no knowledge of the previous conversation needs to be preserved. 27. Admins should be able to review partial, or completed conversations within a list in the admin portal - Each line item should display a status indicator to show if the conversation has been submitted yet, if an admin has began the review process, or if the item has been handled: Ex. In Progress, Submitted, In Review, Awaiting Payment, Handling, Ready To Ship, Closed - Admin should be able to see the answers to the programmatic questionnaire - Admin should be able to review the full conversation history - Admin should be able to review all uploaded photos/files - Admin should be able to review all AI-generated images, and the final one should be clear to them - Admin should be able to see the collected technical design details and measurements 28. Pricing of the garment remains manual and is handled by after review, the AI should not give any quote or present any pricing even if asked by the customer. 29. If the customer asks for pricing, the AI should display a prewritten script like this: "Pricing will be determined by the store owner after this conversation has been reviewed." 30. Invoices and payment will be handled manually through native WooCommerce custom order/invoice functionality which is already present in the e-commerce site, the AI system doesn't need to handle this at all. I mentioned this above on the requirements, but I want to reiterate since it is important and a hard requirement for how the development milestones must be structured: - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to do the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application As an optional add-on to the scope of this project, can you give a separate estimate to enhance the AI such that it understands which kinds of modifications will increase or decrease the cost of producing the gown, so it can guide the customer in case they are asking for very expensive things. - It shouldn’t give any specific price numbers, but should give the customer guidance if additions or alterations will significantly increase or decrease the cost of production. - This will be to prevent the customer from being surprised when the store owner manually follows up with them with the price of the garment they designed. This client did agree to adhere to a strict schedule to provide feedback after each round of development, given that we complete each round of development on the schedule we agreed to. - However, this client has deviated from agreed schedules multiple times in the past on other projects I did with them, so you should factor that into your timeline and cost estimations - We cannot increase the development cost mid-way through the project, however we can adjust the development timeline if the client deviates from the schedule In your proposal, please also include a quote or estimate for the cost of hosting and ongoing maintenance after the app has launched - Our client can pay for the hosting directly - We will need at least ongoing updates to patch security vulnerabilities and ensure uptime of the app and all its features which will be defined by the scope of this project - We don't need a 100% 24/7 uptime SLA, but basically just keeping everything up to date so it stays stable, and we'd need someone to respond to outages within 24 hours - Outage response can consist of simple rollbacks, if necessary, as long as all the chat session info is at least provided to the client as a CSV or similar, along with all graphic assets from any conversations, so they don't lose any data from an outage - I would set the expectation with my client that we would treat any future support or enhancement requests to be additionally charged for on an as-needed basis

2. The core concept An online marketplace exclusively for verified trading card sellers (sports cards, Pokémon, Magic: The Gathering) to sell directly to buyers. Designed to recreate the feeling of browsing a real card show, online. The two features that make this different from a generic marketplace: Map-based discovery — buyers find shops via a US map with pins, not just a search bar Value box flip experience — buyers browse a seller's box of cards by flipping through them one at a time (card-back reveal, fan animation between cards), with a toggle to switch to a standard grid view Important clarification on value boxes: These are NOT mystery packs / blind boxes. Every card and its price is visible — buyers see exactly what they're getting before buying. The "flip" is purely a browsing interaction, not a gambling mechanic. 3. Business model Sellers pay a flat monthly subscription fee (target: ~$49/month, considering tiers — see below) Zero fees on individual sales — sellers keep 100% of every sale This directly undercuts eBay (13.25%/sale), Whatnot (8%/sale), and COMC (~12% all-in) Sellers are manually verified/approved before they can list — not an open marketplace. This is a core trust/quality signal for buyers. Possible future tiers: Starter ($29/mo), Pro ($49/mo), Elite ($99/mo with featured placement + priority support) — not finalized, flat single tier is fine for MVP 4. User roles Buyer Browse shops via map or category Browse a shop's inventory (flip view or grid view) Search by player, team, set Filter by price and category Save/watchlist cards Follow shops to get drop notifications Make an offer or buy now Message sellers directly Seller (verified/approved only) Apply for an account, gets manually approved Dashboard with stats: active listings, monthly sales total, open offers, follower count Upload cards via guided flow: photo → AI auto-detect details → review/edit → set price → publish Option to add a listing to a "value box" grouping or list it standalone Build and publish "drop announcements" (title, date/time, teaser text) that notify all followers Manage/respond to offers and messages Edit or delete listings Easy way for sellers to print off shipping labels. Option where sellers can put a description on each card, or just like in real life, no description needed and can put a price on the card with a photo and that’s it. Can be an option where you upload all the photos and every card in the “box” is $ per card. Easy and fast way to sell just like in real life at a card show. Jump to the top of the homepage. Different payment options for that. US map (accurate state borders, not abstract shapes) with shop pins If US map is too difficult to start with then just the seller's logo with a picture of a value box below it. Pins color-coded by category (sports / Pokémon / MTG / multi-category) Click or hover a pin shows a tooltip: shop name, city, specialty, listing count Drop announcement banners/strip at top (horizontally scrollable) Search bar (player/team/set/shop name) Category browse tiles at the bottom (Sports, Pokémon, MTG, Graded) Stats bar: total shops, total listings, live drops Shop profile / Value box browsing screen Shop header: avatar, name, city, specialty, verified badge Category tabs to filter that shop's inventory Search input + price filter dropdown + category filter dropdown Toggle between Flip view and Grid view Flip view: card stack visual (depth effect with cards behind), tap/click to flip the active card from back (VB-branded) to front (player name, set, price, condition badge, grade). Prev/next navigation with a "fan" animation. Action buttons: Buy Now, Make Offer, Save, Message Seller. Card metadata panel: condition, year, category, seller. Maybe kind of like flipping through photos on a dating app. Grid view: standard 3-4 column card grid, each card shows image/emoji, name, set, price, save heart icon Seller booth (dashboard) Header: shop avatar, name, city, verified badge, current plan/subscription status Stats row: active listings, monthly sales $, open offers, followers Drop announcement builder: title input, date picker, time picker, teaser text input, live preview of how it'll look to buyers, publish button Active listings list: thumbnail, name, meta info, price, status (Live / Offer Pending / Draft), edit/delete buttons "Add listing" button/flow: Step 1: Upload photo (camera, photo library, or bulk upload option) Step 2: AI-detected fields shown (player, year, set, grade) — powered by CollX API — with confidence score, all fields editable. Future possibility!!! Step 3: Set price, shown alongside a market price suggestion/range from CollX, toggle to add to a value box, category/team fields. Future possibility!!! Step 4: Publish (or save as draft) Step indicator showing progress through the 4-step upload flow Also needed but not yet prototyped (describe verbally / sketch if needed): Messaging/chat interface (buyer-seller threads) Offer management screen (accept/decline/counter) Watchlist screen Seller application/verification form (for new sellers applying) Buyer account settings Checkout flow (if handling payment processing for purchases, vs. just facilitating contact between buyer/seller) 6. Core functionality / logic needed User authentication with two roles (buyer / seller) Seller application + manual approval workflow (not self-serve signup) Database relationships: Users → Shops → Listings → Value Boxes; Listings ↔ Offers; Listings ↔ Messages; Shops ↔ Followers; Users ↔ Watchlist Stripe integration for recurring subscription billing (not one-time payments) Search/filter logic across multiple fields (text search + category + price range) Notification system: in-app + email when a followed shop posts a drop Map integration with custom pin placement (real lat/long coordinates, not abstract positions) Image upload and storage for card photos (Phase 2 / nice-to-have) CollX API integration for AI card detection from photos 7. Tech stack — open to recommendation, but my research points to: App builder: Bubble.io (no-code, but open to alternatives like Sharetribe or custom code if developer recommends and price works) Payments: Stripe (subscriptions) Maps: Google Maps API or Mapbox Email: Klaviyo or similar Card AI/pricing data: CollX API (Phase 2) Photo storage: Cloudinary or similar Eventual native app: Open to wrapping the web app via Median.co for App Store/Google Play once validated, rather than building native from day one 8. What I'm bringing to this meeting 3 fully interactive HTML/CSS/JS prototype files (every screen above, functional in any browser). Really don’t understand this part. Full written concept brief (features, screens, budget guidance, tech stack reasoning) Seller-facing pitch document (fee comparison math, used for recruiting sellers — shows the business model is thought through) Brand colors, fonts, and the "VB" mark already defined Domain + LLC already in place 9. Budget & timeline expectations Budget: $2,500–$4,500 for MVP (open to discussing fixed price vs. hourly) Timeline: No hard deadline, prioritizing finding the right developer over speed Phased approach preferred: Core features first (accounts, listings, map, Stripe subscriptions), flip animation and AI upload can follow as a second phase if needed to stay in budget 10. Questions I want to ask THEM in this meeting Have you built a marketplace with buyer/seller roles before? Can I see it? Have you integrated Stripe subscriptions (recurring) specifically, not just one-time checkout? How would you handle the map with custom pins — which tool/plugin, and have you done this before? How would you replicate the card flip + fan animation inside [chosen platform]? Is custom embedded code needed? What about the map idea? What's your recommended database structure for this, and does it match what I've outlined above? Will I be able to log in and manage/edit the app myself after you hand it off, or will I need you for every change? What's not included in your quote that I should expect to pay for separately (plugins, API costs, hosting)? What's your estimated timeline for an MVP with this scope? I need something that can be built and tested out for seller and buyers to use.

I’m looking to hire a product designer or UX/UI designer to help design a homeschool-focused mobile or web app. The app will include a lesson planning system, daily/weekly schedule organization, and a co-op directory where families can discover and connect with homeschool groups. I need someone who can take this concept and turn it into a clear, intuitive user experience starting with user flows and wireframes, then moving into high-fidelity UI designs and a clickable prototype (Figma preferred). The goal is to create a simple, parent-friendly platform that makes it easy to organize homeschooling and find community resources.

I am a licensed therapist building a web app that helps therapists and clients be more connected with homework throughout the week. The app was built using Lovable (an AI app builder) and I need an experienced healthcare developer to review what was built, clean it up, fix any security gaps, and confirm it meets HIPAA technical requirements. This is a startup-stage project. I am the sole founder. I need someone who can communicate clearly with a non-technical person and explain what they find and why it matters. What I Need You To Do: Review all code generated by Lovable and identify security vulnerabilities Confirm or fix data encryption at rest and in transit Review every third-party service or vendor the app connects to and flag any that would require a Business Associate Agreement (BAA) Confirm that client-entered content (homework reflections) cannot be accessed by any unauthorized party Ensure the therapist and client login system is secure and roles are properly separated Confirm that the permanent crisis support button on all client-facing screens cannot be removed, bypassed, or overridden Provide a short written summary of what you found, what you fixed, and what still needs attention What This App Does NOT Do: No billing or insurance No video or scheduling No AI responding to client content No users under 18 What I'm Looking For in You: Demonstrated experience building or auditing HIPAA-compliant SaaS applications Familiarity with BAA requirements and which vendors (cloud hosts, email services, AI APIs) typically require them Experience with web apps built on modern frameworks (React, Next.js, or similar) Ability to explain technical findings in plain English Bonus: experience with mental health, therapy, or healthcare technology specifically To Apply, Please Answer These Three Questions: 1. Describe a HIPAA-compliant project you have worked on. What was the app, what did you build or audit, and what vendors required BAAs? 2. What is your process for reviewing code built by an AI tool like Lovable or Bolt? 3. What is one common HIPAA technical safeguard that early-stage health app developers frequently miss? Applications that do not answer all three questions will not be considered. This app handles real therapy client data. I take privacy and safety seriously and I am looking for someone who does too, not just someone who can write compliant-sounding documentation. Please only apply if you have genuine healthcare tech experience.