[2:45 pm: Awaiting completion of ship upgrades while enjoying a bowl of ramen.]

According to Coaching No Code Apps, there are a few reasons I should NOT use a template.

Reason #1: I'd be opposed to rebuilding the app at some point because I created a kludge.

I kinda meet this criterion because I don't like the idea of starting over, and I don't know the inner workings of Bubble.io well enough to be confident that I'll put things together in the best way possible. If I use a template, it would form the core of The Pathwooded Word Count Tracker, and I want to understand that core well enough to customize it and build on top of it.

Coaching No Code Apps seems to suggest that given my beginner-level skill, using a template automatically makes it hard to understand that core, but can't I learn about it by peeking under the hood? At least learn enough not to screw things up badly?

As I mentioned in the previous post, I could build decent websites with Webflow templates by peeking under the hood at how the template designer implemented distinct features and copying what they did. Maybe I can do that with Bubble.io.

Reason #2: I only want to launch faster.

It may be faster to start from scratch because I'll have a better understanding of how things fit together.

‍

Accounting for all this, it seems the only advantage in using a template, given my skill level and goals, is to learn from it. I'd have a model to play and tinker with.

Tinker shminker.

I'm all for experimenting, but I'm also for getting something out there fast and not having to backtrack.

Scratch it is.

‍