Build full-stack MVP web & mobile Apps

This is a short-term project (3-6 months) building MVP (minimum viable product) applications. For the sake of good communication, this job is only available to moderate, fluent, and native English speakers. Before getting started, you do not need to have a strong coding foundation, but you do need to have the following already set up: 1. GitHub 2. IDE (VS Code, Cursor, Vim, etc) 3. LLM to speed up development (optional). 4. You have a basic understanding of JavaScript, React, and/or Next.js The goal here is as follows: -Build 0 to 1 full-stack applications as quickly and professionally as possible -The type of applications you build can vary in range and diversity. -Acceptable platforms: ios, android, chrome extensions, web applications, blogs, professional local industry style websites (for Doctors, lawyers, construction). The sky is the limit. Judgment Criteria: (not everything here will always be needed) -App should be able to go live, leaving the new owner with little to no technical duties (create OAuth account, Stripe account, Changing .env keys and other 3rd party tools you include) -App can be monolithic or headless, but no micro-services. -App should have a backend and connect to the database (we will provide DB details for you) -Standard network security, like authentication, authorization, and rate-limiting --Existing apps that you want to submit are also acceptable. Note: There is no training, there is no how-to documentation. This task is for people who already know how to do this. If you're hired, and we have to constantly guide you on a fundamental level, it won't work out. Questions that tell us, you might not be capable: - "How do I set up and push to GitHub?" - "How do I set up Google OAuth? It's confusing." Technical questions are always welcome: - "How many lines of code can I change before a push?" - This is good because pushing code with clean commits makes life easier for everyone who isn't you, or you're LLM :) - "I want to trigger an API call on load, but I feel like I don't need to use useEffect() as much as the LLM is suggesting. You think it's cool to remove it?" - This is good because most LLMs use useEffect as a go-to instead of as a last resort, which can be largely problematic down the road if you're not careful. Being able to make this assessment on a case-by-case basis shows you have a strong foundation.