Front-end vs Back-end
Slowly but surely - I know how to make posts :) Get caught up with our series:
How I use "ai" to build things (on HIVE)
I created an opinionated price feed widget - and got blocked by Google
Private vs Public Repos - Learning about GitHub
End to End: F2B or B2F?
Today we are going to talk about an important and classic subject in development, with our new modern spin of using automated "intelligence" to build things. While our agents have vast oceans of knowledge to put at our disposal, our role as prioritizing force requires us to have some grasp on the basic substructures of the universe - and this includes the fact that inevitably, every project has (at least) two "ends".
Let's first take a look at this widget I coded up earlier this year to help myself and others burn dCityNFTs:

https://alextrapp.github.io/burnDcity/
This is the classic "my first blockchain app", and if we break it down:
- Front-end: My code, thanks claude
- Back-end: Hive blocks, Hive-Engine side chain nft contract
- Hosting (Delivery): Github pages
"Recently" with the advent of javascript, more and more can be done in the browser, using the the users own computer to process, hold and mutate the data. By using blockchain api's or other public api's - the advent of free hosting like github pages and Vercel has increased the power of "front-end only" applications.
And yes - it should not escape our attention that there is a "secret" -end, the delivery/hosting end handled by a service or sysadmin. This can sometimes be conflated into backend (but mostly by front-end forward developers).
And don't get me wrong - front-end only apps are powerful, especially when you include the possibility to custom-make bespoke applications with AI for an individual user - leveraging "localhost" self-hosting for easy local delivery.
But surely you might already be able to see - we are just scratching the surface of "building"; adding user interfaces for ai-assisted scripting is only one kind of shape in the world of "code".
Back, Back, Back It Up
Obviously, there is a reason that back-ends exist, even if those reasons might not be immediately obvious.
Suffice it to say, back-ends are so useful they even made some public ones called "blockchains" that are used for all sorts of different types of information storage - but not all site-specific storage can live in a public blockchain; the nuances really depend on "what are you trying to do?".
And yes, in the end - what a back-end "does" is store data - things like user data. A table with userdata that is "always on".
Is that it?
This is the next step up the ladder - and a perfect split for collaborative teamwork. Having and maintaining a backend is an additional and multiplicative layer of complexity - but nothing that can't be handled if the workflows are set up in the right way and the operators grow in their holistic understanding of how things fit together.
And it does matter - even on blockchain. Take one of my favorite HIVE tools as an example: The "TAO" - or Thematic Art Organizer.

Now, theoretically we are able to "ask the blockchain" for all our old posts - but its not fast, in fact its really pretty slow especially if you have posts going back many, many years (cf: HIVE Memories). It might surprise all the nascent blockchain developers - we don't even ask the blockchain at all in the TAO.
That's right - we built a backend! Specially designed to have, filter and deliver the posts of a user in a reasonable amount of time (the continuous and main critique of HIVE Memories - wasn't the code, it was the limitations of the way it was built); we lovingly call it "The Stuffer". HIVE Memories was never going to work as a front-end only app - but to show you that I had to build it (or have it built - thanks @spiritsurge and team!). Did you all learn something?
Now many of you may know I have been working and playing with @thecrazygm for many years now - he is my "sysadmin" (and friend), and generally - naturally perhaps - we do tend to split the work right around this division, between front-end and back-end.
Now, there always end up being a lot more "ends", but this is directional - they split off and head in different directions.
Back-end -> Sysadmin -> Infrastructure
Front-end -> UI/UX -> Customer Service
What's next?
Now that we are defining the layers and splitting out the bits - the next post in the series means to be one about collaboration. Collaborating with agents, and people; Other people with their agents. Follow along to keep learning about "anyone can build" attitudes and strategies on HIVE and elsewhere in the golden age of tokens. The golden age might not last forever, but the future will be marked by the new tools being developed.
I collaborate perhaps more than many - and I am eager to show you some of the things I have been working on and the strategies and techniques that have proven effective (and maybe even some that haven't).
Like and subscribe!!