I’ve now been working on my new (and very exciting) Supernatural Science App project for the few couple weeks. It’s been a fascinating process which has required a fairly steep learning curve and unexpectedly, several complex decisions that have long term ramifications. In the midst of all that, I had two dreams that showed something about the very complicated process of making those critical decisions about short and long-term app features.

The dreams took a few days to really sort out but the day came when I was faced with making some decisions that would not be reversible. If you’d like a behind the scenes look at how the supernatural and science elements come together in this app development project, keep reading — I believe you’re going to find this very interesting…

The Plan That Seemed Obvious

I want to tell you about a few decisions that, if I’d gotten it wrong, could have quickly led to a train wreck. One of the hardest decisions involved which app-building platform to build on — and I quickly learned there wasn’t a single “all of the above” answer. I ended up choosing a dual-track approach: two separate app building platforms that each give very different results. Here’s the short version:

1. Base44 is an AI-driven app building website which gets a real, working version of the app live and in people’s hands now, and very fast — but it has a ceiling on how deep the features can eventually go.
2. FlutterFlow is a very complex AI-assisted manual builder which provides the long-term build underneath it — a much steeper climb, but it’s where the full vision, with every feature fully functioning the way I actually want it to work, ultimately lives.

Base44 proves the concept works, but FlutterFlow is where the app becomes what it’s meant to be.

A Feature-Driven App

Early on, there were several features I was most excited about. One of those was a page where you can record your dreams and keep them in a backed up storage file. The way this would work is that you could instantly look up specific symbols in your dream using my own online dream dictionary. If you didn’t get the answer there, you would have various contact options to ask me for more help.

Another feature I wanted was in-app push notifications. This was critical because I wanted this app to feel personalized — with instant feedback when a new message was sent to the user based either on an important update or an answer to a question sent to me.

In addition to that, I wanted a smart search feature that would allow you to look up answers to your questions in the already existing content in my 430+ blog posts and any ebooks you may have purchased by loading them into the app.

I wanted this app to be something that would be noticeably better than just visiting my website — something that would exist on your phone without having to go to a website every time you had a question.

Ultimately, the plan is to put this app in both App Stores (Apple and Google Play) and yet one of the platform choices for building this app might have made that difficult.

Why I Am Using A Dual-Build Process

In the last couple weeks since I began this project, I started to realize that I unexpectedly walked into an advanced-level educational program. Base44 was super easy to use but then I felt the need to begin researching the long-term success probability based on all the features I wanted the app to have. As I worked through the very complex app-building world, I began finding some very big challenges which I had no solution for. After much debating back and forth and further research into the options, I came to the conclusion that I needed a dual app build process.

The challenges were very real and it felt like mentally climbing straight up a massive mountain cliff. Thankfully, I began to realize that the solution wasn’t to shut the door on the project and give up. The key was to use existing resources and plan to use both app-building processes simultaneously. What worked on Base44 could be transferred to FlutterFlow (although not as easy as it sounds by any means).

Several Recent Dreams About The Project

Here is now where the supernatural element meets with science. In the midst of working through all sorts of design decisions, I had several dreams that took me a few days to sort out. Each of them showed me something about this exact process I’m writing about in this post today and when I figured out the meaning of each, I knew there were significant design details I had to reconsider before I signed myself up for something I couldn’t deliver on.

These dreams took place on more than one night but grouped together in a very unusual way. Most of the time, I get several dreams on the same night, but they are not usually on the same topic. For these app-building dreams, I had two or more of them on the same night — that’s how I realized the level of criticality of what God was showing me in each of them.

Dream 1: Climbing A Complex Building Wall

September 14, 2026 – I’m with some people climbing up a wall on the inside of a building. It’s like we were rock climbing but inside the building where the climbing surface is made up of all building maintenance related parts like pipes, conduits and plastic boxes for meters of all sorts, etc (the things not visible to most people). One section of the climb was dangerous and it felt like it was too easy to fall. I jumped over and landed on a set of meters without falling but doing that made me nervous. We all kept climbing until we got to the top.

This dream is about my app building project (specifically regarding FlutterFlow). The complex series of pipes, conduits and meters represents all the behind-the-scenes inner workings of my app, which most people will never see. The other people climbing with me most likely represent those who accept my invitation to join my development team and support this project. The potential danger of falling represents the design decisions which, depending on how well they are made, could have a positive or negative result for the final app product.

The pipes represent all the workflows that cause each element of the app to work together. The meters represent each area where some kind of decision must be made to determine which direction to go in with the features development. Climbing represents making progress through a challenging personal effort where skill and careful planning is required (that’s why God used the combined illustration of rock climbing and building maintenance elements).

The main point to this dream is that there are critical stages of decisions that must be thoroughly thought through in order for this project to be a success. As long as those decisions are made with careful consideration, this app will turn out very well.

Dream 2: A Drone Design Limitation

September 14, 2026 – I’m outside on a sunny blue sky day. One of my friends has his desktop computer hooked up to a drone contraption with a power cord connecting it to a ground base on a table. He’s flying it nearby and it’s going ok until someone said something and he got too excited about what was happening. In his excitement, he apparently forgot about the rather short power cord and allows the contraption to exceed the limits of the cord and it snaps off. Instead of the contraption crashing right there, it keeps flying away and high up in the air. My friend brings it back around in a big circle hopefully to land. Unfortunately he lets it go off again into the distance before he brings it back around a second time, but this time it makes a “rapid unscheduled disassembly” with the parts flying off in all directions and the whole thing crashes into the ground in a way that most likely destroys the computer. 

This dream represents a specific part of my app project, where the drone contraption is the piecing together of components in such a way where a serious limitation can exist. The big heavy desktop computer represents my lack of ability to handle a heavy-lifting effort by trying to do too much all at once. The short power cord represents a limitation which must be acknowledged and adhered to regarding my ability to keep up with where this project could go. The friend is someone who, in real life, is a website developer (which in this context, represents myself) and pointed most directly at the immense challenges of using the FlutterFlow app builder.

While the dream is a warning of a potential disaster, there is actually a solution when you take the time to look farther into it. The solution is what I’ve been chatting with my AI assistant about — to make sure my app design does not exceed my own personal limitations (not just now, but in the future as well). If you were to replace the big heavy desktop computer with something the size of an iPhone, the “drone” would not be trying to do something it can’t.

This is exactly the tension behind my platform decision too. Base44 lets me get a real version of this app running fast — proof the whole idea works — but like the desktop computer on that short cord, it has a ceiling I’ll eventually run into if I try to push every feature through it. FlutterFlow is the much harder, slower build — the “iPhone-sized” version of the same idea — built to handle the full weight of where this app is ultimately going, without snapping under it.

The point here is that God used this odd illustration to give some app-building wisdom for the purpose of making sure this project becomes a great success.

I found it very interesting that He gave me both of these dreams on the same night and I took from that He’s wanting me to make sure this app is very successful. But that is only two of several dreams I had about this! My other dreams also had a consistent theme and pointed to a limitation which needed to be corrected in a way I will tell you about below.

If you’re wondering about when I had the dream where God gave me the idea for this app, it’s in this blog I just posted recently linked here (ref the new white iPhone battery)…

3 Great Dreams Of Overcoming Adverse Circumstances (Skiing On Snowless Mountain, A Lawyer, New iPhone Battery)

Why I’m Telling You This

I could have just quietly shipped the “faster” version of this app only on Base44 and never mentioned the long-term limitations. But I knew I couldn’t settle for a faster, cheaper build at the cost of the full vision. So that’s why I wanted to give you this update — to let you know that progress is very much moving forward but in a very different direction than I initially expected.

There is a way to short-cut the FlutterFlow app building process and that’s why I wanted to again give you my invitation to my “app development team”. The faster way to get this app deployed on FlutterFlow is by donations to pay for the AI-assist feature. It’s not that expensive in the big scheme of things but it is also not something I can pay myself at this time. Since I want this to benefit my readers, it is only sensible to ask for support in this project.

Most of what I do here is fully paid by myself and that is really not Biblical. When people benefit from the work I do, donations are the proper response. Nothing in this world, or in the spiritual realm, is free. Jesus had to pay for our salvation and we are required to “buy” from God in ways that most of the church knows nothing about.

By the way, I’m happy to share the details of this process for those who accept my invitation to join my development team. Most of the technical behind-the-scenes data and details about design decisions are available exclusively to those who want to support my efforts and give meaningful feedback to help me get this done.

If you’d like a closer look at how these decisions get made — or want to weigh in on future ones — I’m happy to share more with anyone interested in following along more closely. If that’s you, use the link in the promo image below…

— Chris Michals
The Supernatural Scientist

Contact!

---