A complete look at building vertical drama platforms with engaging storytelling seamless video streaming smart monetization and scalable technology for 2027

A person opens a video app while waiting for a coffee. They intend to spend a few minutes scrolling, but a dramatic scene catches their attention. A character discovers a hidden relationship, another faces an unexpected betrayal, and the episode ends just as the situation becomes interesting.

The viewer wants to know what happens next. Instead of waiting for a weekly release, they can continue watching the story through another short episode.

This is the viewing experience that has helped vertical short dramas find an audience.

Unlike traditional television and conventional streaming platforms, short-drama applications are designed around quick episodes, mobile screens, compact storytelling, and frequent moments of suspense. They combine elements of social video platforms, subscription streaming, and mobile entertainment into a different kind of product.

But creating one involves much more than placing videos inside a mobile application. The real challenge is building an experience that makes viewers want to return without making the product feel repetitive or unnecessarily complicated.

This guide explores the product decisions, technology, content structure, monetization options, and development challenges involved in building a vertical drama platform in 2027.

1. What Makes Vertical Short Drama App Development Different?

Vertical short drama app development involves building a mobile-first entertainment platform where fictional stories are presented in short, vertically formatted video episodes.

The format changes how viewers interact with entertainment.

Traditional streaming services generally organize content around movies, television seasons, and longer episodes. Short-drama platforms take a different approach. They divide stories into smaller segments, often ending individual episodes with a question, revelation, or unexpected development.

The difference is not simply the video orientation.

A vertical drama application needs to coordinate several elements:

• A continuous mobile viewing experience.
• Short episodes that maintain narrative continuity.
• Content discovery based on viewer interests.
• Episode access and progression.
• Payment systems for premium content.
• Recommendations that improve as viewers interact with the platform.

Consider a fictional story about a business owner who discovers that their closest business partner has been hiding important information.

A conventional series might explore this development over an entire episode. A short-drama format could divide the same storyline into several compact scenes, with each installment revealing another piece of information.

This changes both content production and application design.

The development team must think about how viewers discover stories, move between episodes, unlock content, and resume watching after leaving the application.

2. Why the Vertical Drama Format Is Becoming Interesting for Digital Entertainment

Short-form video has already changed how people consume online content. However, vertical drama platforms introduce something different: a continuous fictional narrative within a short-video environment.

There are three interesting developments behind this format.

Storytelling is becoming more compact

Writers and producers have to communicate character motivations, conflicts, and developments in less time.

This does not mean every scene needs to move quickly. It means each scene should have a clear purpose.

A short episode that introduces a character, reveals a conflict, or changes the direction of a story can be more effective than one filled with unnecessary dialogue.

Mobile viewing influences production decisions

Vertical video is designed for smartphones, where viewers generally hold their devices upright.

This affects cinematography, character positioning, subtitles, close-up shots, and scene composition.

Producers cannot simply take a traditional landscape video and crop it into a vertical format. Important visual information may disappear in the process.

Entertainment and application design are becoming connected

The viewing experience is influenced by more than the quality of the story.

A slow-loading episode, confusing payment process, or poorly organized content library can interrupt an otherwise interesting experience.

This means product development and content strategy need to work together.

3. Essential Features of a Vertical Short Drama Application

A successful application should not begin with dozens of features. It should begin with the functions that make watching, discovering, and continuing a story convenient.

Here are the main components worth considering.

3.1 Vertical Video Player

The video player is the central part of the application.

It should support portrait-oriented playback, adaptive streaming, playback controls, and smooth transitions between episodes.

Useful capabilities include:

• Full-screen vertical playback.
• Play and pause controls.
• Video quality adjustment.
• Subtitle support.
• Playback progress tracking.
• Automatic next-episode playback.
• Resume-watching functionality.

The player should also handle network interruptions gracefully. A viewer should not have to restart an entire episode because their internet connection briefly becomes unstable.

3.2 Personalized Content Discovery

A large content library becomes difficult to navigate when every viewer sees the same recommendations.

A discovery system can organize dramas using categories such as:

• Romance
• Mystery
• Thriller
• Revenge
• Family drama
• Fantasy
• Historical fiction

Recommendations can also consider watch history, completed episodes, saved stories, and user-selected preferences.

The important distinction is between showing popular content and showing relevant content. A viewer who repeatedly watches mystery dramas may not find a generic romance recommendation particularly useful.

3.3 Episode Management

Short dramas often contain multiple episodes organized into individual seasons or story collections.

The application needs a reliable way to manage episode numbers, viewing permissions, release schedules, and completion status.

For example, a viewer who finishes episode 12 should be able to continue from episode 13 without searching through the entire content library.

3.4 Watchlist and Viewing History

People do not always finish a story in one sitting.

A watchlist allows viewers to save dramas for later, while viewing history helps them return to previously watched episodes.

These functions become especially important when a platform hosts hundreds of stories.

3.5 User Profiles and Account Management

A user account can store viewing preferences, subscription details, saved content, and watch progress.

Depending on the application model, developers can also consider:

• Multiple profile support.
• Account synchronization.
• Language preferences.
• Notification settings.
• Subscription management.
• Parental controls.

The goal is to make the viewing experience consistent across sessions and supported devices.

3.6 Push Notifications

Notifications can inform viewers about new episodes, upcoming releases, and updates to stories they follow.

However, notification frequency requires careful planning.

Sending too many reminders can make an entertainment application feel intrusive. Notifications should be connected to actual viewing interests rather than used as a constant attempt to bring users back.

4. The Technology Behind a Vertical Drama Streaming Platform

The visible application is only one part of the product. Behind the video player, several systems need to work together.

The technology stack will depend on the expected audience, content volume, budget, and development approach.

Here are some common components.

Frontend Development

The frontend handles the interface that viewers interact with.

Common development choices include:

• Flutter: Useful for building cross-platform mobile applications.
• React Native: Allows developers to build applications for multiple mobile platforms using a shared development approach.
• Swift: Used for native iOS development.
• Kotlin: Used for native Android development.

The right choice depends on performance requirements, available expertise, and the complexity of the application.

Backend Development

The backend manages the application logic and communication between different services.

Common technologies include Node.js, Python, Java, and Go.

Backend systems may handle:

• User authentication.
• Content management.
• Episode information.
• Payment processing.
• Subscription records.
• Viewing history.
• Recommendation requests.
• Administrative operations.

For a growing streaming platform, the backend should be designed to handle increases in concurrent viewers and content requests.

Cloud Infrastructure

Video applications require infrastructure that can store and deliver large media files.

Cloud providers such as AWS, Google Cloud, and Microsoft Azure offer services for storage, computing, databases, and application deployment.

A practical architecture may use:

• Cloud object storage for video files.
• A content delivery network for media distribution.
• Managed databases for application records.
• Containerized services where appropriate.
• Monitoring systems for performance and reliability.

The infrastructure should be selected according to the application’s actual traffic requirements rather than assuming that the most complex architecture is automatically the best one.

Video Encoding and Streaming

Uploading a video and delivering it efficiently to viewers are two different processes.

A typical workflow involves:

1. Uploading the original video.
2. Processing and encoding it into multiple resolutions.
3. Generating compatible streaming formats.
4. Storing the processed files.
5. Delivering them through a content delivery network.
6. Adjusting playback quality according to available bandwidth.

HTTP Live Streaming (HLS) and MPEG-DASH are commonly used adaptive streaming approaches.

Adaptive bitrate streaming is particularly useful because mobile viewers may switch between Wi-Fi and cellular networks while watching.

5. How AI Can Improve the Short Drama Viewing Experience

Artificial intelligence can be useful in entertainment applications, but it should solve identifiable problems rather than exist simply because it is a popular technology.

There are several practical applications worth exploring.

Personalized Recommendations

Machine learning models can analyze viewing behavior to identify patterns.

For example, a recommendation system might consider:

• Genres frequently watched.
• Episodes completed.
• Stories added to a watchlist.
• Viewing duration.
• Interactions with recommended titles.

These signals can help the platform suggest content that matches individual preferences.

Content Tagging and Classification

A platform with a large library needs an organized content catalog.

AI-assisted classification can help identify genres, themes, languages, characters, and other metadata.

Human review remains important, particularly when content involves complex storylines or context that automated systems may misunderstand.

Subtitle Generation and Translation

Speech recognition can help generate initial subtitles, while translation tools can support additional language versions.

However, automated subtitles need review. Incorrect character names, dialogue timing, or translated expressions can affect the viewer’s understanding of a story.

Content Performance Analysis

AI-assisted analytics can help identify patterns in episode completion, viewer drop-off, and content engagement.

These insights may help production teams understand whether a particular episode is too slow, whether viewers are leaving before the ending, or which genres are attracting repeat viewing.

The goal should be to improve storytelling decisions, not simply maximize screen time.

6. Monetization Models for a Vertical Drama Application

The business model influences how viewers access content and how the platform generates revenue.

There is no single monetization strategy that works for every application.

Advertising-Based Model

The application offers free episodes and generates revenue through advertisements.

Possible placements include:

• Ads before an episode.
• Ads between selected episodes.
• Rewarded advertisements that unlock additional viewing time.

The challenge is balancing advertising frequency with the viewing experience.

Subscription Model

Users pay a recurring fee to access premium content.

Subscriptions may provide:

• Ad-free viewing.
• Access to exclusive dramas.
• Unlimited episode access.
• Early access to new releases.

A subscription model works best when the platform can consistently provide content that viewers consider worth paying for.

Coin or Credit-Based Model

Some short-drama platforms use virtual currencies.

Users purchase coins or credits and spend them to unlock individual episodes.

This approach gives viewers more control over how much they spend, but the pricing structure should be transparent.

The application should clearly communicate episode costs, remaining balances, and payment conditions.

Hybrid Monetization

A hybrid approach combines free content, advertisements, subscriptions, and individual episode purchases.

For example, a platform might allow viewers to watch the first few episodes for free and then provide several options for accessing the remaining story.

This can create different revenue opportunities without requiring every viewer to become a subscriber.

7. The Development Process: From Concept to Launch

Building a short-drama application involves more than selecting technologies and designing screens.

The development process should begin with understanding the audience and the intended business model.

Step 1: Define the Product

Start by identifying what the application is supposed to offer.

Is it focused on romance and relationship dramas? Will it host multiple genres? Will the platform produce original content or license existing productions?

These decisions influence the content management system, user interface, and monetization strategy.

Step 2: Research the Audience

Understand how the intended viewers consume entertainment.

Consider their preferred genres, language requirements, viewing habits, and willingness to pay for premium episodes.

Competitor analysis can also help identify missing features and areas where the application could offer a different experience.

Step 3: Plan the User Experience

Map the main journey from opening the application to watching an episode.

A basic journey might look like this:

Open application → Discover a drama → Watch the first episode → Continue to the next episode → Unlock premium content → Save the story.

This simple exercise can reveal unnecessary steps before development begins.

Step 4: Build the MVP

A minimum viable product should contain the essential functions required to test the platform.

A reasonable first version might include:

• User registration and login.
• Home screen and content categories.
• Vertical video player.
• Episode management.
• Watch history.
• Basic content administration.
• One monetization method.

Advanced recommendation systems and complex personalization can be introduced after collecting meaningful user data.

Step 5: Test Streaming and Payments

Testing should cover more than whether the application opens successfully.

The team should evaluate video playback across different network conditions, payment failures, interrupted sessions, device compatibility, and content loading times.

Payment testing is especially important when episodes are unlocked through purchases or subscriptions.

Step 6: Launch, Monitor, and Improve

After launch, monitor how viewers interact with the platform.

Useful measurements include:

• Episode completion rate.
• Average viewing duration.
• First-episode abandonment.
• Repeat viewing.
• Subscription conversion.
• Revenue per active user.
• Video buffering and playback failures.

These measurements provide more useful product feedback than download numbers alone.

8. Challenges Developers Should Consider Before Building

A short-drama application may look simple from the viewer’s perspective, but its underlying systems can become complicated as the platform grows.

Some challenges deserve attention early.

Content Production and Licensing

Technology cannot compensate for a weak content library.

The platform needs engaging stories, consistent episode releases, and appropriate distribution rights.

Content licensing should clearly establish where, how, and for how long a drama can be distributed.

Streaming Costs

Video storage, encoding, and delivery can become significant operational expenses.

A platform with growing viewership needs to monitor bandwidth consumption, video quality, storage requirements, and CDN costs.

Viewer Retention

A dramatic ending may encourage viewers to watch another episode, but repeated cliffhangers cannot replace meaningful storytelling.

If every episode follows exactly the same pattern, viewers may eventually lose interest.

Payment Friction

A complicated unlocking process can interrupt the viewing experience.

Pricing should be understandable, payment methods should be reliable, and users should know what they are purchasing.

Copyright and Content Security

Video content needs appropriate protection against unauthorized distribution.

Depending on the business model, developers may consider signed URLs, access controls, encryption, and digital rights management solutions.

No single protection method guarantees that content cannot be copied, but layered security can make unauthorized access more difficult.

9. How to Choose the Right Development Partner

Selecting a development partner is an important decision because the quality of the underlying architecture can affect the application long after its first release.

A vertical drama app development company should understand both the technical requirements of video streaming and the product experience expected from an entertainment platform.

Here are some questions worth asking before making a decision:

Does the team understand video streaming?

Ask about adaptive streaming, video encoding, CDN integration, and playback optimization.

Can it build a complete content management system?

The platform needs tools for uploading dramas, organizing episodes, managing categories, and controlling release schedules.

Does it understand monetization integration?

Payment processing, subscriptions, virtual credits, and advertising need to work together without disrupting playback.

Can the application scale?

Ask how the development team approaches infrastructure, database design, traffic management, and performance monitoring.

What happens after launch?

Clarify maintenance, security updates, bug fixes, technical support, and future feature development.

Companies such as Triple Minds can be explored when evaluating development partners for custom entertainment and streaming applications. The important step is to assess the actual portfolio, technical experience, delivery process, and project fit rather than relying only on service descriptions.

10. What Could Change in Vertical Drama App Development by 2027?

The next stage of development will probably involve improving the relationship between content, personalization, and application infrastructure.

A few developments are worth watching.

More sophisticated recommendation systems

Platforms may move beyond basic genre recommendations toward systems that understand viewing patterns and individual content preferences more effectively.

Better multilingual experiences

Subtitles, dubbing workflows, and localized content discovery could make it easier for platforms to serve viewers across different regions.

More flexible content monetization

Applications may experiment with combinations of free episodes, subscriptions, credits, and premium releases to accommodate different viewing preferences.

AI-assisted production workflows

AI tools may support subtitling, content tagging, editing assistance, and production planning. Human creative decisions will remain essential to maintaining story quality.

Improved cross-device experiences

Although vertical dramas are primarily designed for smartphones, synchronized accounts and viewing progress could help users move between supported devices.

These developments are not guaranteed features of every platform. Their usefulness will depend on audience demand, implementation costs, and the overall product strategy.

Final Thoughts

Vertical short dramas are interesting because they bring two different ideas together: serialized storytelling and mobile-first video consumption.

Building an application around this format requires careful attention to more than the interface. Content organization, episode progression, streaming infrastructure, payment experiences, and audience retention all influence whether the product can become sustainable.

For businesses considering this category in 2027, the better starting point is not to build every possible feature. It is to understand the audience, create a reliable viewing experience, and develop a platform that can evolve as viewing habits change.

The technology makes the experience possible, but the stories give people a reason to return.

Support writers. All our nonprofit’s offerings here.

Click here to subscribe to the IT Chronicles newsletter.

Click for Wordsmith, Mystery Writing, Write Like Stephen King, more

Vertical Short Drama App Development — A Complete Guide for 2027 was originally published in IT Chronicles on Medium, where people are continuing the conversation by highlighting and responding to this story.

Five agencies I vetted for quality AI features and scale

A message landed in my inbox on a Sunday evening a few weeks ago. It came from a founder I’d worked with on an earlier project, a man who runs a regional cab operation with around sixty vehicles and a dispatch process held together by phone calls and a very patient operations manager. He had decided it was time to build his own ride-booking app and he wanted to launch before the 2027 season. His message was short: “You’ve built enough of these. Who should I actually hire?”

I started typing a quick answer and deleted it. The honest reply to that question is never a single name. It depends on whether he wants a platform built around his exact workflow or a proven product he can rebrand in weeks. It depends on how much of his budget should go into technology versus drivers, incentives and marketing. It depends on whether he has any technical people in-house. And it depends on something he hadn’t asked about but needed to: how much AI he needs inside the app on day one versus day three hundred.

So I wrote him a longer reply. This article is that reply, expanded. I’ve worked with all five of the companies below, in different roles and on different kinds of projects, and I picked them for the same reasons I’d pick a partner for my own project: the quality of what they ship, how seriously they treat AI features rather than treating AI as a brochure line, whether the platform holds up as it scales, and how honest they are about what they do and don’t do.

Two of them build custom. Three of them sell white label products. One of those is a marketplace rather than an agency. That mix is deliberate, because the right answer for a taxi business depends heavily on which model fits, and I’ll explain how I think about that before I get to the names.

How I Evaluated These Companies

Every agency’s website says “scalable, secure, AI-powered.” Those words are free. What I look at instead is a short list of things that have separated good outcomes from bad ones across the taxi and on-demand projects I’ve been part of.

• Quality of the shipped product. Not the demo environment. The live app on a real phone, with real drivers, on a real network. Does dispatch lag? Does the rider map jitter? Does the driver app drain a battery in four hours?
• AI depth. Whether AI features are actually built into the platform (smart dispatch, ETA prediction, pricing logic, fraud checks, support automation) or listed on a services page with nothing behind them.
• Scalability. What happens at ten thousand rides a day rather than a hundred. This is about architecture: event-driven location handling, database design, and how the pricing engine behaves under load.
• Ownership and lock-in. Do you receive source code, under what license, and can another team maintain it.
• Post-launch support. Taxi apps fail in the weeks after launch, not before it. Who answers the phone then.
• Honesty. Whether the agency tells you when your idea doesn’t need what they sell.

I also weighted fit heavily. An agency that’s excellent for one kind of client can be the wrong choice for another, and I’ve tried to say clearly which is which.

Custom or White Label: The Decision That Comes First

Before comparing companies, it helps to be clear about the two models, because three of the five agencies below sit on one side and one sits firmly on the other.

Custom development means the app is designed and built around your specific requirements. Your dispatch rules, your fare logic, your driver onboarding workflow, your compliance setup. You get maximum flexibility and a product that fits you exactly. You also get a longer timeline, a larger budget and more first-version risk, because you’re discovering problems in production that an existing product would already have solved.

White label means starting from an existing, tested taxi platform (rider app, driver app, admin panel, dispatch module) and adapting it with your branding, your pricing rules and your market configuration. You get speed and lower cost, and you inherit edge cases that were already fixed for earlier clients. You give up some flexibility, and how much depends heavily on how the platform was built and what license you receive.

My working rule for taxi apps is simple. If your competitive edge is operational (local market knowledge, driver relationships, fleet control, service quality), white label is usually the better starting point, because the platform isn’t what you’re competing on. If your edge is the technology itself (a novel matching approach, an unusual service model, deep integration with an existing fleet system), custom is justified. Most founders I talk to are in the first group and assume they’re in the second.

What a Taxi App Needs in 2027

When my client asked about AI, I told him what I look for in any taxi platform I’d put my name next to. The baseline for 2027 goes well beyond a map with a moving car on it.

• Smart dispatch and matching that considers driver location, heading, acceptance history, and predicted trip duration rather than just “nearest car”
• ETA prediction that adapts to traffic and time of day, because inaccurate ETAs are the single biggest source of rider complaints
• Dynamic pricing support with a real-time demand and supply layer, plus clear rider-facing surge communication
• Fraud and safety detection: fake GPS spoofing, payment fraud, route deviation alerts, and suspicious cancellation patterns
• AI-assisted support that resolves lost-item queries, fare disputes and ride-status questions without a human for the routine ones
• Demand heatmaps and driver positioning guidance so drivers spend less time idle
• Multi-channel booking, including messaging channels where many riders already are
• Admin analytics that show revenue, utilization, cancellation and driver quality by area and time

Not every platform ships all of this, and not every business needs all of it on day one. But the agencies worth hiring can tell you plainly which of these are built, which are configurable, and which would be custom work. That honesty is the filter I use first.

1. Triple Minds

Model: Custom and white label | Headquarters: Mohali, India | US presence: New Jersey

Triple Minds is the one on this list that gives you both routes, and that flexibility is a large part of why I’d put it first for founders who aren’t sure which model fits.

On the white label side, they offer a taxi platform covering the pieces you’d expect: passenger and driver apps, an admin panel, dispatch, live tracking, payments, ratings and scheduled rides. The practical benefit for a founder in a hurry is that you can launch a branded product in weeks rather than months, then iterate from real usage. I’ve seen white label launches from them land on timelines that custom builds simply can’t match, and the foundation was stable enough that the first production weeks were about tuning rather than firefighting.

On the custom side, they’ll build an MVP around your own workflow, or a multi-city platform where operations across regions need different rules, different currencies or different compliance setups. This is where their AI-native approach shows. Because they build AI-featured apps across several categories, including AI chatbots, recommendation systems and agent-style automation, the AI layer in a taxi build tends to be designed in rather than bolted on. In practice that means smarter dispatch logic, AI-assisted support flows, and analytics that go beyond reporting into recommendation.

What I appreciated most was the hybrid path. Several of the best outcomes I’ve seen started with a white label base and then layered custom features on top: a specific corporate account module, a particular pricing rule, a regional payment method. You get the speed of white label without being boxed in.

What I valued:

• A genuine choice between white label, custom MVP and multi-city builds under one roof
• AI features treated as architecture rather than decoration
• Consultation and marketing support alongside development, which matters because a taxi app without driver and rider acquisition is just software

Worth keeping in mind: Because they offer a range, you need to be specific about which path you want and what’s included in each. Ask for the exact feature list of the white label base before you scope customization.

Best for: Founders who want either a fast branded launch or a custom build and would like to move between the two as the business grows. Particularly strong if AI features are a priority from the start.

2. Burj Code

Model: Custom development only | Headquarters: Dubai, UAE

Burj Code is a purely custom development company, and I want to be clear about that, because it changes who should hire them. They don’t sell a pre-built taxi product that you rebrand. They build your app from the ground up around your requirements.

They work across native iOS and Android as well as hybrid and cross-platform approaches, with Flutter and React Native among the options. For a taxi app that matters. The driver app in particular lives or dies on background location handling, battery behavior and push notification reliability, and those are exactly the places where framework and architecture choices show up. On the project where I worked alongside them, what stood out was the care they took in the driver app’s location pipeline and how they handled the realities of unreliable connectivity, such as queuing updates and recovering gracefully when a driver goes through a tunnel.

Because everything is built to your specification, you can get things a white label product wouldn’t easily allow: an unusual dispatch model, integration with a legacy fleet management system, a specific regional compliance flow, a bespoke fare calculation tied to contract rates. The Gulf and wider MENA market experience also matters if you’re building for a region with its own payment methods, language requirements and regulatory expectations.

What I valued:

• Genuine engineering care in the parts of the app that are hardest to get right
• Flexibility on technology choices rather than forcing a single stack
• A good fit for regional and requirement-heavy builds

Worth keeping in mind: Custom is slower and costs more, and you carry first-version risk. Budget for a longer timeline, and be disciplined about scope, because custom projects drift when requirements aren’t pinned down early. If your needs are standard, a white label route will almost certainly get you to market sooner.

Best for: Businesses with truly specific requirements, existing systems to integrate with, or regional needs that off-the-shelf products don’t cover, and the budget and time to build properly.

3. Make An App Like

Model: White label only | Headquarters: London, UK

Make An App Like works from the opposite end of the spectrum from Burj Code. They publish ready-made clone apps across many categories and are built around deploying them quickly, often within one to two weeks according to how they position their offering. If you want a branded taxi product live fast and at a modest budget, this is the kind of provider that makes it possible.

What I’ve valued in working with their approach is the speed to something testable. For a founder who needs to prove that riders will actually book through his app and that drivers will actually log in, getting a functioning product into real hands in a couple of weeks is worth a great deal. You learn more from two weeks of real bookings than from two months of specification meetings.

The honest limitation is depth. A ready-made product gives you the standard feature set well, but it won’t match a custom build for unusual requirements, and the AI layer in a ready-made taxi product is typically lighter than what an AI-native custom or hybrid build would give you. Before committing, I’d confirm exactly which taxi features are in the package you’d receive, whether the source code is included, what license you get, and how updates and support work after launch.

What I valued:

• Speed from decision to a live, testable product
• Low entry cost, which leaves budget for driver acquisition and marketing
• A sensible route for validating a market before bigger investment

Worth keeping in mind: Treat it as a strong first stage. Many operators will eventually want deeper customization, so understand early what the path to that looks like.

Best for: Early-stage founders and small operators who need a branded taxi app quickly, want to validate demand, and don’t have unusual workflow requirements.

4. Sell My Code

Model: White label source code marketplace | Headquarters: Global (online)

Sell My Code is different from the others, and it matters to be precise about how. It’s a marketplace for production-tested source code rather than a development agency. You buy a codebase, you receive it with a commercial license, and you or your team deploy and customize it.

For the right buyer this is extremely efficient. The package typically includes the rider and driver apps and an admin dashboard, the repository is transferred to your own account straight away, and you own the code without ongoing license fees. In my experience the support period and hosting arrangements that come with purchases are also a useful safety net during the first months after launch.

The decisive question is whether you have the engineering capacity to take it from there. A purchased codebase is a starting point. Customizing it for your market, integrating local payment gateways, hardening it for scale, adding AI features that aren’t in the base package, and maintaining it over time all need developers, either in-house or engaged separately. I’ve seen this model work beautifully for teams with a capable CTO and badly for non-technical founders who assumed the code would run itself.

What I valued:

• Full source code ownership with no recurring licensing
• A cost-efficient base for teams that can build on top of it
• Freedom to choose your own developers, hosting and roadmap

Worth keeping in mind: You’re buying code, not a partner. Plan for the engineering work that follows, and review the code quality and architecture with someone technical before you commit.

Best for: Technically resourced founders and development teams who want to own their platform outright and are comfortable customizing and scaling it themselves.

5. Prebuilt Apps

Model: White label, ready-made apps | Delivery: Global

Prebuilt Apps also sits in the white label category, offering ready-made application solutions that you adapt and launch rather than building from scratch. For a taxi business that means starting from an existing booking platform and focusing your effort on branding, market configuration and getting riders and drivers onto it.

Where I found this approach most useful was for operators who already knew exactly what they wanted and just needed a competent base to put their name on. The value is a shorter path to launch and a lower cost than commissioning a build. As with any ready-made product, the details determine the outcome. The quality of the driver app, how the dispatch logic behaves, the depth of the admin panel and the strength of the pricing module vary between products, so it pays to test the demo apps properly on real devices rather than relying on feature lists.

I’d also be direct about AI. If advanced AI features (predictive dispatch, intelligent pricing, fraud detection) are central to your plan, ask what’s actually built and running in the product you’d receive, and what would need to be developed separately. That conversation will tell you whether it’s a good fit or a starting point that needs additional work.

What I valued:

• A quick route to a working, brandable product
• Straightforward economics for operators with standard needs
• A reasonable foundation for teams planning to extend the product themselves

Worth keeping in mind: Test before you buy, confirm what’s included in the taxi package, and be clear on source code access and support terms.

Best for: Operators and startups who want a standard taxi platform under their own brand, quickly and economically, and who will manage their own roadmap afterwards.

How the Five Compare at a Glance

If you want the short version, here is how I’d summarize them.

• Triple Minds: custom and white label, strongest on AI-native features, good for founders who want flexibility to move between models
• Burj Code: custom only, strongest for bespoke and regional builds, requires more time and budget
• Make An App Like: white label, strongest on speed and low cost, best for validating a market quickly
• Sell My Code: white label source code, strongest on ownership and cost efficiency, needs your own engineering
• Prebuilt Apps: white label, strongest for standard brandable launches, check AI depth before committing

The most important point is that these aren’t ranked from best to worst. They’re arranged by what they do, and the right one depends on you.

How I’d Choose Among Them

When I advise a founder, I walk through a few questions in order, and the answers usually point to a clear starting place.

Do you have unusual requirements that a standard taxi platform can’t handle? If yes, because of fleet system integration, a distinctive service model or specific regional rules, you’re looking at custom, and Burj Code or the custom side of Triple Minds is where I’d start.

Do you need to be live within weeks to test the market? If yes, white label is the sensible path. Make An App Like, Prebuilt Apps and the white label side of Triple Minds are all built for this.

Do you have your own developers? If yes, Sell My Code gives you the most ownership for the least money. If no, choose a provider that supports you after launch instead of one that only hands over code.

Is AI a priority from the start? Then ask every candidate to show you the AI features running in a live product, and pick the one that can. This is where I’d lean toward an AI-native provider.

Are you unsure? Then start with white label, learn from real rides, and add custom features once you know what your market wants. The expensive mistake is committing to a full custom build before you’ve watched a single real passenger use the product.

Questions I’d Ask Any Taxi App Agency

Whichever company you shortlist, these are the questions that have saved my clients the most trouble.

• Can I use a live taxi app you’ve delivered, as a rider and as a driver, on my own phone?
• How does the driver app handle background location, poor connectivity and battery use?
• What exactly happens at ten thousand rides a day, and has the platform been tested at that load?
• Which AI features are built and running today, and which would be new development?
• Do I receive the full source code, under what license, and can another team maintain it?
• How is the pricing engine structured, and can it support surge, corporate accounts, subscriptions and promotions together?
• What does support look like in the first ninety days after launch, and who responds when something breaks at midnight?
• How are payments, driver verification and rider safety handled, and what compliance work is expected from me?

An agency that answers these specifically and without defensiveness is usually one you can work with. Vague answers are the warning sign.

What I Told My Client

Here’s the recommendation I eventually sent. His situation was a real operator with a loyal driver base, a clear local market, no in-house developers and a launch window of a few months. His competitive edge was operations, not technology.

I told him to start with a white label route, with Triple Minds as my first call because he could launch quickly, keep the option to customize, and get AI-assisted dispatch and support without commissioning it from scratch. I suggested he treat the first three months as a market test, track cancellations, ETA accuracy and driver utilization closely, and only then decide which custom features were worth building. I told him that if his needs turned out to be more specific than he expected, Burj Code was where I’d go for a bespoke build. And I told him that if he later brought a technical team in-house, Sell My Code would be worth a look for owning the platform outright.

He wrote back with one line: “That’s the first time anyone has told me when not to build.” That sentence is the best summary of how I’d approach this decision. The goal isn’t to buy the most impressive technology. It’s to match the model to the business you actually have.

Pick the one that fits your situation, test it on real devices, and put the money you save into the part of a taxi business that actually wins: reliable drivers, fair pricing and riders who trust the app.

Support writers. All our nonprofit’s offerings here.

Click here to subscribe to the IT Chronicles newsletter.

Click for Wordsmith, Mystery Writing, Write Like Stephen King, more

Best Taxi App Development Companies in 2027 was originally published in IT Chronicles on Medium, where people are continuing the conversation by highlighting and responding to this story.

The case for an office of global experience architecture

I delighted in birds chirping and the sun rays piercing the clouds as I sauntered over the cobblestones into a local cafe. Pale pink dress with lace trim at my décolletage, a gentleman held the door and I murmured thanks into the quiet of the morning.

At the wood counter I asked for an espresso with a tilt of my brow. There is an unhurried pace to life in the little village in Europe where I lived. I “dressed” every time I went out, according to American standards. I took a trip to see The Birth of Venus and enjoyed walking the same streets as da Vinci. A bouquet holder, (aka tussie mussie) dangled from my wristlet, a Victorian era configuration to carry flowers. The care with which the small bouquet holder is like a mini-work of art, flowing geometric curves and silk ribbon, is astoundingly intricate by today’s standards. But need not be! Another time I walked under Roman viaducts. I dined in the alps, gazing at the cows that produced the milk that created the fondue I dipped fresh baked bread in. There is courtesy in published spaces, drivers giving way and little assists throughout the day. The sense of community and congeniality is strong.

Returning to the USA and trying to navigate a subway late at night felt like being a Disney character leaving the animated world and being dropped into a brutalist void.

US public spaces have seen a theft of beauty!

Our public spaces have suffered a theft of beauty and state-sponsored sensory poverty comes at the cost of morality, civility, and wellness. Our public spaces are in need of a masterclass. Beauty is a right. A civil right. A human right. I call for a renewed effort to support human flourishing. We can combine the work of historic legends with the latest research, to be a global leader in human flourishing.

Public spaces are meant to invoke awe, curiosity, wonder, and pride.

We are currently derelict in leaving a legacy in how we steward public and business spaces in the US. We have a public health crisis because of the lack of sensory governance and neuroception in our planning. Redlining in our public design has deepened the divides among communities. Neglected and negative design, such as spikes on benches, have been used as a tool of systemic oppression. Polarity in political ideology is magnified by this crisis. Ugly keeps us in a fight-or-flight state that makes it easier for us to hate our neighbors. Attending to global experience architecture is more than luxury.

Beauty is a biological support for social cohesion.

Nowhere is this sensory poverty more aggressive than in the rapid expansion of AI data centers. I live in a town that was the first in the US to restrict data centers. These windowless AI factories are the ultimate technophony: vibration-heavy, 100-decibel monoliths that can be heard two miles away. They are often situated in vulnerable communities, where their unrelenting low-frequency hum and artificial night-glow act as a modern form of design-based redlining. They don’t just use our water and hike our energy bills; they colonize our silence. The theft of silence is the theft of health! Erosion of our sensory environment is not inevitable; we have seen that intentional governance can not only stop but reverse the rot.

Beauty may be expensive but ugly is even more so.

The resulting sensory poverty takes a devastating toll in the form of healthcare costs, policing, and lost productivity. Not to mention lost delight!

“The first business of the philosopher-king is to look to the soul… Government exists not for the sake of life only, but rather for the sake of the good life.” -Aristotle in Politics, Book III.

The towering intellects of antiquity remain our enduring vanguard, illuminating the path toward systemic renewal. We have built one of the greatest civilizations, let us not cease to evolve. The goal is not trying to law society into submission. But the state is responsible for providing guardrails to ensure a lack of sensory poverty and equitable access. The state should also guide new development and support the revision of existing infrastructure.

The path guided by how to best human.

Government, then, is tasked with providing unalienable laws limiting lack of beauty for all, and supportive guidance in getting deep knowledge into practice.

“Laws are made for the sake of the good men, not to teach them how to avoid wrongdoing, but to provide them with a guide for living together in harmony and achieving greatness.” -Plato

Pillars of Beauty

“There are only two ways to live your life. One is as though nothing is a miracle. The other is as though everything is a miracle” -Albert Einstein

Here are tenets of beauty to consider at a personal and systems level for crafting environments that support human flourishing, along with a Socratic Probe each uses to address: Is the state supporting beauty/joy/love/cohesion?

1. Purity | Cleanliness as Care
   Socratic Probe: Does the chronic accumulation of waste and visual clutter permanently drain the baseline executive functioning and cognitive bandwidth of the public or do our shared thoroughfares signal an agile, disciplined government that respects its inhabitants?
2. Architecture
   Socratic Probe: Are the sharp, sterile angles of modern commercial infrastructure engineering a state of spatial alienation and neurological distress, or are we actively integrating biophilic geometry, color psychology, and mathematical harmony to down-regulate cortisol levels?
3. Movement | Choreography of Kinesthetics
   Socratic Probe: Are our transit pathways and public squares being designed as hyper-efficient, sterile corridors meant to rush human bodies through a frantic maze of consumerism, or are they choreographed using spatial rhythm to facilitate dignified, multigenerational connection?
4. Sound | Acoustic Design
   Socratic Probe: Does our municipal zoning permit windowless technology factories and data center technophony to colonize our silence and trigger chronic sympathetic alert states or does the state demonstrate support of invisible nervous system regulators in the form of peace and quiet as a fundamental right?
5. Lighting | Circadian Governance
   Socratic Probe: Does photic pollution and dependency on high-intensity, hostile 5000K streetlights trap the public in a permanent state of artificial high alert or does the state sponsor support of the physiological organ baselines of our community?
6. Nature | Natural Access
   Socratic Probe: By abandoning our landscapes to sterile turf grass monocultures and unkept concrete corridors, are we inflicting a redlined design-based trauma on vulnerable communities that strips children of the calculated risk required to learn situational safety or is the state investing in biodiversity and organic landscaping as is planned by top scientists?
7. Food | Gastronomy & Localized Foodways
   Socratic Probe: Have we permitted our public planning to be so colonized by highly processed corporate monopolies or is the state designing local access to nutrient dense local produce and quality protein?
8. Language | Linguistic Topography
   Socratic Probe: Does corporate monetization flatten linguistic heritage and generic utility severely contract the internal mind’s architecture and the behavioral morality of our citizens or does the state support geographic nomenclature and public signage?
9. Time | Temporal Governance & Civic Legacy
   Socratic Probe: Do we build our civic spaces out of cheap, disposable synthetic materials designed to decay in a generation, thereby inducing a state of constant, subconscious uprootedness and temporal amnesia or does the state show evidence of the belief time is love?

“True law is right reason in agreement with nature; it is of universal application, unchanging and everlasting… It summons to duty by its commands, and averts from wrongdoing by its prohibitions.”
-Marcus Tullius Cicero (106–43 BCE) in De Re Publica Book III

Now that we have established beauty as a fundamental purpose of the state, let us explore each axiom with more depth.

Purity | Cleanliness as Care

“Cleanliness is the hallmark of perfect standards and the best proof of the care which a government has for its people.”
— Lee Kuan Yew in his memoir, From Third World to First: The Singapore Story: 1965–2000

Lee Kuan Yew is the founding father of modern Singapore. He transformed a decaying city into a global oasis. He focuses heavily on cleanliness as a path to create life ease.

Core Principle

Cleanliness is Care! Decreasing spatial and environmental litter directly decreases cognitive clutter, optimizes executive functioning capabilities, and builds collective civic trust. The physical purity of shared spaces is a foundational capital asset that directly dictates a population’s capacity for complex problem-solving, educational performance, and baseline social cohesion.

Systemic Interventions

• Civic Care Infrastructure Grants: Directing federal funding to municipalities to construct and maintain dignity-focused public hygiene utilities — such as showers and changing rooms at all public beaches, transit hubs, and municipal parks. Make garbage cans sealed from pests.
• Odorless Air & Soil Remediation Mandates: Establishing strict regional standards for environmental purity. This includes binding regulations that target industrial soot, chemical odors, and soil contaminants, recognizing that true air quality is completely odorless and foundational to public health. Degraded soil quality from monocrops, pesticides, and artificial fertilizers has led to soil that is less healthy and produces vegetation that is less tasty, aromatic, and nutritious.
• Correct Market Failures: Purity is the natural baseline, and chemical contamination is the deviation that must be penalized. In economics, chemical runoff and soil destruction are called “negative externalities” which are hidden costs that corporations offload onto public health systems and taxpayers. Any foods and farms not organic or free-range must be taxed penalties severe enough to make organic and free-range fiscally responsible alternatives. Make toxic cheap no longer.
• Sensory Clutter Restrictions: Empowering the commission’s enforcement arm to fine municipal bodies or commercial entities that leave public squares in states of aggressive neglect, treating chronic litter and visual blight as a direct violation of sensory governance.

Foundational Anchoring:

Cleanliness and organization help people think and behave better. When a government permits its public and business spaces to rot, it communicates a profound lack of care to its most vulnerable populations, triggering a subconscious alert system that forces citizens into a defensive, hyper-vigilant state. Cognitive research proves that clutter directly impairs focus, diminishes test scores, and suppresses workplace productivity. Conversely, physical purity and structural order act as an agile, disciplined shield that down-regulates anxiety and fosters deep social trust. Clean air, water, and soil are intertwined in multiple pillars, and foundational to the interconnected web of the good life. A society cannot achieve greatness or live in harmony if its everyday environments keep its people in a state of sensory poverty.

Architecture

“Architecture is frozen music.”
— Johann Wolfgang von Goethe as recorded by Johann Peter Eckermann in Conversations with Goethe (Gespräche mit Goethe), March 23, 1829

Johann Wolfgang von Goethe was a German polymath who believed that the proportions of a building should have the same harmonic math as a symphony.

Core Principle

We achieve somatic harmony by looking to biophilic geometry and utilizing classical architectural principles and contemporary neuroaesthetic design theories to guide the physical construction of all public and corporate infrastructure. The built environment must incorporate biophilic structures, mathematical harmony, color psychology, and organic curved lines to actively down-regulate cortisol and foster a baseline sense of human safety.

Systemic Interventions

• Biophilic Material Integration Grants: Establishing a federal funding pipeline to incentivize the use of raw, natural, and biologically supportive materials — such as smoothed stone, solid native timber, wrought metal, copper, and structural linen — in all new civic infrastructure. Copper is naturally antibacterial. Wool is naturally fire resistant. Linen is so healing it speeds wound closures and saves lives. Hempcrete is the perfect permeability that allows a building to breathe. Nature has already engineered the highest, most resilient standard of care available.
• Endocrine-Disrupting Chemical (EDC) Bans: Enforcing prohibition on toxic, synthetic chemicals (such as PFAS, microplastics, cheap synthetic laminates, and off-gassing sheetrock coatings) within public textiles, civic seating, and commercial apparel infrastructure. The onus on shoppers to research and avoid hormone disruption in appeal is a failure of the state.
• New Materials Certification: New materials must undergo testing to certify safety before introduction, not after as is the current modus operands — releasing harmful materials and wait for humans as guinea pigs to report problems. This corrects the profound ethical bankruptcy in corporate manufacturing and modern chemical governance seen in the USA.
• National Architectural Curriculum Directives: Issuing standard-of-care guidelines to American architectural educational programs to reintroduce glorious curved lines, structural alignment, and Christopher Alexander’s principles of architectural philosophy, directly countering the systemic over-standardization of sterile commercial design.

Foundational Anchoring
We used to see recognizable, time specific architecture being erected. Today, modern cheap buildings go up with sharp angles and a dearth of curved lines that look devoid of specificity to any time or place. They are not timeless, they are worthless. We took pride in our city skylines and can once again. This global “blandemic” of boring buildings causes severe sensory alienation and psychological distress. As Thomas Heatherwick fiercely calls for a,

passionate call to arms, urging readers to get enraged about the global “blandemic” of boring buildings. “Intense and dreadful changes have been creeping through our towns and cities for the last 100 years, bringing with them destruction, misery, alienation, sickness and violence,” he writes. The outsides of buildings around the world have become “boring”. He admits this is a “rubbish-sounding” word that “doesn’t do justice to the harm it describes”, but settles with it as the best way of evoking a “century‑long global catastrophe”.

excerpt from an interview of Thomas Heatherwick as appeared in The Guardian.

The sanitization of space strips the built environment of texture, warmth, and natural mystery. Human hands require haptic interaction with textures that hold physical weight, organic warmth, and antimicrobial harmony to regulate the nervous system. Integrating natural materials like wool offers an elegant contrast to cheap synthetics that require a barrage of industrial chemicals to achieve basic safety standards. Reclaiming our city skylines is not an act of sentimental daydreaming; it is the structural preservation of human flourishing.

More in Thomas Heatherwick’s book Humanize (I recommend BookShop.org for online book purchases), and Christopher Alexander’s The Nature of Order.

Movement | Choreography of Kinesthetics

“Dancers are the athletes of God.”
-Albert Einstein thematic essays The World As I See It

Albert Einstein (1879–1955), was a revolutionary theoretical physicist and polymath who re-engineered our understanding of the universe through the fluid dynamics of spacetime. Beyond his contributions to quantum mechanics and relativity, Einstein was deeply attuned to the invisible, harmonic laws of nature, recognizing that human movement and physical geometry are fundamentally interconnected dimensions of kinetic energy.

Core Principle

A choreography of movement of young and old and everyone in between! Arranging public structures and physical pathways using the principles of spatial rhythm, somatic geometry, and kinetic flow. The physical transit of human bodies through space must be engineered to transform everyday navigation into an experience of effortless connection, biological alignment, physical poise, and absolute human dignity.

Systemic Interventions

• The Civic Rest Utility Mandate: Requiring the integration of beautiful, organic, curved, and dignified public seating configurations regularly within all pedestrian corridors and public transit hubs, legally treating physical rest as a basic, guaranteed public utility. Removal of spikes or tools designed to inhibit laying.
• Somatic Flow Path Infrastructure: Mandating that all master public square pathways, crosswalks, and gallery entries deploy advanced fluid dynamics, pedestrian crowd hydrology, and kinesiology mapping to structure walkways that organically facilitate healthy pauses, natural community dialogue, and comfortable connection.
• Choreography of Ages: Designing multigenerational spaces where kinetic flow allows children, adults, and seniors to co-exist in movement. This includes gentle labyrinth walking paths, physical public puzzles, tactile barefoot pebble walks, and shared architectural landmarks that compel spontaneous cross-generational interaction.

Foundational Anchoring

A somatic choreography! Arranging physical spaces using the principles of spatial rhythm and kinetic flow, transforming everyday transit into an experience of effortless connection and dignity.

Public architecture cannot be viewed or judged purely as a static monument; it is actively experienced through the raw physics of the human body in transit. Rooted in a deep understanding of structural alignment and dance pedagogy, this dimension addresses how a society moves. Rather than engineering public spaces as hyper-efficient, sterile corridors designed to rush a human body through a frantic maze of hyper-consumerism, we must prioritize spatial rhythm.As the phenomenologist architect Juhani Pallasmaa noted, “Architecture is the art of structuring and staging human experience, including movement, rest, and encounter. It is a form of choreography that shapes our behavior, perception, and emotions.” Modern architectural educational frameworks have completely severed human emotion and physical geometry from their training, resulting in spaces that leave communities feeling alienated and hyper-vigilant. True sensory governance honors the choreography of ages, constructing environments where children, adults, and seniors co-exist in beautiful, fluid kinetic harmony. Rest and movement must be balanced to reclaim the somatic poise of our civilization.

Public architecture shouldn’t be viewed statically; it is experienced through the physics of the human body in transit. Rooted in deep understanding of structural alignment and dance pedagogy, this pillar addresses how a city moves. It tackles the physical pathways of public squares, crosswalks, transit hubs, and galleries. Rather than engineering public spaces as hyper-efficient corridors designed to rush a human body through a maze of consumerism, it focuses on the choreography of space — structuring walkways to organically facilitate pause, mutual gaze, micro-moments of natural community dialogue, and a somatic sense of physical poise.

Christopher Alexander’s view of architecture deeply accounts for how people move within a space, (in fact, he argued that human movement, behavior, and emotional experience are completely inseparable from the physical geometry of a building) but as not all schools of thought teach this to modern architects, this pillar is borne.

More on this as well as my personal form of movement: Athletes and Angels, and the Soul of Dance.

Nature | Natural Access

“Air is disinfected by sunlight and foliage… We require such an consumption of natural landscape as can only be obtained through the structure of public parks. …the low-rate of health, physical and mental, which belongs to a population living in a state of high-density… can be directly countered by providing the simple, natural recreation of walking among trees and enjoying their grateful shade.”
 — Frederick Law Olmsted in his foundational address Public Parks and the Enlargement of Towns

Frederick Law Olmsted was the father of American landscape architecture (Central Park). He argued that green space was a public health requirement for a democratic society.

We delight in access to nature, are kinder and solve problems better. Our mood is also improved [refer to citations 12–25]. For example, Attention Restoration Theory (ART) is a foundational framework that proves that natural environments relieve “directed attention fatigue,” allowing the brain’s executive functioning capabilities to rest and recover.

As I drove through a blighted urban corridor, the kind that exists in every major US city, the sight of the unkept vegetation on the boulevard and litter everywhere raised my alert system. Urban greening is an act of civic pride and long-term legacy. The environment we create should not be a conquest of nature but an extension of its natural flow and balance.

Core Principle

Natural Access — Exposure to natural, self-sustaining ecosystems is an unalienable natural right required for human flourishing. Deploying macro urban-greening, indigenous flora networks, and biodiverse ground cover serves as a critical biological buffer for public health, cognitive replenishment, and national economic resilience.

Systemic Interventions

• The Low-Maintenance Ground Cover Directive: Funding state and municipal transitions away from invasive, water-thirsty turf grass monocultures toward self-sustaining regional sanctuaries of creeping thyme, endemic flora, and native wildflowers to anchor the natural water cycle and mitigate flash floods. Also encourages pollinators, butterflies, birds, and fireflies.
• Scent-Scaping: Implementing active Olfactory Architecture by zoning aromatic flora networks — such as lavender, jasmine, pine, or mint — along high-stress transit corridors and public squares to subconsciously lower public aggression and cultivate an organic sensory sanctuary.
• Autonomous Regional Supply Chains: Establishing dedicated federal networks for organic, circular, and health-supportive civic materials — such as raw flax, local wool, plant-based dyes, and natural waxes — to entirely phase out synthetic, toxic options from public landscape design.
• Design-Based Risk Reintroduction Frameworks: Overturning the sterile over-sanitization of public play and civic spaces designed by lawyers and corporate HR departments. The sanitization of public life strips spaces of texture, variation, and natural mystery renders them sterile, alienating, and ultimately unsafe in their banality. Public parks must intentionally integrate variations, natural textures, mystery, and calculated environmental risk to challenge human logic, teach children situational safety, and keep adults dynamically engaged in the present.

Foundational Anchoring
Over a millennium prior, the Greek polymath Theophrastus laid the botanical groundwork for this continuity, proving that human vitality is inextricably bound to the structured harmony of living plant systems. When a state abandons its landscapes to litter and unkept, blighted concrete, it communicates to its citizens that they hold no value, inducing a hyper-vigilant state of neuroceptive threat that forces individuals to construct psychological walls against their neighbors.

psithurism: The sound of wind blowing through trees, a word that comes from the Greek term for whispering

Why do we invent such words? The lingering delight of sound! Nature sounds soothe us and lead us to work, laugh, and love better.

We celebrate psithurism because natural acoustics and soft visual awe are biological homing signals that soothe directed attention fatigue, allowing the brain’s executive functioning capabilities to rest, recover, and sharpen working memory. The awe that comes from gazing up at a tree compliments the peace from its shade.

The data is unassailable! Often cited in urban sociology, dirty public spaces communicate to the public that they are not valued by the state. Do not mistake this as sentimental emotional daydreaming. Park access alone fuels 1.65% of global GNP [Ref 3], boosts workplace productivity by up to 11% [Ref 13], as nature acts as a buffer against mental health-related performance losses, and significantly improves working memory, cognitive flexibility, and attentional control (scores 20% higher on memory recall [Ref 19], and yields a 50% increase in creative problem-solving [Ref 16]). Conservation investments yield significant returns by reducing public health costs, with ratios typically reaching 4:1 nationally and as high as 11:1 in specific states [Ref 4]. Residents in green environments report fewer violent crimes and fewer “incivilities,” which lowers the public cost of policing and surveillance [Ref 12]. Beautification is the only proven method for litter reduction [Ref 10]. Every $1 invested in federal conservation saves up to $7 in future disaster costs related to floods and wildfires [Ref 4 & 11]. A mere 20 minutes in a natural setting has been found to improve concentration and reduce the need for ADHD medications in children [Ref 18 & 24]. Historically, manicured lawns emerged as a sterile status symbol akin to expensive blank flyleaves on luxury paper volumes; lacking intentionality, they became our default. True sensory governance re-wilds our shared soil, transforming public spaces from concrete jungles into self-sustaining sanctuaries where butterflies dance and humanity flourishes.

More of this in Rewilding, Beyond Yards, Historia Plantarum (Enquiry into Plants) and De Causis Plantarum (On the Causes of Plants).

Lighting | Circadian Governance

“We find beauty not in the thing itself but in the patterns of shadows, the light and the darkness, that one thing against another creates.”
— Jun’ichirō Tanizaki: Author of In Praise of Shadows

Jun’ichirō Tanizaki (1886–1965) was one of the most formidable and celebrated twentieth-century Japanese authors, whose literary legacy focuses heavily on the profound tension between traditional Japanese aesthetics and the rapid encroachment of Western modernization. In his seminal 1933 essay In Praise of Shadows (In’ei Raisan), Tanizaki established a foundational philosophy of sensory neuroception, arguing that the Western obsession with clinical, uniform brightness destroys the essential nuance, shadow, and indirect illumination required to settle the human nervous system. His work provides the bedrock philosophical anchoring for circadian governance, proving that texture, soft amber frequencies, and spatial darkness are not merely decorative preferences, but vital biological sanctuaries necessary to foster safe social engagement, civic congeniality, and deep psychological grounding.

Core Principle

Protecting physiological organ baselines requires implementing lighting systems that dynamically match the solar spectrum to support natural circadian rhythms. Light determines the baseline psychological grounding, metabolic health, and neurological mood of a space. The state has a moral and regulatory obligation to eliminate state-sponsored photic pollution, ensuring that artificial lighting architectures act as a supportive sanctuary for human biology rather than a chronic threat mechanism.

Systemic Interventions

• The National Dark Sky & Photobiology Directive: Mandating a comprehensive federal phase-out of high-intensity, hostile 5000K fluorescent and blue-rich LED streetlights in all public municipal zones. These will be replaced by dim, warm, sun-mimicking tones (under 2700K) in the evening to protect the public’s natural melatonin production and sleep architecture as well as re-regulating insects.
• Spectral Impact Assessments (SIA): Requiring all new public infrastructure, transit hubs, and commercial skyscrapers to submit photobiological lighting blueprints prior to approval. Built environments must demonstrate a rhythmic transition from high-intensity natural spectrums during the day to soft, indirect, low-altitude amber frequencies after dusk.
• Circadian Workspace Standards: Enforcing workplace infrastructure updates that mandate ten minutes of natural sunlight access during the morning, midday, and evening for all workers, while eliminating toxic, unshielded fluorescent overheads in favor of diffused, biologically aligned lighting layers.

Foundational Anchoring
Bright lighting destroys the nuance and indirect beauty essential to a peaceful soul. Fluorescent lighting keeps the American public in a state of high alert (sympathetic nervous system), whereas the sanctuary design of the old European and Middle Eastern construction allows for social engagement. We have traded away the deep, restorative medicine of the night for an aggressive, artificial glare. Modern American public lighting forces citizens into a permanent reactivity of a destructive, chronic activation of the sympathetic nervous system. Lighting can allow the nervous system to settle into its ventral vagal state, fostering safe social engagement, local trust, and civic congeniality. The toll of sensory poverty in lighting is silently devastating. While terrible lighting does not show an immediate, visible financial cost, current research proves it causes a systemic decrease in the performance of vital biological systems, quietly compromising metabolic pathways (kidneys), liver, and cellular repair networks [Ref 26, 27, & 28]. Your conscious mind might remain unaware of the invisible photic strain, but your body is deeply aware [Ref 28]. True sensory governance recognizes that light sets our internal biological clocks; by reclaiming natural illumination architectures, we directly restore public health, reduce institutional healthcare burdens, and invite a quiet renaissance of human flourishing back into the night. Let us bring this need to light.

More on this in Lumen & Lore parts I - III.

Sound | Acoustic Design

“A healthy city should sound like a forest, not a factory.”
— Bernie Krause

Bernie Krause is a bioacoustician who records “the great animal orchestra.” His work says humans feel safe when they hear biophony (life) like birdsong rather than mechanophony (machines).

Core Principle

Peace and quiet must be recognized as an invisible nervous system regulator and a fundamental civil right that citizens have a right to defend. The commission treats the sonic environment as critical civic infrastructure. We must actively protect human biology from the aggressive expansion of modern technophony — the unrelenting, machine-driven noise pollution that triggers permanent sympathetic nervous system alert states and fractures social cohesion.

Systemic Interventions

• Soundscape Planning: Mandating that all enterprise-scale infrastructure, commercial developments, and high-density transportation corridors integrate active acoustic design prior to federal zoning approval. This requires utilizing natural materials, structural topography, and “soundscaping” techniques — such as moving water, rustling native leaves, and acoustic barrier vegetation — to deliberately mask industrial and traffic noise.
• Independent Decibel Enforcement Units: Establishing autonomous monitoring arms within the commission to enforce strict, legally binding decibel caps on commercial technology facilities. This includes immediate, non-negotiable fines and shutdown protocols for vibration-heavy AI data centers and windowless technology factories that violate local peace.
• Pockets of Peace: Injecting dedicated federal funding into local municipalities to construct “Quiet Gardens,” urban bird estuaries, and wind-chime sanctuaries within high-stress civic zones, ensuring quiet tranquility is a guaranteed public utility.

Foundational Anchoring
Sound dictates our immediate, sub-conscious sense of biological safety. Human biology evolves and down-regulates cortisol when immersed in biophony — the vibrant sounds of living nature — whereas constant exposure to mechanophony induces chronic neurological trauma, lost productivity, and heightened public anxiety. The prosody of space dictates that physical arrangements control the rhythm of human connection. To counter modern sensory alienation, our public spaces must be sonically insulated. Precedents found in historical Arabic garden design heavily favor using water not just as a visual centerpiece, but as a precise, kinetic tool for sound masking and nervous system regulation. True sensory governance recognizes that defending our sonic borders is not an indulgence of luxury; it is a baseline requirement for protecting the public health, restoring community trust, and preserving the collective soul of our cities. Sound determines our sense of safety. Prosody of space explores the idea that spatial arrangement dictates rhythm and connection. Who couldn’t use a bit more connection? The sound of joy and peace.

More on this in Sonus and Sanctum and Generations of Peace.

Food | Gastronomy & Localized Foodways

“Tell me what you eat, and I will tell you what you are. A population fed on corporate banality and synthetic processing will inevitably construct a society of high-alert polarity.” -Jean Anthelme Brillat-Savarin in a foundational masterwork, La Physiologie du Goût, 1825

Jean Anthelme Brillat-Savarin, (1755–1826) was an elite French lawyer, politician, and epicure who fundamentally invented gastronomy as a serious academic and philosophical science.

While many view food simply as agriculture or domestic cooking, Brillat-Savarin treated it as a profound lens through which to understand human psychology, biology, and civilization.

Core Principle

Gastronomy and localized foodways supporting human immunity, communal health, and biological resilience by actively engineering ultra-local, nutrient-dense culinary ecosystems. Access to raw, unadulterated, and locally harvested nutrition is an unalienable human right, foundational to fostering micro-moments of positivity resonance and systemic biological well-being.

Systemic Interventions:

• Agricultural Antitrust & Subsidy Realignment: Breaking up corporate distribution monopolies, outlawing seed patents, and redirecting federal subsidies away from corn and soy monocultures toward diverse, regional heirloom vegetable networks. Better cellular quality of the heirloom vegetables yields more nutritious, aromatic, and flavorful produce as does soil regeneration.
• Relabeling & Reorganizing: It is backwards and broken to label organic and require farmers to pay for organic certification. Non-organic foods need to be labeled as pesticide produce and such growers must pay the government to fund regulatory testing to check that the levels are at “acceptable” limits. They must also pay for the stupidity in leaving the soil less healthy than they found it.
• Farm-to-Fork Standard of Care: Do you know I have not been able to eat grilled chicken in the USA? It is fucking gross! USA industrial poultry and meat cannot be sold in the EU! This is a classic example of treating a symptom rather than the cause. The systemic failure of sloppy, low-welfare farming practices with a lack of space, ventilation, strict biosecurity, and high-quality feed during the rearing process result in the USA using a chemical wash at the end as a “fix.” Not only disgusting once you have eaten real normal chicken, but creating poor hygiene among animals, and poor psychological impacts on farm hands. Purity must be maintained throughout the lifespan, not chemically forced at the end.
• Edible Urban Forestry Directives: Mandating that municipal public spaces and community local urban gardens actively prioritize the planting of nutritious, fruit-bearing trees and available heirloom plants for public consumption and wild foraging.
• Sustainable Dining Infrastructure Mandates: Phasing out the over-saturation of highly processed corporate food supply chains in public spaces, while enforcing an absolute ban on single-use, non-biodegradable plastic serving ware in favor of sustainable, circular utensils.
• Macro-Nutrient Fiscal Penalties: Tax ultra-processed corporate manufacturing chains, directing monies towards public medical systems.
• Pre-Market Safety Certification: artificial and “natural” flavors and additives must pay fees to show certification of their safety before entrance into the food ecosystem. Testing must be done by watchdogs, not silent corporate friends. Regulations on all natural foods, including magic mushrooms must be lifted. It is not the government’s role to regulate the natural. It is the role of the state to protect the population from corporate greed that has decimated the nutritional value of the food ecosystem in the USA.

Foundational Anchoring
This dimension bridges environmental aesthetics with biological fuel through L’art de the table — the comprehensive cultural and social practice of hosting, tableware etiquette, ambiance, and enjoying a meal together. Somewhere along the trajectory of modern urban planning, fruit-bearing trees were deemed “too messy” for the public square. The glorious bounty and brilliance of heirloom fruit that could feed passersby, filled the air with heavy fragrance, the beauty and bounty both sweet. This over-standardization represents the corporate McDonaldization of the environment, a systemic banality that strips communities of local logic and problem-solving. True food systems require “heartware” — the emotional, human, and psychological layer of a city that structurally cultivates safety, welcome, and community spirit bolstered by systematic access to resources. When public spaces include nutritious plants available for direct consumption, they foster shared presence. Stewarding the wild things is unbridled beauty, turning daily nourishment into the infrastructure of love. Underpinning all of this is the assumption that access to local food is a human right. Yummm!

More on this in The Physiology of Taste (La Physiologie du Goût), The Scent of Rain, Wildcrafting, and Everyday Miracles.

Language | Linguistic Topography

“The limits of my language mean the limits of my world. When we permit our public vocabulary to be commercialized and flattened, we contract the very architecture of human thought.” -Ludwig Wittgenstein Tractatus Logico-Philosophicus Proposition 5.6

Ludwig Wittgenstein (1889–1951) was an Austrian-British polymath and stands as arguably the most formidable, radical philosopher of the 20th century. While he is traditionally celebrated for fundamentally upending the fields of logic and the philosophy of language, he was also a trained aeronautical engineer and a practicing architect.

Core Principle

Preserving the mind’s internal architecture requires embedding linguistic diversity, historic naming rights, and elevated prose into public frameworks. The state must halt the systemic cognitive erosion caused by a generic, over-standardized lingua franca. Public squares, civic halls, and community spaces must be spatially and semantically engineered to organically foster eye contact, shared presence, and elevated dialogue.

Systemic Interventions

• National Linguistic Heritage Registry: Establishing a federal protection framework to secure historic naming rights for geographic locations, streets, public infrastructure, and civic facilities. This halts the corporate monetization of public spaces (e.g., stadium naming rights, commercialized public squares) and anchors environments in deep historical and regional memory.
• Nomenclature Integrity Protections: Enforcing strict, legally binding geographical naming rights for all regional agricultural and artisanal goods. Without this nomenclature protection in the United States, our consumer markets suffer from subquality industrial products riding on the coattails of historical quality products. Food created and produced using ancestral, hyper-local methods must be legally allowed to maintain the economic prestige and biological purity they built, making toxic duplication fiscally impossible.
• Linguistic Landscape Statements (LLS): Mandating that all municipal rezoning and master-planned developments submit an aesthetic evaluation demonstrating the integration of elevated prose, typography, multi-lingual inclusivity, and historic continuity within public signage and civic installations.
• Beauty in Speech: Narrative guardrails on algorithmic speech protect our collective sensory environment. When violent and degrading language is permitted to spread far and fast online, it fundamentally alters human neuroception, directly degrading social behavior, community morality, and civic trust. Governance has been lax in updating legislation to protect people from hate speech, misogynist/misandrist rhetoric, and highly volatile false news. Linguistic toxicity has been allowed to colonize our collective psyche, directly fracturing communal bonds and social cohesion without check. Conversely, true sensory governance must actively sponsor digital architecture that elevates high-signal curation, artistic merit, and refined prose. By instituting federal grants and prestige frameworks for cultural architects and creators of positive digital media, the state can actively cultivate an online landscape that anchors the public mind in knowledge, beauty, and mutual respect.
• Architectural Propinquity Ordinances: Regulating the spatial layout of benches, courtyards, and community hubs to mandate physical proximity layouts that naturally encourage shared small moments of spontaneous conversation, actively countering the isolation built into modern, distracted spaces.

Foundational Anchoring

Language is the ultimate architect of the human psyche. The erosion of linguistic diversity and the degradation of elevated, intentional speech in public spaces directly mirrors the architectural blandemic of cheap sheetrock and cold steel. When our civic nomenclature is reduced to commercial utility, the mind’s internal topography shrinks.European precedents demonstrate the long-term governance returns of aesthetic preservation. France utilizes a dedicated national authority — the Académie française — to formally regulate grammar, vocabulary, spelling, and official lexicography to protect cultural integrity from dilution. Given that the United States lacks a mandated national language, the commission does not seek to enforce homogeneity; rather, it introduces a necessary standard of care to elevate our public use of language with absolute parity. We must treat words as an essential layer of the civic environment. Public signage, structural inscriptions, and monument typography should not merely dictate direction — they must invite contemplation, honor heritage, and actively lower biological stress through aesthetic beauty. True sensory governance recognizes that the words allowed to echo in our public square directly dictate the behavioral morality of our citizens. As a masterclass in human flourishing, the ultimate baseline for this dimension is simple, timeless, and profound: “For beautiful lips, speak only words of kindness.”

More on this in Echos of the Heart and Reframing The Manosphere: A Public Health Response To A Commercial Ecosystem by Professors Sarah Hawkes and Kent Buse.

Time | Temporal Governance & Civic Legacy

“Time is the most valuable thing a man can spend, for when you honor the rhythm of the seasons, you align your soul with the unchanging law of nature.”
-Theophrastus (371–287 BCE)

Theophrastus was the father of Botany. A Greek polymath, philosopher, and the immediate successor to Aristotle as the head of the Peripatetic school in Athens. While Aristotle laid the massive analytical foundations for Western thought, Theophrastus was the master observer who grounded those heavy philosophies into the practical rhythms of nature, botany, and human character. His entire life’s work was dedicated to studying how living systems, biological rhythms, and human environments interconnect.

Core Principle

Temporal governance & civic legacy is found in time. Anchoring society in historical continuity, material permanence, and ancestral anchoring to combat the placelessness and temporal amnesia of modern development. Human beings require a deep sense of permanence and historical trajectory to feel anchored, safe, and neurologically grounded across generations.

Systemic Interventions

• The 30-Hour Civic Freedom Mandate: Establishing a standard 4-day, 30-hour work week at the federal level to prevent counterproductive labor exploitation, discourage forced overtime, and protect human cognitive bandwidth.
• Algorithmic Containment Directives: Enforcing strict, legally binding restrictions on corporate AI architectures and persuasive design feeds to protect children, insulate vulnerable communities, and systematically eliminate compulsive doomscrolling.
• Generational Material Mandates: Requiring that all new public infrastructure projects pass rigorous durability evaluations proving the use of enduring, regional materials engineered to age gracefully and stand structural strain for centuries, entirely banning cheap quarterly budgeting shortcuts.

Foundational Anchoring:
A public space cannot truly facilitate long-term human flourishing if its physical structures feel disposable, ephemeral, or completely disconnected from ancestral roots and future lineages. We can combat the “placelessness” and temporal amnesia of modern development. Human beings require a sense of permanence and historical continuity to feel anchored and safe. As Cicero masterfully declared in De Re Publica, “True law is right reason in agreement with nature; it is of universal application, unchanging and everlasting… It summons to duty by its commands, and averts from wrongdoing by its prohibitions.” Modern society has allowed short-term corporate cycles to fracture our macro concept of time. When our civic spaces are built out of cheap, synthetic materials designed to decay in a generation, we induce a state of constant, subconscious uprootedness. True sensory governance honors the past while building a protective shield for the future. Restricting the frantic digital intrusions that colonize our attention allows communities to reclaim the slower rhythms of human connection. By treating time not as a corporate commodity, but as a space for shared flourishing, we align our civilization with its ultimate purpose. New infrastructure cannot be built for immediate utility or cheap quarterly budgets. It mandates the preservation of local historical narrative, the use of enduring regional materials meant to age gracefully across centuries, and design that deliberately honors both ancestral heritage and future legacy. True legacy demands a commitment to permanence, reminding us that Time is Love.

The Infrastructure of Love: Civic Legacy in the form of Office of Global Experience Architecture

“We shape our buildings; thereafter they shape us.”
— Winston Churchill

For Easter, my family visited a charming town with boutique stores only (city ordinance forbidding chain restaurants and stores) in the US. It was overflowing with blossoms, trees, boutique shops, artisan restaurants, and the urban design encouraging walking. Wisteria bloomed inside of one store and a cafe next to it sourced all their ingredients locally for a small but nutrient dense menu (not an oligopolistic Sodexo truck in sight!). People working slowed for mico-moments of positivity resonance–connection and conversation. Expand these pockets of perfection by creating a National Office of Global Experience Architecture. Standard of care is a moral constitutional duty. Historic cities like Florence have strict guidelines in place to preserve history. Lacking the age of those places, we need visionary leadership to help drive systematic scaling of the beauty that we do have in the US. With such support we would see more small businesses thrive and greater economic resilience.

This move would honor the deeply interconnected nature of life. By housing these elements jointly it would allow for agility that is lacking in current American governance systems. The McDonaldization of Americans has led to over-standardization. The cult-like banality of standardization has led to a loss of logic and local problem solving. The goal of a national office would include basic standards of human decency to be regulated as pro forma. We have profoundly lack of care for our most vulnerable communities. Regulations are needed to eliminate conditions that no person should have to endure. But mandates will not overreach, but rather, allow room for local flavor in all pillars. The goal is not to create uniform looks of vibe to the country, but to mandate standard of care for all, and encourage flourishing through the dissemination of best-in class planning resources and information.

“Legislators make the citizens good by forming habits in them, and this is the wish of every legislator, and those who do not effect it miss their mark, and it is in this that a good constitution differs from a bad one.”
 — Nicomachean Ethics

A national office of Global Experience Architecture could provide thought leadership on concepts that use deep ancient knowledge to support modern flourishing. “National” being the physical jurisdiction of the governance and funding (the where). “Global” in this case defines the scope of the intelligence, heritage, and luxury ethics being utilized (the what). Such leadership in the form of an independent federal regulatory commission, which like the Federal Communications Commission (FCC) and Securities Exchange Commission (SEC) possess independent regulatory power, their own enforcement arms, and the mandate to write binding rules within their domain. There are legal precedents (the FCC and SEC), and a biological justification for its cross-disciplinary authority. It would issue Sensory Governance Guidelines that existing departments (like the DOT, HUD, and Labor Department) must integrate into their frameworks. Current departments do not move with enough agility; to regulate the sensory landscape a single office must possess the cross-disciplinary authority to defend human biology from systemic trauma. The result being shifts such as mandating decibel buffers for AI data centers and incentivizing curved lines and biophilic structures to lower cortisol. In using research, they could support people and systems with policy guidance, such as phasing out 5000K fluorescent streetlights for circadian-aligned warm lighting. Civic respect would be one of the bonuses added to the return on investment. All systems are interconnected.

Attending to experience architecture is naught mere indulgence. It is the infrastructure of love. By prioritizing sensory governance, we can move from a state of high-alert polarity to one of shared flourishing. Beauty is a biological necessity, a public health tool, and a driver of civic economics.

Beauty by design: A new iteration of love!

From Love 2.0 to love 1.618 phi (φ).

As a strategic brief, this piece is conceived as a catalyst for dialogue and collaboration.

If you have or know of a piece that you would like linked to this brief, feel free to email the author.

What beauty have you seen that inspires?

References

Bioacoustics & Sound Theory
1. Krause, B. (2012). The great animal orchestra: Finding the origins of music in the world’s wild places. Little, Brown and Company.

Polyvagal Theory & Environmental Neuroception
2. Porges, S. W. (2011). The polyvagal theory: Neurophysiological foundations of emotions, attachment, communication, and self-regulation. W. W. Norton & Company.

Global Environmental & Cognitive Economics
3. World Bank. (2021). The economic value of global ecosystem services and natural infrastructure. World Bank Group.

National Conservation Return on Investment (ROI)
4. The Trust for Public Land. (2020). The return on investment of federal and state conservation investments. TPL Research Report.

Architectural, Urban Design, & Historical Policy Frameworks

Landscape Architecture as Public Health
5. Olmsted, F. L. (1870). Public parks and the enlargement of towns. American Social Science Association.

Linguistic & Aesthetic Philosophy
6. Tanizaki, J. (2001). In praise of shadows (T. J. Harper & E. G. Seidensticker, Trans.). Vintage Books. (Original work published 1933).

Acoustic Ecology & Environmental Planning
7. Schafer, R. M. (1977). The tuning of the world: Toward a science of sonic design. Knopf.

Civic Design as Social Engineering
8. Yew, L. K. (2000). From third world to first: The Singapore story: 1965–2000. HarperCollins.

Architectural Proportions and Aesthetics
9. von Goethe, J. W. (1829). Conversations with Eckermann.

Federal & State Legislative Precedents

Wildflower and Highway Beautification Policy
10. Highway Beautification Act of 1965, Pub. L. №89–285, 79 Stat. 1028 (1965).

Environmental Municipal Zoning Revisions
11. State of Nevada & Napa Valley Municipal Code. (2021). Bans on invasive decorative grasses and water-thirsty grass replacement incentive policies. State Environmental Protection Frameworks.

Natural Access: Research demonstrates that exposure to nature increases empathy, generosity, and community connection.

Study on Generosity and Helpfulness: A series of studies published in Personality and Social Psychology Bulletin found that individuals immersed in or exposed to beautiful natural environments acted more generously and demonstrated higher levels of prosocial behavior (kindness and helping others).

12. Zhang, J. W., Piff, P. K., Iyer, R., Koleva, S., & Keltner, D. (2014). An occasion for unselfing: Beautiful nature leads to prosociality. Personality and Social Psychology Bulletin, 40(6), 758–772.

13. Kirsten Weir. Nurtured by nature: Psychological research is advancing our understanding of how time in nature can improve our mental health and sharpen our cognition, Last updated: April 8, 2025

14. Zhuojun Yao 1 and Hanyao Liu. Does Short-Term Exposure to Nature Enhance Prosocial Outcomes? A Systematic Review and Meta-Analysis of the Experimental Evidence, Institute of Higher Education, Dalian University of Technology, Dalian 116024, China, Department of Military Oceanography and Hydrography & Cartography, Dalian Naval Academy, Dalian 116018, China

Awe and Social Connection: Research highlights that the awe inspired by nature reduces focus on the self, encouraging people to be more cooperative and compassionate.

15. Piff, P. K., Dietze, P., Feinberg, M., Stancato, D. M., & Keltner, D. (2015). Awe, the diminished self, and prosocial behavior. Journal of Personality and Social Psychology, 108(6), 883–899.

Natural access: Cognitive Function & Attention. Time spent in nature replenishes our mental bandwidth, leading to dramatic boosts in creative problem-solving and focus.

The 50% Creativity Boost Study: Psychologists tracked hikers before and after a four-day backpacking trip without electronics. They found a 50% increase in performance on a creative problem-solving task after the nature immersion.

16. Atchley, R. A., Strayer, D. L., & Atchley, P. (2012). Creativity in the wild: Improving creative reasoning through immersion in natural settings. PLOS ONE, 7(12), e51474.

17. Minnesota Department of Health. Nature and Mental Health

18. Children & Nature Network. Effects of nature (greenspace) on cognitive functioning in school children and adolescents: a systematic review

19. Kaplan, S. (1995). The restorative benefits of nature: Toward an integrative framework. Journal of Environmental Psychology, 15(3), 169–182.

Psychological Well-Being: The evidence connecting green spaces to lower stress, anxiety, and depression is vast and thoroughly documented.

20. Bahufite, E. The Impact of Nature Exposure on Mental Health and Cognitive Performance: A Systematic Review of Mechanisms, Meta-Analytic Evidence, and Clinical Applications

21. Byers, M. Go Outside! How Nature Helps Our Mental Health

22. Stott, D., et. al. Interactions with Nature, Good for the Mind and Body: A Narrative Review.

The 90-Minute Walk Experiment: A notable Stanford University study showed that participants who walked for 90 minutes through a natural area had decreased neural activity in the subgenual prefrontal cortex — an area of the brain associated with rumination and a high risk for mental illness — compared to those who walked through an urban environment.

23. Bratman, G. N., Hamilton, J. P., Hahn, K. S., Daily, G. C., & Gross, J. J. (2015). Nature experience reduces rumination and subgenual prefrontal cortex activation. Proceedings of the National Academy of Sciences, 112(28), 8567–8572.

The 120-Minute Minimum: A massive study of over 20,000 people found that spending at least 120 minutes a week in nature is the critical threshold strongly associated with good health and high psychological well-being.

24. UK Health Foundation. Nature: How connecting with nature benefits our mental health

25. White, M. P., Alcock, I., Wheeler, B. W., & Depledge, M. H. (2019). Spending at least 120 minutes a week in nature is associated with good health and wellbeing. Scientific Reports, 9(1), 7730.

26. Global CKM Syndrome Landmark Study PubMed 40753430

27. Comprehensive Light-Gut-Liver Axis Review PubMed 41302675 / PMC 12653006

28. National NHANES Light-Activity Alignment Study Xiao et al., Diabetes Care, 2023/2026

About the Author

Hajira Buser is a researcher in luxury ethics and brand strategy with a Master’s in Policy Analysis. She has worked as a global experience architect, focusing on the intersection of organizational excellence and refined aesthetics. She curates beauty by design and advocates for the flourishing from such wellsprings.

Support writers. All our nonprofit’s offerings here.

Click here to subscribe to the IT Chronicles newsletter.

Click for Wordsmith, Mystery Writing, Write Like Stephen King, more

Beauty Matters was originally published in IT Chronicles on Medium, where people are continuing the conversation by highlighting and responding to this story.

The real limits of AI assisted app development from someone who builds with it daily

I want to start with two projects that happened within three months of each other last year, because together they capture the honest reality of vibe coding app development better than any framework I could describe.

The first was a consumer wellness app for a founder who had a clear product vision, no technical background, and a budget that would have covered maybe six weeks of traditional development. We used a combination of Lovable for the initial build, Cursor for the iteration phases, and Claude Code for the backend logic and integrations. The app — mood tracking, habit logging, a simple AI journaling feature, push notifications, a subscription paywall — was in the App Store eleven weeks after the first conversation. The founder launched with twelve hundred dollars in marketing spend, got featured in a niche wellness newsletter, and hit five hundred subscribers in the first month. The product wasn’t perfect. It had rough edges that a traditional development process would have smoothed. But it existed, it worked, and it was generating revenue while a traditionally-built version would still have been in development.

The second was a fintech data platform where a startup team had used vibe coding services to build their MVP, gotten enough traction to raise a seed round, and brought me in to help them scale. What I found when I got into the codebase was a system that had the structural characteristics I’ve come to associate with heavy AI-generated code without sufficient engineering oversight: authentication logic that technically prevented unauthorized access but had a session management vulnerability that would be visible to any developer who looked at it carefully, a database schema that worked for the initial data volume but had indexing choices that would degrade badly at ten times the user count, API error handling that caught obvious exceptions and ignored subtle ones in ways that would produce data integrity issues under specific race conditions, and test coverage that covered the happy path and not much else.

The team had shipped fast. They had achieved genuine traction. And they had accumulated technical debt that was going to cost them significantly more to address than a more careful initial build would have cost, at exactly the moment when the business needed to move fast on new features.

Both of those experiences are real. Both are representative. And the honest accounting of vibe coding app development in 2026 requires holding both of them simultaneously rather than resolving to either the enthusiasm of the first story or the caution of the second.

What Vibe Coding Actually Means in Practice

The term vibe coding was popularized by Andrej Karpathy in early 2025 when he described an approach to software development where the developer describes what they want in natural language, an AI system generates the code, and the developer accepts or rejects the output rather than writing code directly. The “vibes” in vibe coding refer to the intentional looseness of this approach — you’re not specifying precise implementation details, you’re conveying intent and trusting the AI to fill in the technical gaps.

That original framing has expanded in the year and a half since Karpathy’s description, and the term now covers a spectrum of AI-assisted development approaches that range from fairly traditional coding with AI completion assistance to fully AI-driven application generation from a text description. Understanding where on this spectrum a specific tool or workflow sits matters a lot for setting accurate expectations about what vibe coding can produce.

At one end of the spectrum are AI code completion tools embedded in professional IDEs — Cursor, GitHub Copilot, Windsurf, Claude Code. These tools assist experienced developers by suggesting completions, generating implementations of functions from docstrings, explaining unfamiliar code, suggesting fixes for identified bugs, and helping with the boilerplate that consumes developer time without requiring developer judgment. The developer is still writing code, still making architectural decisions, and still reviewing everything the AI generates. The AI is a very capable autocomplete and pair programmer. This is vibe coding in the loose sense — the developer is working with AI assistance — but it’s fundamentally a professional development workflow accelerated by AI.

At the other end of the spectrum are the full application generation tools — Lovable, Bolt, Replit Agent, v0 — where a non-technical user describes an application in plain English and the tool generates a working codebase from that description. The user doesn’t write code, doesn’t necessarily understand the code that’s generated, and interacts with the system through continued natural language instructions when they want changes. This is vibe coding in the strongest sense — the application is vibed into existence by someone who is not a software developer.

In between these extremes is where most practical vibe coding for serious app development lives: experienced developers using AI tools aggressively, leaning on AI generation for the implementation of defined components while maintaining human oversight of architecture, security, and the integration points where AI generation is least reliable.

I spend most of my working time in this middle zone, and my honest view is that it’s the zone where vibe coding produces the most consistently valuable outcomes — faster than traditional development, more reliable than full AI generation without technical oversight, and calibrated to the specific problems that AI assistance helps most with.

The Tools That Matter and What Each Does Well

The vibe coding tool landscape has consolidated faster than most technology categories, and the tools that have proven their value in production app development are worth understanding specifically.

Lovable is the tool I reach for first when working with non-technical founders who need to validate a product concept quickly. It’s a full-stack AI web app builder that produces deployable applications from natural language descriptions. A founder who can clearly articulate what they want their app to do can have a working version in hours. The output is a complete application with a database, API layer, and frontend — not a demo or a prototype, but something that actual users can use.

Lovable’s limitations are worth being precise about. The applications it generates are optimized for typical web application patterns — CRUD operations, user authentication, basic data processing, standard UI components. When the requirements deviate significantly from these patterns — complex state management, real-time multi-user interactions, sophisticated business logic, integrations with external systems that have complex authentication flows — the generated code becomes less reliable and requires more technical intervention to get right.

For product validation work — building something real enough to show to potential users and get genuine feedback — Lovable is genuinely excellent. For production applications that need to scale to thousands of concurrent users or that handle sensitive data with strict security requirements, it’s a starting point rather than a final product.

Cursor is the tool I use for the majority of my own development work, and the one I recommend to development teams who are evaluating how to integrate AI assistance into a professional workflow. It’s an AI-first IDE built on the VS Code foundation, which means the full ecosystem of VS Code extensions, integrations, and workflow tools are available alongside the AI capabilities.

What distinguishes Cursor from simpler code completion tools is the quality and depth of the AI’s understanding of the full codebase. When I’m working on a complex React Native application, Cursor’s AI assistance doesn’t just understand the file I’m working in — it understands the architecture of the whole project, the patterns established in other parts of the codebase, and the dependencies between components. The code suggestions it makes are consistent with the existing codebase rather than generically correct for the language.

The specific Cursor capabilities that I find most valuable in practice are the composer mode — where I can describe a multi-file change I want to make and Cursor executes it across the relevant files — and the chat mode — where I can ask questions about the codebase and get specific, accurate answers without having to manually trace through the code myself.

Claude Code has become part of my workflow specifically for the backend and infrastructure work where the reasoning quality of the underlying model matters more than the IDE-level integration. For designing data models, reasoning about architecture tradeoffs, generating complex SQL migrations, and working through integration patterns for external APIs, Claude Code’s ability to hold complex technical context and reason about it carefully is genuinely useful.

Bolt occupies a similar position to Lovable for full-stack application generation, with somewhat different technical output characteristics. Bolt tends to produce applications with slightly different framework choices and deployment patterns than Lovable, and the tool’s sweet spot is somewhat more technical — users who have some development background but want to accelerate the initial build will find Bolt more flexible than Lovable, while users with no technical background often find Lovable’s guided experience more accessible.

Replit Agent is the tool I recommend most readily for backend development and server-side components, both because of its browser-based environment that eliminates local setup friction and because its agent is particularly good at infrastructure tasks — setting up databases, configuring deployment pipelines, establishing API structures — that are time-consuming without being intellectually demanding for an experienced developer.

Where Vibe Coding Works Genuinely Well

Having spent the past year working with vibe coding tools across a range of projects, I have a reasonably clear picture of the use cases where the approach produces genuine value.

Consumer mobile apps with standard feature sets are the category where I’ve seen the most consistent success. An app that does mood tracking, habit logging, journaling, workout recording, recipe management, expense tracking, or any of the dozens of well-understood consumer app patterns can be built with vibe coding tools at a fraction of the time and cost of traditional development without significant quality sacrifice. The reason is that these patterns are well-represented in the AI training data — the generated code reflects accumulated knowledge of how these features work rather than novel problem solving — and the user-facing quality is high because the design patterns are mature.

MVP validation builds are where vibe coding tools deliver the most disproportionate commercial value. A startup that needs to validate whether their product concept has genuine market demand before committing to a full development investment can use vibe coding to get a working product in front of users in weeks rather than months. The product doesn’t need to be perfect for validation purposes — it needs to be real enough that users’ responses tell you something true about whether they want what you’re building. Vibe coding makes this real-enough product achievable at a cost that most early-stage businesses can afford.

Internal tools and workflow automation are significantly underappreciated as vibe coding use cases. A company that needs a custom dashboard for tracking specific business metrics, a tool for managing a specific internal workflow, or an interface for interacting with data from multiple internal systems can have it built with vibe coding tools in days rather than weeks. The audience for internal tools is forgiving about design polish and tolerant of workflow quirks in ways that consumer-facing apps can’t be. The AI generation quality is sufficient for these use cases without the refinement that consumer applications require.

Prototype and demo builds are an obvious vibe coding use case but worth stating explicitly because the value is high and the alternative is often an expensive traditional development engagement. A sales demo that shows a potential enterprise customer what a custom integration would look like, a prototype that communicates a product vision to investors more concretely than slides can, a proof-of-concept that demonstrates technical feasibility — these builds benefit from the speed of vibe coding without needing the production quality that would require more careful engineering oversight.

Iteration on existing products is a vibe coding use case that experienced developers often undervalue. Once an initial product is established, adding new features and variants using AI assistance is one of the highest-leverage applications of vibe coding tools. The existing codebase provides context that grounds the AI’s generation in established patterns, and the AI assistance compresses the implementation time for new features while the developer’s knowledge of the system catches the cases where generated code doesn’t fit the architecture correctly.

Where Vibe Coding Breaks — The Specific Failure Modes

This is the section I want to spend the most time on because it’s the section that’s least well-represented in the popular coverage of vibe coding and that has the most practical implications for people making decisions about when and how to use these tools.

Authentication and authorization logic is the failure mode category I’ve seen most consistently in AI-generated application code. The pattern is specific: the AI generates authentication flows that technically work — a user can log in, their session is maintained, protected routes redirect to login for unauthenticated users — but that have subtle vulnerabilities in the implementation details. Session token validation that checks for the presence of a token without verifying its integrity. Authorization checks that happen on the frontend without corresponding enforcement on the backend API. Password reset flows that are vulnerable to timing attacks. Role-based access control implementations that check the correct role in some code paths and miss it in others.

None of these vulnerabilities are obvious from the user experience — the app looks and behaves securely. They’re only visible through code review by someone who knows what security vulnerabilities in authentication systems look like. The AI generates the pattern correctly and gets the implementation details wrong in ways that don’t affect normal usage but that create real exposure.

For any application that handles personal data, payment information, health information, or any other sensitive data category, having a security-focused engineer review the authentication and authorization implementation is not optional regardless of how good the vibe coding output looks.

Database schema design under scale is the second consistent failure mode. AI-generated database schemas are typically correct in structure — the right tables, the right foreign key relationships, the right data types — but frequently wrong in the choices that determine performance at scale. Missing indexes on columns that will be used in high-frequency queries. Normalization choices that produce correct behavior but require expensive joins for the queries the application most frequently executes. Schema structures that work for the initial data volume and degrade predictably as data accumulates.

The reason this is particularly insidious is that it doesn’t manifest as a problem until the application is scaling, at exactly the moment when the team has the least capacity to address fundamental infrastructure issues. The technical debt accumulation from schema choices that don’t scale is deferred to the worst possible time.

On the fintech platform project I described at the opening of this article, the specific schema issue was an absence of appropriate indexes on the columns used in the platform’s most frequent query — a transaction history query that ran on every user session. At a few hundred users, the query was fast enough not to notice. At several thousand concurrent users, the unindexed query was causing response time degradation that looked like an infrastructure capacity problem until a database performance analysis revealed the missing index.

Error handling and resilience is the third failure mode category that appears consistently in AI-generated production code. The generated code handles the expected success cases correctly and handles obvious error cases — empty results, invalid inputs, authentication failures — adequately. It frequently fails to handle the subtle error cases that appear in production under real conditions: network timeouts on external API calls with no retry logic, database connection failures with no fallback behavior, race conditions under concurrent access that produce data inconsistency rather than an explicit error, and error responses from third-party services that are structurally valid but semantically indicate a failure the application needs to handle differently.

The consequence of inadequate error handling is not usually application crashes — it’s silent data corruption, inconsistent state, and application behavior that is wrong in ways that are difficult to diagnose after the fact. An e-commerce application that processes a payment successfully but fails to create the corresponding order record because of a database error during the order creation step has silently failed in a way that produces a customer support problem rather than an obvious application error.

Complex business logic with multiple conditions is where AI code generation starts to drift from correct implementation. Simple business rules are generated accurately. Rules with many conditions, exceptions, and interactions between conditions — the kind of logic that defines how a complex pricing engine works, how a matching algorithm handles edge cases, how a workflow approval system handles conditional routing — are generated with varying accuracy that requires careful review against the intended behavior specification.

The specific pattern that appears is that the AI generates logic that is correct for the primary cases described in the prompt and incorrect for edge cases that weren’t explicitly specified. In a traditional development process, a developer who deeply understands the business logic will anticipate these edge cases and handle them. An AI generating from a description will generate for the described cases and leave the edge cases unhandled or handled incorrectly.

Long-term maintainability is a structural concern rather than a specific failure mode, but it’s worth addressing because it affects the total cost of ownership of vibe-coded applications in ways that aren’t apparent at launch. AI-generated codebases frequently have inconsistent naming conventions across files generated at different times, architectural patterns that were chosen by the AI for individual components without consideration of how they interact with other components at scale, and documentation that describes what the code does in the moment rather than why design decisions were made.

A codebase that a single developer understands because they generated it with AI assistance becomes difficult for a second developer to work in because the patterns that make sense to the original developer — because they were there when the AI generated them — aren’t self-evident from the code itself. Onboarding a new developer into a vibe-coded codebase without adequate documentation and refactoring is consistently more time-consuming than onboarding into a carefully structured traditional codebase.

The Production Readiness Checklist That Vibe Coding Generates You Skip

Over the past year I’ve developed a checklist of production readiness reviews that I run on any vibe-coded application before recommending it for production deployment. These are the things that AI generation tools consistently don’t address adequately and that require deliberate human review.

Security review:

• Authentication flow — token generation, validation, storage, and invalidation
• Authorization enforcement — backend API route protection, not just frontend route guarding
• Input validation — SQL injection, XSS, and injection attack surface assessment
• Sensitive data handling — encryption at rest and in transit for personal and financial data
• Dependency vulnerability scan — review of the generated package dependencies for known vulnerabilities

Database review:

• Index coverage analysis — identifying the queries the application executes most frequently and verifying that appropriate indexes exist
• Schema normalization review — identifying denormalization choices that will create data integrity issues under concurrent writes
• Connection pool configuration — ensuring the database connection configuration handles peak concurrent load
• Query performance testing — running the application’s most frequent queries against a realistic data volume

Error handling review:

• External API call resilience — timeout configuration, retry logic, and fallback behavior for all third-party API calls
• Database error handling — behavior under connection failure, query timeout, and transaction rollback scenarios
• Concurrent access handling — behavior under simultaneous requests that modify shared state
• Error logging — ensuring that production errors produce logs that contain enough context to diagnose the issue

Performance review:

• Frontend bundle size — ensuring that the application’s JavaScript bundle hasn’t accumulated unnecessary dependencies
• API response time testing — measuring response times under realistic concurrent load rather than single-user testing
• Memory usage profiling — identifying memory leaks that are invisible under development conditions and appear under sustained load

Operational review:

• Environment variable management — ensuring that API keys, database credentials, and other secrets are not hardcoded in the application
• Deployment pipeline — ensuring that the path from code change to production deployment is defined and doesn’t require manual intervention
• Monitoring and alerting — ensuring that production errors and performance degradation trigger alerts rather than being discovered by users

Running this checklist on a vibe-coded application before production deployment is the difference between the first story I told at the beginning of this article and the second. The wellness app went through a version of this checklist before launch. The fintech platform didn’t.

The Honest Position on Vibe Coding for Serious App Development

I’ve been asked several times over the past year to take a clear position on whether vibe coding is ready for serious app development — whether it’s a legitimate approach or a shortcut that produces the impression of software without the substance.

My honest position is that this question is malformed because it treats vibe coding as a single thing when it’s a spectrum of approaches with genuinely different production readiness profiles.

Full AI generation without technical oversight — using Lovable or Bolt to produce an application without any engineering review of the output — is not ready for production deployment of applications that handle sensitive data, that need to operate reliably under significant user load, or that will be maintained and extended by a team. The AI generation quality is impressive and genuinely useful for validation, but the production readiness gaps are real and consequential.

AI-assisted professional development — experienced developers using Cursor, Claude Code, and similar tools as accelerators within a professional development workflow that includes architectural oversight, code review, security assessment, and testing — is not only ready for serious production app development, it’s the approach I recommend as the default for most development projects. The productivity gains are real and substantial. The production quality is as good as traditional development with fewer AI tools, because the AI assistance is applied under human oversight that catches the cases where generation is incorrect.

The middle ground — using full AI generation tools for the initial build and then having engineering review refine the output toward production quality — is appropriate for some use cases and requires calibration to the specific application. A consumer wellness app that handles no payment data and no health data of clinical significance can be refined from an AI generation starting point at manageable risk. A healthcare data platform that handles PHI or a financial platform that handles payment card data requires a more fundamentally careful approach.

The framing I’ve found most useful is this: vibe coding tools change what’s possible at a given cost and timeline. They don’t change what production-ready software requires. The requirements for production-quality authentication, production-quality database design, production-quality error handling, and production-quality security don’t decrease because the code was generated by AI rather than written by hand. What vibe coding does is give you a faster starting point — and give you more time and budget to address the production requirements properly — if you use the time and budget it saves you to do that work rather than treating the initial generation as the finished product.

What the Best Vibe Coding Looks Like From the Inside

Let me describe what the vibe coding workflow looks like when it’s working well, because the description above of failure modes and production readiness concerns might give the impression that vibe coding is primarily a risk to manage rather than a capability to leverage.

On the wellness app project that I described at the beginning, the workflow that produced the App Store launch in eleven weeks looked like this:

Week one and two were Lovable-driven initial generation. The founder and I worked through the application structure together — she described what she wanted, I translated it into prompts that would produce architecture I could extend, and we iterated through several generations to produce an initial application that covered the core features. At the end of week two we had a working application with user authentication, mood tracking, habit logging, and basic data visualization.

Weeks three through five were Cursor-driven refinement. I took the Lovable-generated codebase into Cursor and worked through the production readiness checklist — addressing the authentication implementation, adding proper error handling to the API calls, refactoring the database queries for performance, and adding the monitoring and logging infrastructure that production requires. The AI assistance in Cursor was valuable here for understanding the generated code quickly and for suggesting the refactoring approaches that addressed the identified issues.

Weeks six through eight were feature addition. With the production foundations in place, adding the AI journaling feature, the subscription paywall, and the push notification system was the work of three weeks because the foundation was solid enough that new features integrated cleanly rather than requiring architectural adjustments.

Weeks nine through eleven were testing, App Store submission, and launch preparation. The testing phase surfaced several issues that the Cursor-assisted refactoring had missed — a state management issue in the mood tracking feature under specific sequences of user actions, a notification scheduling bug that appeared only on Android — and fixing them took the majority of the testing window.

The eleven weeks total was genuinely faster than traditional development for the same scope would have been. The quality was production-appropriate because the production readiness review was part of the workflow rather than an afterthought. And the founder’s involvement throughout the process gave her a product she understood and could iterate on after launch.

That’s what good vibe coding looks like from the inside. It’s not the process of generating an application and shipping it. It’s the process of using AI generation to accelerate the parts of development where AI is reliable, while applying experienced judgment to the parts where it isn’t.

Where Vibe Coding Is Going

The trajectory of vibe coding tools over the past eighteen months has been steep enough that the tools available at the end of 2026 are materially better than those available at the beginning of 2025 in ways that affect the production readiness profile I’ve described.

The specific improvements that matter for production app development:

Security-aware generation has improved. The latest versions of the major vibe coding tools have been refined to generate more secure authentication implementations by default, with better input validation and more appropriate secret handling. The improvements are genuine and measurable — but they haven’t eliminated the gap between generated code and production-grade security implementation.

Architectural consistency has improved. The tools are better at maintaining consistent patterns across a codebase as features are added iteratively, rather than generating each feature in relative isolation. This reduces some of the maintainability concerns I described, though it doesn’t eliminate them.

Test generation has improved. The tools now generate meaningful test coverage more reliably, including edge case coverage that was less common in earlier versions. This is one of the most valuable improvements because tests are both important for production quality and tedious enough that they’re frequently skipped in time-pressured development.

What hasn’t improved substantially is the fundamental capability gap between what AI generation can produce and what production-quality software requires for the hardest problems — complex business logic, sophisticated security requirements, high-scale performance optimization, and careful architectural design for systems that need to evolve over years. These gaps will narrow over time, and the trajectory suggests they’ll narrow significantly. But in 2026, they’re real and they determine where vibe coding works and where it breaks.

The honest use of vibe coding tools is neither evangelism nor dismissal. It’s the specific, calibrated understanding of where the tools produce genuine value and where human engineering judgment remains irreplaceable — and the discipline to apply each appropriately.

Support writers. All our nonprofit’s offerings here.

Click here to subscribe to the IT Chronicles newsletter.

Click for Wordsmith, Mystery Writing, Write Like Stephen King, more

Vibe Coding App Development — What It Is, Where It Works, and Where It Breaks was originally published in IT Chronicles on Medium, where people are continuing the conversation by highlighting and responding to this story.