Frequently Asked Questions
Find answers to your questions
Project FAQ
Because building a fully functional, secure, accessible app is a massive undertaking. This first phase is focused on foundational planning, prototypes, systems design, legal/business setup, and proving out the concept properly before anyone overcommits financially. I would much rather approach this responsibly and sustainably than promise a giant fully-developed platform immediately and risk the project collapsing under its own scope.
Short answer: no. Longer answer: aside from my general ethical opposition to generative AI in creative spaces, many of those tools create significant concerns around IP ownership, asset protection, long-term platform control, scalability, and data governance. I do not feel comfortable sacrificing control over the realm’s creative assets, systems, or user data to third-party AI tooling whose infrastructure and policies I cannot fully control. Additionally, accessibility, moderation, privacy, app store compliance, account systems, backend architecture, security, and long-term maintainability are all things that still require real development work and proper oversight if this is going to be done responsibly.
Nope! The goal is expansion, not replacement. I view the app as another pathway into the realm rather than a substitute for the existing experience. The Herald, website, social media content, side quests, and community spaces are all still core parts of the realm itself. Different travelers simply enjoy engaging in different ways, and I want the realm to remain accessible across multiple formats.
The plan is to keep all core functionality free. That is extremely important to me philosophically. The realm was built around accessible side questing and community participation, and I do not want the core experience locked away behind a paywall. There may eventually be optional cosmetic purchases, supporter options, expanded materials, or other additions that help sustain development long-term, but the goal is for the primary experience itself to remain accessible.
This first phase is primarily funding foundational work: planning, prototypes, design systems, technical exploration, accessibility planning, legal/business setup, early development infrastructure, and assembling the proper support needed to approach the project responsibly. Basically: building the foundation correctly before trying to construct the entire castle on top of it.
Because apps are unfortunately very expensive to build properly Especially if you care about things like accessibility, account systems, moderation, backend infrastructure, security, cross-platform support, data privacy, UI/UX design, long-term maintainability, and compensating real artists/developers fairly. I would rather build this slowly and responsibly than rush out something unstable, exploitative, or unsafe.
Most productivity apps are built around optimization and management: managing tasks, habits, schedules, streaks, efficiency, and visible incompletion. Sir Kadean is built around engagement instead. The core idea behind the realm is that many people already know what they need to do. The harder part is that modern life can begin feeling repetitive, overwhelming, emotionally flat, or entirely maintenance-oriented. Over time, even the tools meant to help can start feeling stressful or guilt-inducing themselves. Rather than reducing life to static checklists, Sir Kadean reframes daily life as an evolving quest-based experience. The system blends productivity, creativity, exploration, rest, movement, social connection, reflection, and play into one interconnected world designed to make engagement feel more natural and rewarding over time. The app is also intentionally designed around positive reinforcement and achievable entry points. Users are rewarded for participation and momentum rather than punished for imperfection. Quest structures vary in difficulty and tone so there is always something realistically achievable regardless of energy level, executive functioning, schedule, or emotional state. Ultimately, the goal is not simply to help people “optimize” themselves harder. The goal is to help daily life feel more immersive, dynamic, navigable, and alive.
Concept Art Exploratory artwork used to establish the visual direction, environments, icons, mood, and overall feel of the realm. Mockups Polished visual examples of what the app could look like before it fully exists. Prototype An interactive test version that lets us click around, test navigation, and explore how the app actually functions before full development. UX/UI UX = User Experience UI = User Interface Basically: making sure the app is intuitive, readable, immersive, and actually pleasant to use. Technical Architecture The behind-the-scenes structural systems that allow the app to actually function properly: accounts, notifications, reward tracking, saving progress, syncing between devices, admin tools, etc. Cloud Infrastructure The online systems that store app data and keep everything running. This is what allows your progress, rewards, quests, and account information to persist instead of disappearing every time you close the app (that would be sad!). Contractors Sir Kadean is not currently a fully funded game studio or software company with a permanent internal development team. Much of the specialized work for the app would therefore be done through contractors: developers, UX designers, engineers, QA, accessibility specialists, artists, consultants, and other professionals hired for specific parts of the project as development expands instead of full time employees. Engineering Consultations Working with actual developers to determine what is technically realistic, how systems should be built, estimated costs, and how to avoid accidentally building a cursed nightmare infrastructure. Roadmap A structured long-term development plan showing the intended phases, priorities, systems, and progression of the project over time. Basically the “what gets built when and in what order?” type thing. Beta Testing Allowing a small group of users to test early versions of the app before public release in order to identify bugs, usability problems, confusing systems, balancing issues, accessibility concerns, and general feedback. Security & Privacy Systems The protections that keep user accounts, personal information, and app data secure and compliant with platform requirements. Accessibility Standards Apps are expected to support users with different visual, auditory, motor, neurological, and cognitive needs. This includes things like readable interfaces, screen reader support, contrast requirements, scalable text, navigation accessibility, and more. App Store Approvals Apps must meet Apple and Google requirements around privacy, security, accessibility, stability, and functionality before they can officially launch. MVP (Minimum Viable Product) The smallest functional version of the app that still properly delivers the core experience. For Sir Kadean, that means: -daily quest delivery -quest tracking -simple rewards/progression -foundational account systems
This project is ambitious. I want to be very upfront about that. The largest challenge by far is that building a fully functional, secure, accessible, cross-platform app is an enormous undertaking that requires far more than simply “having a good idea.” Proper development involves engineering, UX/UI design, accessibility compliance, backend infrastructure, moderation systems, data/privacy considerations, testing, long-term maintenance, legal/business structure, and sustainable production planning. That is specifically why this project is being approached in phases rather than attempting to promise a fully completed app immediately. This first phase is focused on building a strong foundation: prototypes, planning, technical exploration, design systems, early infrastructure, and assembling the right support to move responsibly into larger-scale development. Another challenge is scope management. The realm has grown far beyond what I originally expected, and there are many possible directions this project could expand into. One of my primary goals throughout development will be protecting the core spirit of the realm itself rather than overloading the project with unnecessary systems or features too quickly. Physical rewards and mailed items also carry normal fulfillment risks such as manufacturing delays, shipping delays, supply availability, and timeline shifts. I will do my best to communicate transparently and early should any delays arise. I also want to be transparent that this is not currently backed by a large studio, publisher, or corporate production pipeline. Much of the early organizational work is being navigated independently and collaboratively with contractors/supporters as the project grows. Because of that, timelines may evolve as development realities become clearer. That said, I do come into this with a strong background in software product development, systems planning, healthcare technology, user engagement systems, and cross-functional project coordination. While I am not personally coding the app itself, I do understand the realities of software production and the importance of building responsibly rather than rushing toward unrealistic promises. Most importantly: I care very deeply about protecting the trust, accessibility, creativity, and community spirit that made the realm meaningful in the first place. I would rather move carefully and sustainably than compromise those things for speed.
BackerKit FAQ
BackerKit Crowdfunding is an all-or-nothing collaborative funding platform. Creators share their project ideas and set a funding goal with a deadline. Backers pledge money to help make the project possible.
If the project meets its goal by the deadline, pledges are charged and the creator moves forward. If it doesn’t, no one is charged.
Backers often receive special rewards for their support, such as:
- Exclusive products
- Bonus rewards for backing related projects
- Discount pricing
- Behind-the-scenes updates
- Creative input opportunities
Pledging in crowdfunding is a commitment to support the creation of a new product or project. Unlike a traditional purchase, you're not buying an item that already exists. Instead, your contribution helps bring a creative idea to life, and in return, you typically receive rewards (such as the product itself) as a thank you for your early support.
- Select a pledge level with the reward(s) you would like to receive
- Select any add-ons
- Confirm your pledge!
- You are charged only if the campaign meets its funding goal.
- Charges happen when the campaign ends, not when you pledge.
The creator will send you a survey to:
- Ask you for more information about your rewards (selecting options, etc)
- Collect shipping information
- Offer additional items you may want to add to your pledge
- Collect shipping fees (if applicable)
The survey will be sent to the email address we have on file with your pledge. Additional payments are charged when you complete the survey.
Only the project creator and the BackerKit Support Team can see your pledge and contact information. Other backers and the public cannot see your individual pledge amount or personal details.
You can change or adjust your pledge level and add-ons before the campaign ends. After the project concludes, cancellations or changes are at the creator's discretion and may depend on what stage the project is in.
Overtime Mode extends your campaign past its original end time to give backers a final chance to make their pledge. It will add an additional 10 minutes past the end time as long as pledges keep coming in. The campaign will end when there is a 10-minute period without any new pledges.