Living System Best Practices

Learn from successful Genesis users to build better apps faster and avoid common pitfalls.

Writing Effective Prompts

The quality of your prompt directly impacts the quality of your app. Here's how to write prompts that get great results.

The Perfect Prompt Formula

Industry + Users + Problem + Solution + Outcome = Great Results

I run a [INDUSTRY] and [USERS] need to [PROBLEM] because [CONTEXT]. They should be able to [SOLUTION] and when they do, [OUTCOME] should happen automatically.

Be Specific About Your Industry

❌ Too generic: "I need a booking system"

✅ Industry-specific: "I run a veterinary clinic and pet owners need to book appointments for their animals"

Why this matters: Different industries have different requirements, terminology, and user expectations. A booking system for a vet clinic needs different features than one for a hair salon.

Describe the Complete User Journey

❌ Incomplete: "Customers can book appointments"

✅ Complete journey: "Customers browse available times, select their preferred veterinarian, choose appointment type (checkup, vaccination, emergency), provide pet information, pay a deposit, receive confirmation with pre-visit instructions, and get reminder calls 24 hours before their appointment"

Include Business Rules and Constraints

❌ Vague: "Handle cancellations"

✅ Specific rules: "Allow cancellations up to 24 hours before appointment time with full refund, cancellations within 24 hours forfeit the deposit, and emergency cancellations due to pet illness can be rescheduled without penalty"

Specify Your Audience

Consider these factors:

• Technical comfort level: "Elderly clients who prefer simple interfaces"

• Device usage: "Busy parents who primarily use mobile phones"

• Context of use: "Staff who need to quickly enter data between customer interactions"

Testing Your App

Test Like a Real User

Use realistic scenarios:

✅ Book an appointment for your actual pet with real dates
✅ Submit feedback about a meal you actually ate
✅ Upload a real document that your customers would submit

Avoid testing shortcuts:

❌ Using "[email protected]" as an email
❌ Entering "asdf" in text fields
❌ Skipping optional fields that real users might fill out

Mobile-First Testing

Test on actual devices:

• Pull out your phone and use the app

• Try typing on the mobile keyboard

• Test with poor internet connection

• Check how it looks in both portrait and landscape

Common mobile issues to watch for:

• Buttons too small to tap easily

• Text too small to read

• Forms that don't work with mobile keyboards

• Images that don't load on slower connections

Test Edge Cases

What happens when:

• Someone uploads a very large file?

• A user enters special characters or emojis?

• Multiple people try to book the same time slot?

• Someone leaves required fields blank?

• The internet connection is slow or interrupted?

Get Real User Feedback

Start with a small group:

• Choose 3-5 people who represent your actual users

• Watch them use the app (don't just ask for their opinion)

• Take notes on where they hesitate or seem confused

• Ask specific questions: "Was it clear how to submit your request?"

Iterating and Improving

Make One Change at a Time

❌ Too many changes at once:

"Make the button bigger, change the colors, add a progress bar, connect to our CRM, and add a payment system"

✅ One focused change:

"Make the submit button bigger and more prominent so it's easier to find on mobile devices"

Why this matters: When you change multiple things at once, you can't tell which change caused which result. If something breaks, you won't know what to fix.

Test Each Change

After each modification:

1. Test the specific change you made

2. Make sure you didn't break anything else

3. Get feedback from users if it's a significant change

4. Document what worked and what didn't

Use Data to Guide Decisions

Track meaningful metrics:

• How many people complete the main action (conversion rate)

• Where people drop off in the process

• How long it takes people to complete tasks

• What questions or problems come up most often

Ask the right questions:

• "Where do people get stuck?"

• "What features do people use most?"

• "What do people ask for help with?"

Managing Your App

Document Your Setup

Keep track of:

• Integrations: Which services are connected and how

• Automations: What triggers what actions

• User roles: Who has access to what features

• Business rules: Special policies or requirements

Why this matters: When you need to make changes or train new team members, you'll want to remember how everything works.

Plan for Growth

Start simple, scale thoughtfully:

1. Build for your current needs first

2. Monitor usage patterns to see what's working

3. Add features based on actual user requests rather than assumptions

4. Test new features with a small group before rolling out to everyone

Maintain Your App

Regular maintenance tasks:

• Test integrations to make sure they're still working

• Review user feedback for improvement opportunities

• Update content like pricing or service descriptions

• Clean up old data that's no longer needed

Team Collaboration

Getting Team Buy-In

Include your team in the process:

• Show them early versions and get their input

• Train them on how to use the app effectively

• Ask for their ideas on improvements

• Celebrate successes when the app helps the business

Assign Ownership

Clear responsibilities:

• Who updates content like prices or service descriptions?

• Who monitors for problems or user feedback?

• Who responds to customer questions about the app?

• Who makes decisions about new features or changes?

Security and Privacy

Protect User Data

Essential security practices:

• Use strong passwords for admin accounts

• Limit access to only the people who need it

• Regular backups of important data

• Monitor for suspicious activity or unauthorized access

Be Transparent

Clear communication with users:

• Explain what data you collect and why

• Provide options for users to control their information

• Make it easy for users to update or delete their data

• Respond quickly to privacy concerns or questions

Common Mistakes to Avoid

Over-Engineering

❌ Building for imaginary future needs:

"Add advanced analytics, multi-language support, and integration with 10 different services in case we need them someday"

✅ Building for current reality:

"Build a simple feedback form that works well for our current customers and can be enhanced later if needed"

Ignoring User Feedback

❌ Assuming you know what users want:

"The app is perfect as designed, users just need to learn how to use it properly"

✅ Listening and adapting:

"Three people mentioned the same confusion, let's fix that before rolling out to more users"

Perfectionism Paralysis

❌ Waiting for perfection:

"We can't launch until every possible feature is built and every edge case is handled"

✅ Iterative improvement:

"Let's launch with the core features working well and add enhancements based on real usage"

Feature Creep

❌ Adding features without purpose:

"Let's add a chat feature and social media integration because other apps have them"

✅ Purpose-driven development:

"Our users are asking for a way to communicate with our team, so let's add a simple contact form"

Success Metrics

Define Success Early

Before building, decide what success looks like:

• Usage metrics: How many people use the app?

• Completion rates: Do people finish the main action?

• Time savings: Does this make processes faster?

• Customer satisfaction: Are people happier with this experience?

• Business impact: Does this help achieve business goals?

Regular Check-Ins

Monthly review questions:

• Is the app being used as expected?

• What feedback are we getting from users?

• Are our integrations still working properly?

• What improvements would have the biggest impact?

• Should we add new features or simplify existing ones?

Getting the Most from Genesis

Leverage the AI Agent

Use the built-in AI for ongoing improvements:

"What features should I add to make this app better for my restaurant customers?"

"How can I improve the mobile experience for people booking appointments?"

"What integrations would be most useful for a customer feedback app?"

Stay Updated

Keep learning:

• Follow Genesis updates for new features and capabilities

• Join the community to see what other users are building

• Experiment with new features as they become available

• Share your successes to help other users learn

Think Beyond Your First App

Once you've mastered one app:

• Identify other processes that could benefit from automation

• Consider apps for different audiences (customers vs. internal team)

• Build connected systems where apps work together

• Help other team members build their own solutions

---

Quick Reference Checklist

Before Building

• Clearly define the problem you're solving

• Identify who will use the app and how

• Write a detailed prompt with business context

• Plan how you'll test the app

During Development

• Test each feature as it's built

• Make one change at a time

• Get feedback from real users early

• Document important decisions and setup

After Launch

• Monitor usage and gather feedback

• Plan regular maintenance and updates

• Train team members on using the app

• Measure success against your original goals

Ongoing Success

• Listen to user feedback and iterate

• Keep security and privacy in mind

• Share successes and learn from others

• Look for opportunities to build additional apps

---

Remember: The best Genesis apps are built iteratively. Start with something simple that works, get it in front of real users, and improve based on their actual needs and feedback.