Skip to main content

Vibe Coding with GitHub Spark: From idea to app in minutes

There are multiple platforms available to support you in your vibe coding experience. I mostly used bolt.new but also experimented with lovable.dev and v0.app. But did you know that Github has there own vibe coding platform?

Time to give Github Spark a try…

Enter GitHub Spark

GitHub Spark, it's an AI development platform that converts plain English descriptions into complete, deployable full-stack applications. And I do mean complete—frontend, backend, authentication, database, hosting, the works.

Its main focus is simplicity, allowing you to create simple applications without having to worry about all the technical details.

Let’s dig into some of the features it has to offer.

Pure natural language development

The starting point is the same as with any of the other available platforms. You can enter a prompt that describes what you want.

"I want to create mobile friendly 7 minutes workout app.."

That's it. No setup, no configuration, no choosing between frameworks. Spark handles everything.

Spark starts its magic and spits out a working application after some minutes.

Specification driven

A nice functionality of GitHub Spark is that it creates a PRD markdown file with the specifications of your application. If you later ask to add some extra features, the markdown file is updated as well.

Real-Time Preview

As Spark generates your application, you see it come to life in real-time. The live preview updates instantly, showing you exactly what's being built. This is not different compared to any of the other platforms but still a must have.

 

Three Ways to Work

Spark adapts to your skill level:

  • Pure vibe coding: Use natural language prompts exclusively
  • Visual editing: Adjust UI elements with visual controls
  • Direct coding: Dive into the code editor with Copilot assistance

It is very easy to switch between the 3 modes allowing you to choose what is most appropriate.

Some remarks I got when trying Spark:

  • It only seems to know React and Typescript (which doesn’t have to be a problem).
  • The model used seems a little outdated as it got stuck on some rather obvious changes I asked it to make where most coding models don’t struggle with.
    • E.g. Add support for PWA to this application
  • There seems a lot of reasoning involved when using the model. But I noticed that it got stuck a few times. As the train-of-thought is shared during the process, I was able to interrupt and bring the AI back on the right track in some situations.

Other features

Spark offers some other features worth exploring but I’ll leave that for a follow up post tomorrow.

More information

GitHub Spark · Dream it. See it. Ship it. 

Building and deploying AI-powered apps with GitHub Spark - GitHub Docs

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more