- Tubelator AI
- >
- Videos
- >
- People & Blogs
- >
- How to Build an AI Teaching Assistant with BuildShip, FlutterFlow, and ChatGPT API
How to Build an AI Teaching Assistant with BuildShip, FlutterFlow, and ChatGPT API
Learn how to create an AI teaching assistant using BuildShip, FlutterFlow, and ChatGPT API. Dive into understanding APIs fundamentally for better utilization in your application development. Gain insights and advantage from experienced developers to enhance your no-code tool utilization.
Install Tubelator On Chrome
Video Summary & Chapters
No chapters for this video generated yet.
Video Transcript
Build ship, build ship, build ship.
That's all I've been hearing from y'all lately.
And now we're gonna dive in and start our tutorial
on how to use build ship to create APIs
for your application.
But before I jump in, I want to cover APIs fundamentally
so that you understand what an API is, how an API works,
so that when you're using an API builder like build ship,
you know what's going on under the hood
and you're not treating it like magic.
That's why myself and my team have been so successful using no code tools like Flutterflow and Buildship is because we've come from
over 30 years of combined experience
building full stack software by hand and that's why I think we have an
Advantage in using these tools. So before we go on I'm gonna give you that advantage by jumping in just for two minutes and giving
You an insight into what an API is at the fundamental level. So let's jump in and explore. What is an API?
All right, so APIs are the building blocks of the internet.
They're responsible for...
for handling the underlying business logic
of an application.
And in layman terms, what that means is
when you click a button on an application,
you are triggering an API request to a server.
So your front end is talking to another server
via an API request.
Think of an API request as a waiter at a restaurant.
Your waiter comes to your table
and the table is your front end.
The front end tells the waiter what they want to order.
In this case, it's a piece of data.
The waiter goes to the back end,
which is the back of the restaurant, the cook,
tells the cook what to make and
then brings that food back to the front end.
So an API is the waiter.
It's the vehicle between a front end
and the server which is handling the data.
So the server is responsible for accepting the request,
such as the order,
processing the data,
and then returning the data back to the front end.
As mentioned in my previous video about Buildchip,
But your API normally is responsible for getting that data.
Nowadays with no code tools like Flutter Flow, we're integrating Firebase, Firestore, or
Superbase directly into our front end.
So our front end is becoming coupled with the data.
However, traditionally we would be using APIs to manipulate that data.
And now with a tool called Buildship, we're able to actually manipulate that data using
a backend decoupled service so that we can tap into triggers and we'll get into that
more later.
But what you need to know for the purpose of this lesson is that your server is responsible for accepting the request
