It’s been nearly four weeks since I started working on my very exciting Supernatural Science App project and much has developed since I took the first steps! This is my top project right now and not a day goes by that I’m not working on all the necessary details to get this app fully ready for App Store deployment. As you know, I have an invitation for all to join my “development / supporters team” and that is where I post the majority of the behind-the-scenes details which I do not tell publicly. Having said that, the way to encourage more people to join my team is to post certain updates here in my blogs. If you’d like to know the latest publicly releasable updates, keep reading here…

Behind The Scenes Details

At the time of this post, I have at least 10 messages in my private development team member board. In those messages, I give the current link to the progressive web app (PWA) in its current form, I tell more about the dual aspect of my app project and give regular updates about all the decisions that must be made regarding layouts, backend connections, user profiles, true native app versus web-wrapper issues, how push notifications will need to be connected and how app updates in the Google Play and Apple App Stores will push to users. There’s quite a lot there and every couple days or so, I post new updates.

It’s really a fun project and definitely not without its challenges! If you look at this blog post’s featured image, you start to get an idea of how this app developed from a very basic sketched out drawing into one with more and more detail. If you’re a long time follower of mine, you know I do a lot of digital artwork which can be found on my Gumroad digital store. The designs you see in the last several blog updates about this project are made in the same manner — using the same sketch app where I can draw out what I want the app to look like, then show my artificial intelligence assistant which then creates instructions for the next stage of the app build.

I have done everything here as inexpensively as possible which has unfortunately resulted in many delays to this project. Those familiar with my story know that money is scarce in my world and even $40 for a monthly AI app builder plan is totally out of my reach. SAD BUT TRUE. That’s how it’s been for me for most of the last 11 years and the reasons for that are fully discussed in my ongoing series, The Secret Life of A Supernatural Entrepreneur. But… my long austere road is all going towards a VERY BIG destination and that’s the reason why things have been so impossible for me in the money realm. God severely tests and trains His top people which is what I extensively speak about in my series.

Creating Backend Connections (not easy!)

For this update, I want to briefly tell you about the features that will make this app work as advertised. To do that, I need to give you a little behind-the-scenes glimpse of what I post in my team membership board.

One of the top challenges of getting an app built is the backend connections. By that, I mean things like creating a database setup where user profiles can be stored, then linked back to the app so it remembers the user each time they open the app. I’m guessing for the average person, you never thought about what goes into making sure something like this actually works. The typical app user only knows that they open an app, sign in with a log in, add their user information and from that point on, everything just magically works. NOT SO in real life!

Building an app requires a TON of backend connections which require a database to have separate entries for things like “userid”, “name”, “lastname”, “datecreated”, “email” and much more. If you’re using an AI-driven app builder like Base44, this is done for you, but not without a ton of manual checking to make sure it actually works. If you’re using a manual app builder like FlutterFlow, you have to manually create every single data entry item in a Firebase account and then manually link it to each and every page that your app user will interact with.

When I first tried doing this manually on FlutterFlow, I just about had a mental breakdown. I’m not a computer programmer or coder and I don’t necessarily have a great ability to handle an intense level of techie computer details. The first day I worked on my app using FlutterFlow, I spent about 12 hours before my brain finally could no longer think straight about anything. That was the day I realized my recent dreams that warned me about how hard this would be were playing out.

Dual Artificial Intelligence Assistants for App Building

Some of you may know that, in order to work within my extremely limited financial constraints, I had the brilliant idea to combine two separate AI assistants to help me get this app done. That has worked very well. Despite the outward appearance of the current PWA version looking very behind the power curve compared to my sketches, there’s actually much more progress being made.

Here’s how I chose to employ the two AI’s… I use one AI (like Claude or Grok) to draft the instructions that I can paste in to the Base44 app builder. Claude figures everything out so I don’t have to use up my extremely limited Base44 AI credits too fast. Once I have the very specific instructions ready (and prototyped in Claude), then Base44 does the actual build in the most efficient manner possible.

My limit here is dual in that I run into AI limits on two fronts: Claude and Base44. Claude gets me much farther down the road than Base44 so I do most of my behind-the-scenes work with Claude. When I’m able to make progress on Base44 (when AI limits reset), then the actual app begins to catch up on everything I worked on with Claude.

Does any of this make sense? It’s a little complicated, especially if you’ve never done anything like this before.

Actual AI Prompts

Now that I’ve given you a little peek at what this process involves, here’s an actual snippet of one prompt I got from Claude which I then pasted into Base44 word for word. Once Base44 received this, it went about implementing the instructions and adding the backend functions that my app will need.

Please implement the following, building on the homepage already in place:

1. PWA + NOTIFICATIONS

• Make sure the app is configured as an installable Progressive Web App (manifest, service worker, “Add to Home Screen” support on both iOS and Android).
• Enable push notifications for the PWA. Set up a notification type for gentle re-engagement reminders (e.g., “Don’t forget to log last night’s dream”) that can be sent to users who haven’t opened the app in a few days.

2. USER ACCOUNTS

• Add sign-up and login (email-based is fine to start; social login optional if easy to add).
• Require login before using: Dream Journal, My Library (saved/favorited items), and Contact.
• Dream Dictionary and Smart Search should remain usable without logging in.
• Once logged in, use the account’s first name for the homepage’s personalized greeting (“Good morning, [name]!”) instead of a placeholder.

3. DREAM JOURNAL — SERVER-SYNCED

• Journal entries (title, description, date, any tagged symbols) should save to the user’s account on the backend, not just local browser storage — so entries sync across devices and aren’t at risk if local browser storage gets cleared.
• Include a manual “Export journal” button that generates a dated JSON file (e.g., “dream-journal-2026-09-08.json”) containing all entries, and downloads it directly to the user’s device with a single tap (no file-picker dialog needed for saving).

4. BACKUP SAFETY NET

• Automatically trigger the same journal export (as a background/low-friction action, not a full workflow) once per day if the user has the app open and there are new entries since the last backup.
• If the app ever loads and finds the logged-in user’s journal unexpectedly empty (e.g., sync failed or local cache issue), show a friendly message: “Looks like something went wrong loading your journal — you can restore from a backup file if you have one,” with a file picker allowing them to select a previously exported JSON file and restore its contents.

— Claude Sonnet AI

Remember that we are first building a PWA (web app) before we turn this into an actual App Store product. This progressive development serves the purpose of testing the app in “free mode” before trying to get this approved by each App Store (Apple and Google Play) and paying their listing fees.

App Evolution: Features in Development

Now that we got some of the mild techie stuff out of the way, let’s talk app features now. As you can see from the featured image for this post, there are many features I’m building into this app in an effort to make this really worth loading on your phone. Here are just a few of many in the works…

• Dream Journal Creation / Storage
• Dream Dictionary (synced to website)
• Smart Search (for all website content)
• Favorites Library (uploading PDFs)
• Journal Reminders
• Direct Messaging
• Event Updates
• Daily Tips
• Notifications

These features are just the beginning and the whole appearance of the app is still in the development stage. I’m determined that this app will not look “boring” or stagnant so I have my own creative / artistic ideas already lined up for the build.

Why This Matters To You

Also… This app will help to organize the full scope of all my website content to include all major blog categories in a way that users will more easily see how they all fit together. Want to know how discovering your purpose fits in with dream interpretation and the Supernatural Entrepreneur series? What about how the Blue Cube Rocket invention or marvel supernatural abilities tie together and relate to you? This app will help with that.

What I really want to express here is that the future of this app is equally as BIG as everything God has called me (and YOU) to in this life. When you see how it all ties together, you will begin to get a really good idea of how YOUR CALLING is also MUCH BIGGER than you’ve been led to believe. If there’s one message I want to convey in this entire website, that right there is it.

Well, that’s a pretty good (and very light) recap of my recent efforts on this app. This is just barely a slight glimpse into what goes into app development and much more has been in the works.

If you would like to join my “development / supporters team” and help me get this app deployed to app stores, use the link in the promo image below. Trust me, you don’t need any serious technie skills for this! I really just want anyone who finds this project interesting to join and help test the app and give me feedback for its direction.

If that’s something you can do, please join the effort! The more people who join, the faster this will happen!

As always, thank you for reading and for your support!!

Contact!

---