Something we ve been thinking about a lot at @Fine:

We ve entered an era where software is starting to behave like content.

We launched Fine Feed today, and I wanted to share a bit of the thinking behind it.

A lot of tools today focus on building big apps, polished platforms, or things meant to scale. And that s great. But what about apps that don t need to live forever?

Hey folks!

We just launched @Fine Feed today

Hey folks!

At Fine we're experimenting with a new kind of build mindset:

Don t launch. Don t maintain. Just solve.

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

I started using Replit about 3 weeks ago. First on a trial basis and then decided to pay the quite ok monthly fee of $25. What I didn't realize back then was that once they got my credit card info they just keep charging for use even if cancel my sub.

The thing is that Replit charges 'checkpoints' a 25 cents each no matter what it does. Implementing Google Auth with 2FA or failing over and over again to format an output i Typescript, same result. The checkpoints just runs away. When the AI fails to solve a very basic variable naming problem for the Xth time you tend to get a bit frustrated - to say the least. Tell the AI to mind the difference between CamelCase and snake_case and it remembers it for less than 5 minutes. Putting it in writing in the manifest Instructions.md makes no difference.

After about a week I decided to make a first deployment. The AI ran all sorts of test and then deployed. Successfully in its own words. Except not a single endpoint worked in deployment. Not even logging in to the Express backend as admin. So I asked the AI if it thought it was ok that code that worked in the Replit dev env did not work in their own deployment env (based on Google Cloud). It wasn't. So I sent a mail to support. Which yielded absolutely nothing but a boilerplats BS answer. You see, the support too is an AI. How clever is that!

Hey fellow makers!

Jonathan here from @Fine .

Hey fellow makers!

Jonathan here from @Fine .

Hey Friends!

Jonathan here, the cofounder of @Fine.

Hey Friends!

Jonathan here, the cofounder of @Fine .

I started using Replit about 3 weeks ago. First on a trial basis and then decided to pay the quite ok monthly fee of $25. What I didn't realize back then was that once they got my credit card info they just keep charging for use even if cancel my sub.

The thing is that Replit charges 'checkpoints' a 25 cents each no matter what it does. Implementing Google Auth with 2FA or failing over and over again to format an output i Typescript, same result. The checkpoints just runs away. When the AI fails to solve a very basic variable naming problem for the Xth time you tend to get a bit frustrated - to say the least. Tell the AI to mind the difference between CamelCase and snake_case and it remembers it for less than 5 minutes. Putting it in writing in the manifest Instructions.md makes no difference.

After about a week I decided to make a first deployment. The AI ran all sorts of test and then deployed. Successfully in its own words. Except not a single endpoint worked in deployment. Not even logging in to the Express backend as admin. So I asked the AI if it thought it was ok that code that worked in the Replit dev env did not work in their own deployment env (based on Google Cloud). It wasn't. So I sent a mail to support. Which yielded absolutely nothing but a boilerplats BS answer. You see, the support too is an AI. How clever is that!

I'm learning (slowly) about the importance of marketing your product. (I am probably one of todays 10,000 around guerrilla marketing)
So last night I hacked together https://purposefulpoop.com/ to see if it could drive some leads for my product.
I'm going to launch the playful tool next monday and use this thread to give a plot synopsis on how it all goes.

Prior to launch though, I'm curious if anyone has any feedback that might make the hook stronger?
I added (a poorly designed) OG image, so the shareable is at least somewhat tasteful:

What else am I missing?

Hey everyone!

At Fine, we ve been deep in the AI-building space, helping people create fully functional apps from a simple prompt.

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.