Create a Food-Delivery App Like DoorDash for the US: Marketplace Ops, Dispatch & Promotions
By Tracy Shelton
November 20, 2025
Table of Contents
The US continues to be one of the most active and lucrative markets for on-demand food delivery. With millions of daily orders in cities, suburbs, and college towns nationwide, consumer demands have transcended convenience. Today, customers crave speed, transparency, personalization, and promotions that seem tailored to their habits. This is a great time for building a Food-Delivery App like DoorDash that can be truly modern, scalable, and data-driven.
Food delivery demand has normalised at levels that are higher than pre-pandemic peaks, even after the surge in deliveries during the pandemic. A lot of people order while working remotely, late at night, while traveling, or just because they want to “know exactly what they’re going to get” from their favorite restaurants — and quickly. DoorDash is winning in the U.S. because it realized early on that food delivery isn’t a logistics business per se — it’s an industry powered by a marketplace model, one that unites merchants, consumers, and couriers all operating within an intricately woven web of interconnected commerce.
The rapid growth of DoorDash in thousands of U.S. cities is a reminder that small towns and suburbs matter just as much as major metros. People in these markets rely on deliveries to eat out, for last-mile convenience, and everyday meals. This leaves massive scale-up potential for entrepreneurs who would like to build hyper-local, mid-city, and regional platforms.” The tech can, if built well, do so at scale across different geographies and with high levels of operational efficiency.
If you choose to develop an app for food delivery like DoorDash, your platform has to control three main things from the very start: manage the Marketplace, automate dispatch, and plan a promotion strategy. Those pillars are the ones that make sure your app never goes beyond being a competitive regional brand or grows into a national player. If you build the right architecture, onboard merchants, shortcut into value-added services, and can promote this by optimizing your routing, then don’t let the US audience stop you.
DoorDash established its ascendancy by building a three-sided marketplace where incentives are aligned for restaurants, drivers, and customers. And rather than relying exclusively on high-volume chains, DoorDash made a priority of local restaurants and smaller retail stores that were left behind by most delivery platforms. That expanded the Marketplace rapidly and made DoorDash the only option in places where competitors were slow to enter.DoorDash’s marketplace model has three experiences at its core. Customers benefit from easy ordering, on-time delivery, and full visibility over the entire process. Merchants are given access to a digital shop front that enables them to drive sales without hiring extra staff. Dashers (delivery partners) have a flexible, multi-shift earning model that uses smart dispatching to optimize their time and earnings.When you create a food-delivery app like DoorDash, you need to mirror this alignment. If any part of the triangle falters — long wait times, low driver pay , or unpredictable restaurant availability — the whole chain feels the pain. A healthy marketplace is balanced by providing each player the right set of tools to operate effectively.
DoorDash thrives on knowing what is happening at a neighborhood level. It splits up each area into delivery zones and draws on historical data, traffic patterns, restaurant concentration, and Dasher availability to maximize the efficiency of its operations. Smaller zones result in quicker delivery times, better driver earnings, and happier restaurant customers. It is this granularity that enables DoorDash to scale a business from one city to thousands of localised micro-markets.
For building a DoorDash-like food delivery app, also add support for micro-zoning, localised pricing, regional promotions, and smart sourcing of resources. The more you customise the experience on a city, suburb, or block level, the more competitive your Marketplace becomes.
The secret to DoorDash’s success was that it gave all three marketplace participants equal treatment. Customers get real-time tracking, personalised recommendations, and reliable service. Merchants receive order management tools, menu syncing, promotions, and analytics. Dashers receive smart dispatch, peak-pay promotions, and route-optimized navigation.
Achieving balance in this triad is the secret to growing an effective market. If you want to make a food-delivery app like DoorDash, your success will hinge on creating experiences of similar strength for all three groups. A business that only cares about customers is a failure. A marketplace that doesn’t take into account the merchant or delivery partner will not scale. The win is in the ecosystem, not the app by itself.
In the case of the US food delivery market, that includes engineering a platform to work at scale and process high order volume while also being able to compete in local micro markets. By opting for the development of a food delivery app like DoorDash, you’re not simply creating an ordering app—you’re establishing the full marketplace infrastructure tailored for restaurants, customers, and drivers.
Core architecture will start with the separation of concerns. You require three divergent layers: the customer interface, the restaurant dashboard, and the delivery partner flow. All that has to happen in real time, and behind the scenes relies on a sturdy backend coordinating orders, dispatches, payments, menus, promotions, fees, and geographical zones. This would be your backend, being your nerve center; everything you do is being codified into structured data to help automate mass activities.
Syncing your menu is another basic need. Prices at restaurants are constantly changing, sometimes even on a daily basis. Your system must be able to pick up when the menus change and not display items that are unavailable. It also needs to handle multi-location restaurants, each with different hours, kitchen load, and prep time. The more precise your menu and hours listing is, the fewer cancellations and delays you’ll receive.
Routing is the brain of the platform. What you need is a dispatch engine that knows city geography, traffic patterns, lead time, and driver supply. When implementing a food-delivery app like DoorDash, your routing algorithm also needs to take into consideration (on the fly) when to give an order and give you an XD amount of visit time that will minimize multiple orders, batch it with another order if necessary, or plant it downstream, or even delay dispatching in terms of kitchen timing. This balance of kitchen time and driver arrival represents your operational efficiency.
DoorDash isn’t running cities — it’s running zones. Each zone operates like its own mini-market, with its driver availability, saturation of restaurants, peak hours, prep times, and service levels. Your system needs to mimic this micro-market methodology. Each zone requires a separate delivery radius, dispatch rules, promotions, surge incentives, and operational insights.
A robust zone structure guarantees consistency in delivery times and the demand-supply ratio. It also makes it easy for the platform to scale from one neighbourhood to a whole city. When creating a food-delivery app similar to DoorDash, a multi-zone design should be the core of your scaling approach.
Menu syncing means that customers only see what is available, with the price always matching. Restaurants are also prone to stockouts or unanticipated rushes. Your system should be able to dynamically remove unavailable items or change your menus when you receive real-time signals in the merchant dashboard.
Syncing inventory would also help eliminate cancelled orders, which ruin the credibility and cost reimbursement. You need to monitor the status of items, the length of time on prep, when you’re in a rush in the kitchen, and are going to sell out and be forced to temporarily close. These flexible changes cut friction and allow restaurants to keep running smoothly.
A food delivery marketplace works when there is a frictionless transaction between all three sides of the ecosystem: consumers, who order food; Merchants, who make it… as well as Drivers. Features you need to build a food-delivery app like DoorDash. When building an on-demand delivery app like DoorDash, your features should encourage smooth transactions for all user groups.
If you want the end-to-end experience for your customers available at your fingertips,ʼs product must have quick browsing, personalised recommendations, fast checkout, accurate ETAs, and real-time tracking. Restaurants must be armed with intuitive tools for managing incoming offers, updating menus, managing prep queues, and tracking payouts. For delivery partners to be successful, they need reliable navigation, visibility into what jobs are available, financial reporting, and clear instructions to help eliminate ambiguity.
The customer interface must be fast and easy. From restaurant discovery to dish selection to confirming payment, every step needs to be friction-free. Transparent delivery time estimates help to gain trust. Real-time tracking creates transparency. Problems are resolved without much effort with the help of communication utilities. Personalised recommendations enhance retention.
These are the things that determine satisfaction with the service and strong repeat usage.
Your Marketplace’s merchants are its economic lifeblood. Their backend should make order, menu, store hours, promotions, and discounts, as well as preparation times, simple to manage, and also include payout analytics. Restaurants need the ability to pause orders at peak times or make an item available instantly.
This precision minimizes cancellation and enhances workflow.
Drivers need clarity. The app they use has to display minimum wait times until a driver can pick it up, instructions for delivery and gate codes, the disaggregated payout of earnings, and surge/peak bonuses. An optimal driver experience = more supply is available, which directly impacts the wait time for the customer.
You see, with a food-delivery app like DoorDash, you also treat drivers as foundational stakeholders in your business for the long haul.
In the United States, operational excellence is required in order to win in the Marketplace. Each city is unique, and so is each neighborhood in terms of demand patterns, preferred cuisines, peak hours, and driver supply. When you create a food-delivery app like DoorDash, your operational model should account for these nuances to enable high fulfillment rates, fast deliveries , and strong merchant retention.
Restaurants are really the backbone of your Marketplace. Some of those chains will be large operators with lots of outlets; some will be small local kitchens working with reduced staff. Your platform must support both. Restaurant onboarding should be simple, with menu uploading, prep time setting, promotions management, and a sheet for tracking payouts or deposits. There’s also the need to confirm operating hours, kitchen load, and preparation time, as inaccurate restaurant data leads to customer dissatisfaction.
Delivery zones are equally important. Metropolitan areas like New York, Chicago, or Los Angeles need micro-zones to control traffic and density. Suburbs require bigger delivery radii as restaurants are spaced out more. Your system will need to continuously track order density, driver availability , and restaurant distance to automatically readjust these zones as demand rises and falls. It’s this dynamic zoning approach that is the secret sauce behind DoorDash’s reliability.
The more restaurants, the faster your Marketplace grows. The user journey must be very easy to understand, transparent, and reinforced by a clear commission model. Restaurants want to know what they pay, what they earn, and how much visibility or promotions contribute to their monthly revenue. Upon signing up, merchants ought to be getting digital contracts, setup instructions, and onboarding support.
Marketplace fees and delivery fulfillment fees are accompanied by optional promotions on the platforms. Local laws in the US also oblige transparency on fees. Things get tricky when you create a delivery app like DoorDash, because your commission engine will include multi-tier pricing as well as city-specific caps and use cases for promotional cost-sharing between restaurant and platform.
Delivery areas indicate the time to fill and the cost of a delivery. Smaller zones mean faster travel times, higher driver wages, and happier customers. Large areas mean more variety among merchants, but slower fulfillment. Here, your system needs to find the right balance between geography and population density.
Service-level agreements (SLAs) ensure quality. An SLA could include expected delivery time, acceptable delay ranges, prep time windows, and driver arrival buffers. These SLAs assist restaurants in planning kitchen flows and help dispatch systems to effectively assign drivers. When you create a food-delivery app like DoorDash, SLA enforcement helps maintain operational stability and minimize refunds or cancellations.
Dispatch is the highest order and most complex part of a food delivery system. It’s what decides how quickly your platform feels, how much drivers make, and how satisfied customers are. As you develop a food delivery app like DoorDash, your dispatch engine will evolve to be the nucleus of your marketplace operations.
Dispatch requires constant decision-making. It needs to know when a driver should be dispatched, which driver is the best fit, when to wait for kitchen prep, when to batch orders, and how we can minimize total delivery time. These calls need to be made not by humans, but by algorithms because marketplaces are high-volume.
There are traffic conditions to consider, road closures, weather, distance, restaurants’ prep times, and where the customer is. The system has to determine the most efficient route in seconds and update the driver’s app in real time. As a result, accurate routing helps cut delivery times and boosts drivers’ take-home pay, which in turn bolsters the supply of drivers.
Batching is equally important. And drivers can deliver multiple orders from the same restaurant or restaurants in close proximity all at once. Batching is a great booster of efficiencies, though it requires careful timing to ensure that orders do not go cold. To maximize profitability, the dispatch engine needs to be aware of kitchen speed, customers’ distance, and driver proximity in order to craft batches for success.
With auto-assignment, a driver is sent to each order. The engine has to consider such factors as distance to restaurant, distance to customer, driver speed, behavior of traffic, drivers’ preferences for earnings , and available batches. A well-executed algorithm cuts wait time for drivers and improves customer ETAs. As you develop a food-delivery app like DoorDash, powerful auto-assignment is also necessary to synchronize the supply and demand without human allocation.
Batching increases profitability. If several customers are ordering from the same restaurant, that system can pair their orders with one driver. The ideal drop-off sequence is calculated to optimize every customer’s food delivery time.
This multi-order batching system is not only intelligent, but it also needs to be professionally refined and maintained. It is one of the best features of a professional delivery platform — and one of the hardest to create.
Promotions are the rocket fuel behind growth in the US food delivery market. Shoppers immediately jump from platform to platform based on discounts, free delivery, loyalty rewards, and subscriptions. If you will also build a food-delivery app like DoorDash, then you obviously require a strong sort of promotion engine that supports experimentation, segmented targeting, and joint campaigns with restaurants.
Promotions can’t just be about lowering prices. They are about shaping behaviour. Tactical offers promote first orders, convert infrequent users into weekly customers, and re-engage dormant accounts. A promotion engine should enable you to offer city-specific offers, cuisine-specific campaigns, time-sensitive deals, and personalized incentives based on ordering history. The more data you accumulate, the better your targeting gets.
Retention is where the money is. It’s costly to win a customer in today’s competitive world. Keeping them there with consistently good quality, reliable ETAs, and smart promotions is how a marketplace lives. If you build an app for food delivery like DoorDash, retention should be considered a product feature, not just something marketing does.
In the United States, promotions are typically financed by one of three entities: the restaurant, the platform, or a combination of both. Restaurant-funded discounts enable merchants to nudge up order volume in off-peak hours or for new menu items. Offered by the platform, platform-funded offers generate user acquisition and loyalty/reactivation across many restaurants at the same time.
Your system of promotion has to make it clear just who is going to pay for what. Restaurants need to be able to opt in/out of a campaign, cap (set a limit) their contribution, and track results on their dashboard. The platform must have clear exposure to campaign performance by city, cuisine, and segmented users. By creating an app for food delivery like DoorDash, this joint responsibility in promoting the restaurants helps to keep them engaged and places less of a strain on your own marketing budget.
Loyalty programs and subscriptions turn occasional users into high-frequency customers. Repeat orders, larger cart sizes, and trying new restaurants are rewarded with the points-based loyalty system. Referral programs transform happy customers into advocates by incentivizing them to refer friends and family.
And then there are subscription models, like DashPass, that offer free or discounted delivery for a monthly charge. This changes user psychology. They instead make it less likely your subscribers will open your app first because they feel as if they are “wasting” their benefits by ordering elsewhere. If you build a DoorDash-like food delivery app but don’t see a long-term vision for loyalty and subscription, then the chances of losing users to your competitors with better retention levers are high.
Beneath the smooth veneer of a delivery experience is a complicated stack of technology. You want mobile apps, web portals, backend services, dispatch algorithms, notification systems, analytics pipelines, and monitoring tools all gliding together in real time. When you’re building a food-delivery app like DoorDash, your technology has to be dependable and fast and built for constant testing.
On the frontend tier, customers browse and order food as well as track orders, pay for orders, and get customer support. Responsive and fine-tuned even under heavy load. Error states, time-outs, and edge cases all need to be handled gracefully because any payment-related friction at checkout directly impacts revenue.
The backend handles business logic like what is the availability of that restaurant, calculation of pricing, commission logic behind the advertised offers and other promos, zone rules, what will be dispatched next, SLA tracking, etc. It collects live signals from every order, driver, and restaurant before pipelining data into the dispatch engine, the analytics systems, and dashboards. The better architected your backend, the more scalable and easily extensible it is.
Frontend should be modular, reusable components for apps and web. It also helps in creating consistent interfaces as well as saving time when you create new flows , like subscription signup or group ordering. Performance is key, in particular for search, menu scanning, and cart updates.
It has to have the backend structure around core domains like users, restaurants, drivers, orders, payments, and zones. Service-driven or micro-services architecture is common, so that when you update one component, you don’t risk breaking everything else. When you’re building an app like DoorDash for Food Delivery, having this separation allows you to iterate on dispatch logic, fees, or promotions without rewriting the whole platform.
You assume real-time visibility at this point. It wants them not just to see when an order is accepted at a restaurant, but also when food is being made, the driver heading for pickup, and delivery nearing. They require instant directions and an agile plan. Restaurants require the most current order queue and exact pickup times.
In order to enable that, your “whole stack” will need to allow event-driven communication between all components. Update in locations, change in status, and ETA re-calculation are to be done then and there. The notification layer should dispatch push notifications, SMS, and in-app messages without hiccups. When you create an app like DoorDash for food ordering and delivery, real-time tracking is not some superficial functionality — it is a trust-building tool that helps maintain the balance between all engaged.
Building a US-ready market doesn’t end at coding an app. It means getting product, engineering, operations, legal, marketing, and support aligned around a common roadmap. Organized development allows you to escape the chaos and lets you build your platform with scalability and reliability in mind from the beginning. Developing a food-delivery app like DoorDash. When developing a food-delivery app, such as DoorDash, you should break down the process into stages that will also be influenced by data.
It typically begins with discovery. You set your target cities, restaurant mix, commission strategy, delivery model, and unit economics. You process the rides of customers, restaurants, and drivers in great detail, including any edge cases (missing items, late drivers, and kitchen overload). This stage serves the purpose of figuring out what is needed for launch and what could be postponed.
Then you go into design and architecture. UX teams design flows for ordering, driver onboarding, restaurant setup, promotions, and support. There are backend architects, database schemas, dispatch rules, and notification logic to design for engineers. The aim here is to generate a blueprint that provides for a good user experience without compromising on operational constraints.
Discovery is where you choose what kind of Marketplace you want to be. Will you concentrate on a type of cuisine, a region, small towns, college campuses, or corporate districts? Do you support scheduled deliveries, takeaway, grocery add-ons, or only instant orders? It’s important to know these options when you create a food delivery app like DoorDash, as they shape dispatch rules, UI design, and other factors related to pricing and go-to-market.
This would also be a time to learn about U.S. laws on gig work, delivery areas, food safety communication, and fee transparency. There are legal requirements that must be built into your product design and contract with the restaurants and drivers.
When the plan is set, full development becomes possible. Parallel development of customer, restaurant, and driver apps along with backend and admin dashboards. Payments, maps, geocoding, SMS, email, and analytics integrations are set up. At an implementation level, request engines, promotion subsystems, and commission logic are configured with endpoints to live or sandbox services.
Testing is so important right now. You need to verify order flows, time calculations, geo-fencing, driver payouts, refunds, promo application, and menu syncing. When you build a food-delivery app like DoorDash, you’re building a system in which many small errors can result in big real-world headaches if left to fester.
They develop, then you’re in pilot mode. 1. You launch in a few neighbourhoods, with a small number of restaurants and drivers. This is the pilot that lets you experience the joy of real-world complexity: traffic delays, kitchen bottlenecks, mispicks, address confusion, and promotion abuse. You iterate on the product, operations, and anything else based on actual data instead of surmises.
Once the pilot is successful, you continue launching city by city with an open and repeatable rollout playbook. Each new city comes with its own zone definitions, onboarding pipeline for restaurant partners, strategy to recruit drivers, and calendar for promotions. It’s this controlled scaling pattern that helps you build a food-delivery app like DoorDash, which can grow sustainably and not collapse under its weight.
How much does it cost to develop a delivery platform in the us? The US price. Let’s imagine that your landing region is going to be the same area where you are launching, paired with feature complexity, quantity of modules, dispatch logic, and marketplace size. With a food delivery app like DoorDash, you aren’t just developing a customer app — because when building a multi-app system, it typically includes tools for merchants too, along with driver workflows, real-time routing, and an admin command center. Costs can also fluctuate with the ambition of the project, whether it’s setting up a regional platform for one or two cities, or striking out to build a nationwide program. Dispatch engines, batching logic, menu-sync automation, subscription systems, loyalty features — it all takes real engineering depth. In addition to development, ongoing operational cost drivers include cloud hosting, customer support, restaurant onboarding, driver background checks, map usage, and promotion funding.
The more cities you expand to, the more you require automation, and hence, upfront development costs would pump up exponentially, but long-term operational overhead will cut down drastically. A well-designed system enables your platform to scale without needing to bring in armies. This longevity of efficiency is why it is so important to invest properly from the start when you create a food delivery app like DoorDash.
The customer app, restaurant dashboard, driver app, admin platform, dispatch engine, promotion system, and payments integration are just some of the costs feeding into those development fees, along with routing logic (et al), menu-sync engine, and subscription layer, to name a few, and not forgetting all those analytics. The more complex ones are the dispatch, routing, batching, and constant improvement of customer retention engines, which can take up significant amounts of resources when one is looking to automate them intelligently.
A platform designed for US geography means advanced zone logic, adjustable fee structures, and compliance-oriented restaurant contracts. This adds to the cost, but is a requirement for long-term stability.
Once launched. Your OPEX would be cloud hosting, email and sms notifications bill, map aPI calls charges, customer care executives, merchant onboarding crew, and driver validation process, along with promotions budget. These ongoing costs are necessary to maintain the safety, quality, and compliance that customers expect.
Cloud costs are based on the number of orders, real-time updates, push notifications, routing calculations, and driver location pings. Special offers and reader perks turn into ongoing investments, too. Planning for long-term operating costs is as critical as estimating the actual development budget when you build a food delivery app like DoorDash.
The U.S. market for food delivery is a potential blockbuster, but it’s both big and fragmented, so growth needs to be done strategically. The key to a successful launch is attempting city-by-city operations, not a nationwide presence from day one. If you are going to build a food-delivery app like DoorDash, a phased rollout gives you the best chances to gain strong initial retention and reach profitability early on.
Begin with a specific area, one that has a mix of dense neighbourhoods, strong local restaurants, and manageable delivery distances. This means you will be able to develop brand recognition, optimise the timing of the dispatch, test the drive time zones, and analyse drivers’ habits. Little cities, university towns, and suburban conglomerations often even outperform big metros for early-stage launches because of lower competition and closer-knit local behaviour.
Once you have your first region stabilised, you clone your model in similar cities. Your playbook for rollout should cover everything from the restaurant onboarding process to patterns of driver recruitment, local promotions, partnerships, and fee structures. Each city should have unique operating rules for zones, ETAs, peak times, and surge incentives. This is the localisation that helps this platform to feel trustworthy, as opposed to generic.
Tier 1 city demand is high and competitive , so it’s better for the later stage. I am looking at Tier 2 cities/Outside and Suburbs – It is easier to get traction faster with cheaper marketing. College towns and smaller, mid-sized cities tend to offer the best ROI in the first few years.
Any rollout has to be meticulously choreographed: zone creation, restaurant signup, driver supply activation, promotional campaign, and local partnerships. This uniformity guarantees predictable performance and linear scalability.
Partnerships accelerate trust and adoption. Local restaurants offer loyal customers and ghost kitchens the scale of order volume.” Brand partnerships — think national chains — lend credibility and predictable demand. Early partnerships matter a lot when you first start building an app like DoorDash; they will lower your CAC and boost retention in the long term.
Idea2App is an expert in developing robust, scalable, and user-friendly on-demand applications to cater to the US market. Hire Idea2App to develop an app similar to DoorDash: You get a tech partner who understands how the Marketplace works, dispatch logic, promotions, routing algorithms , and retention strategy. Idea2app as a leading food delivery app development company is here to help you.
Each module is constructed by a team with deep technical skills. Customer apps are quick, user-friendly, and optimized for conversion. Merchant dashboards include menu syncing, order queues, payouts, and business insights. Comprehensive navigation, batching your deliveries, and transparent earnings help you work smarter — not harder. On the backend, a strong Admin panel tracks live operations, flags exceptions, and automates manual processes.
Idea2App also develops smart dispatch systems that improve routing and reduce delivery time, while boosting driver income. With our promotion engine, you can even run personalised offers in a city/restaurant, funded discounts, or subscription benefits, just like the big US delivery platforms.
Whether you aim to start in a single city or build the business across numerous states, Idea2App serves as a technology and platform engine that shapes both sustainable marketplace growth and profit. Because with us, you can take your delivery concept from an idea to a lightning-fast US food delivery platform.
The US food delivery market is being served by an increasing number of platforms, which represent a huge opportunity for entrepreneurs who would like to challenge the leading players. With a powerful technology backend, smart operations, and successful promotions, you can build an Uber Eats clone that differentiates itself by being more reliable, local, and customer-focused.
Succeeding involves striking a balance between market dynamics, providing fast ETAs, promoting restaurants, drivers’ earnings, and retention. Dispatch intelligence, customer loyalty programs, restaurant partners, and regional branding become defining factors. A platform that nails these pillars can build a lasting competitive advantage.
With Idea2App as your tech partner, you get a team that understands US/UK market dynamics and the operational complexity and technical architecture necessary to scale. This combo gets you off to a great start and gives you the propellant to go long!
A full-function platform with customer, merchant, and driver modules usually takes from 12–20 weeks for an MVP (Minimum Viable Product), and a fully scalable version takes about 6–9 months.
Yes. In fact, the easiest way to grow predictably is by starting with a single city or region.
We leverage event-driven location updates, routing algorithms, and dynamic ETAs for accurate results for customers, drivers, and restaurants.
Yes. Subscription packages, restaurant-sponsored deals, referral rewards, and custom promotions can all be added.
It has a dedicated dashboard for merchants to update menus, stock levels, prep times, and order capacity in real time.
Absolutely. The technology is built to accommodate multi-brand cloud kitchens with differentiated menus and operational profiles.
