Vibe coding and best free hosting platforms#3021
Open
aishwaripahwa12 wants to merge 24 commits into
Open
Conversation
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Messaging handles push notifications, emails, and SMS through one unified API |
Contributor
Greptile SummaryThis PR adds five new blog posts covering vibe coding workflows and free hosting platforms, all marked
Confidence Score: 5/5Safe to merge — all posts are unlisted drafts with no breaking changes to existing routes or site infrastructure. The changes are purely additive content files with no logic, routing changes, or shared infrastructure affected. All five posts are gated behind unlisted: true so they won't surface publicly until intentionally enabled. The only finding is an editorial duplication within one article that has no impact on rendering or site correctness. The 'where vibe coding stalls' section in how-developers-are-shipping-apps-10x-faster-with-vibe-coding/+page.markdoc has a duplicate bullet worth trimming before the post goes live. Important Files Changed
Reviews (16): Last reviewed commit: "Apply suggestion from @atharvadeosthale" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
…havent-tried-in-2026/+page.markdoc Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
…havent-tried-in-2026/+page.markdoc Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
adityaoberai
requested changes
May 26, 2026
Comment on lines
+88
to
+92
| ## 8. Claude Code | ||
|
|
||
| Claude Code is Anthropic's agentic coding tool that started in the terminal and now works across the terminal, IDE, desktop app, and browser. The terminal sounds intimidating, but the experience is closer to texting a senior engineer than writing shell commands. It reads your repo, makes changes, runs tests, and explains what it did in plain English. | ||
|
|
||
| Best for: beginners who want to learn the command line through guided practice rather than dry tutorials. |
Contributor
There was a problem hiding this comment.
I'd bring Claude Code to the top and add Codex and OpenCode too
|
|
||
| A short checklist for developers picking up the workflow now: | ||
|
|
||
| * **Pick one AI assistant and learn it deeply.** Switching between five tools costs more than picking one and using it for a month. Claude Code and Cursor are both excellent starting points. |
Contributor
There was a problem hiding this comment.
I don't there's that much of a learning step
Better advice would be to understand which assistant does what better, but that's my opinion
|
|
||
| The tools developers reach for have settled into a small number of categories. The list below covers what shows up most in real workflows: | ||
|
|
||
| * **Coding assistants.** Claude Code and Cursor are two of the most visible tools in this category. Both let you describe changes in plain English and apply them across a codebase. GitHub Copilot stays strong for in editor autocomplete. The difference between "assistant" and "agent" matters here. Assistants help you write. Agents go off and do. |
|
|
||
| * **Coding assistants.** Claude Code and Cursor are two of the most visible tools in this category. Both let you describe changes in plain English and apply them across a codebase. GitHub Copilot stays strong for in editor autocomplete. The difference between "assistant" and "agent" matters here. Assistants help you write. Agents go off and do. | ||
| * **App generators.** v0, Bolt, Lovable, and Replit Agent take a higher level prompt and return a working app. They are excellent for the first 80 percent of a project. The last 20 percent still belongs to a human in a real editor. | ||
| * **Design to code.** Tools like v0 and Magic Patterns close the gap between Figma and a working frontend. The output is usually React or Vue with sensible defaults. |
Contributor
There was a problem hiding this comment.
Claude Design and Figma Make?
| * **Coding assistants.** Claude Code and Cursor are two of the most visible tools in this category. Both let you describe changes in plain English and apply them across a codebase. GitHub Copilot stays strong for in editor autocomplete. The difference between "assistant" and "agent" matters here. Assistants help you write. Agents go off and do. | ||
| * **App generators.** v0, Bolt, Lovable, and Replit Agent take a higher level prompt and return a working app. They are excellent for the first 80 percent of a project. The last 20 percent still belongs to a human in a real editor. | ||
| * **Design to code.** Tools like v0 and Magic Patterns close the gap between Figma and a working frontend. The output is usually React or Vue with sensible defaults. | ||
| * **Backend and database.** This is the layer most vibe coding tools cannot fully generate, because the choices here have consequences that compound. Appwrite, Supabase, and Firebase are the platforms developers pair with their AI generated frontends. |
Contributor
There was a problem hiding this comment.
Let's just have Appwrite in here
| * **App generators.** v0, Bolt, Lovable, and Replit Agent take a higher level prompt and return a working app. They are excellent for the first 80 percent of a project. The last 20 percent still belongs to a human in a real editor. | ||
| * **Design to code.** Tools like v0 and Magic Patterns close the gap between Figma and a working frontend. The output is usually React or Vue with sensible defaults. | ||
| * **Backend and database.** This is the layer most vibe coding tools cannot fully generate, because the choices here have consequences that compound. Appwrite, Supabase, and Firebase are the platforms developers pair with their AI generated frontends. | ||
| * **Deployment.** Vercel, Netlify, Cloudflare Pages, and Appwrite Sites handle the deploy on push side of the loop. The shorter your deploy time, the more iterations you get in a day. |
Contributor
There was a problem hiding this comment.
Appwrite Sites should be first
Comment on lines
+89
to
+91
| The single biggest predictor of whether a vibe coded project survives past the prototype stage is what the developer chooses for the parts they do not generate. | ||
|
|
||
| Authentication is a good example. You can ask an AI to generate a login system. It will produce something that works in the happy path and fails in interesting ways at the edges. Session management, password reset flows, OAuth integrations, multi factor auth, account recovery. Each one is a known problem with known solutions, and reinventing them costs you weeks you do not have. |
Contributor
There was a problem hiding this comment.
Not sure if some of these problems are as prevalent with newer models
I'd rather be more nuanced, talk about how these issues occur at times due to a lack of planning
Contributor
|
We also need to ensure that Appwrite fits in more naturally in the conversation. Like if we talk about specific products like Sites, linking those make sense. Similarly, there are no mentions of our AI integrations and flows that would be a given in these |
Merged
Vibe coding blogs
adityaoberai
requested changes
May 26, 2026
Comment on lines
+113
to
+117
| The fastest vibe coders in 2026 share one thing in common. They do not waste cycles on infrastructure. They keep their AI focused on what makes their product unique, and they let a backend platform handle the rest. | ||
|
|
||
| That is exactly what Appwrite is built for. Auth, databases, storage, functions, messaging, and realtime, all available through a single SDK that your AI assistant already understands. Prompts like "add Google login," "store the user's avatar," or "send a welcome email" translate directly into Appwrite SDK calls, with no infrastructure setup required. | ||
|
|
||
| Appwrite is open source, self hostable, and built for developers who want to ship fast without surrendering control. Whether you are building a side project on a weekend or scaling a serious product, the platform stays out of your way and lets your AI assistant do its best work. |
Contributor
There was a problem hiding this comment.
we should be talking more about our AI integrations too
Comment on lines
+90
to
+94
| # Start vibe coding with Appwrite | ||
|
|
||
| Vibe coding only works when your backend works with you. Appwrite gives you auth, databases, storage, functions, real time, and messaging in one platform that AI assistants speak fluently. Clean SDKs, predictable APIs, and documentation that models can read without getting lost. | ||
|
|
||
| Sign up for [Appwrite Cloud](https://cloud.appwrite.io/) or spin up a self hosted instance in minutes, and let your next idea ship at the speed your AI can actually keep up with. |
Contributor
There was a problem hiding this comment.
We need to talk about our AI integrations
adityaoberai
requested changes
May 28, 2026
|
|
||
| Vibe coding only works when your backend works with you. Appwrite gives you auth, databases, storage, functions, real-time, and messaging in one platform that AI assistants speak fluently. Clean SDKs, predictable APIs, and documentation that models can read without getting lost. | ||
|
|
||
| And if you are already coding with Claude or Codex, the [Appwrite plugin for Claude Code](https://appwrite.io/integrations) and the [Appwrite plugin for Codex](https://appwrite.io/blog/post/announcing-appwrite-codex-plugin) drop our MCP servers and SDK skills straight into your editor, so your assistant can talk to Appwrite directly instead of guessing at it. |
Contributor
There was a problem hiding this comment.
we should also link our MCP server docs, our skills docs, and AGENTS.md generator
goes for all blogs that currently have a section covering Appwrite's AI offerings
|
|
||
| The takeaway is not that vibe coding stops working past a certain point. The takeaway is that the parts of the stack where the cost of being wrong is high are exactly the parts where you should reach for battle tested infrastructure rather than generated code. | ||
|
|
||
| # The infrastructure question |
Contributor
There was a problem hiding this comment.
Titles like this don't make sense on the first look and are bad for AEO
They need to represent the section better, not just vaguely
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Updated content to enhance clarity and added links to resources for Appwrite plugins and tools.
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
3 new latest blogs