Your first phone is a baseline, not a final flagship. Build it to learn the complete design-to-sales route while keeping enough cash for a second attempt. Use the options available in the 2007 garage, choose parts deliberately, set a recorded price, hand the design to your team, select marketing only after checking its cost, then read the critic review and live sales before making another investment.
Prepare the first design
Open the designer and move through every visible category once. The official Experience description names screen size, cameras, corners, buttons, colour, finish, and logo. Do not assume a locked premium finish or wallpaper is necessary; standard options are enough to establish how the product flow works.
Choose a clear product idea such as inexpensive and simple, or balanced within the starter budget. That idea gives each decision a purpose. If you mix the most expensive part with random appearance choices and an untested price, a poor result will not tell you which decision failed.
Write down the available cash before confirming the design. Keep a reserve for any visible development and launch costs plus another phone. The public pages do not state the initial cash, exact component prices, or the current production formula, so use the numbers shown in your server rather than a fixed budget copied from elsewhere.
Work through the design fields
If the current interface exposes other fields, treat them the same way: read the label, inspect the displayed consequence, and record the choice. Do not assign a hidden stat to a cosmetic unless the game shows it.
Set the first price
Price is a testable input. Start from the current displayed cost and leave a reasonable visible margin, but avoid claiming an exact universal percentage. Demand can depend on design, parts, year, marketing, regions, reviews, and update balance. Your goal is to create one measured point on that curve.
Record the exact price before launching. If sales are weak, lower the price on a closely matched follow-up phone or improve one product input while keeping the price stable. If sales are strong, resist a huge jump; increase carefully so you can see where demand changes. The Pricing guide provides a longer test sequence.
Send it to the team
After confirming the design and price, follow the visible command that hands the product to your team. Watch the development state and respond only to controls the game actually shows. Do not invent a worker assignment or skip condition from another tycoon.
If the product appears blocked, read the current status message. It may point to a missing resource, occupied slot, office requirement, or unfinished step. Resolve that named requirement rather than buying unrelated furniture. The optional Extra Design Slot pass officially allows two devices to be built at the same time, which means a normal first run should be planned around one active design unless the current interface shows otherwise.
Choose marketing and launch
The developer confirms that products can launch with a marketing campaign. Before selecting one, read its name, current cost, duration or effect if displayed, and whether the cash reserve still covers another product. The most expensive campaign is not automatically correct for an untested phone.
Once launched, let the sales interface establish a pattern. Read the critic review rather than focusing on a single number. Note what the review praises or criticizes, the direction of live sales, and the resulting cash balance. Those three observations tell you whether the second phone should change product quality, price, campaign, or company capacity.
Build the second phone from evidence
Weak review, weak sales
Keep price close and improve one design or development choice the review points toward.
Good review, weak sales
Test a more accessible price or a different marketing choice before rebuilding the entire product.
Good review, healthy sales
Preserve the design baseline and upgrade one component or test a small price increase.
Cash nearly exhausted
Pause office cosmetics and recruitment, then protect the cheapest viable route to another launch.
One controlled change is the key. You are building a personal comparison inside the current version rather than chasing an unsupported “best phone.” Save both results with the in-game year because research and product expectations can change over time.
First-phone checklist
- Confirm official Experience identity and let the tutorial load.
- Record starting cash and the current in-game year.
- Inspect screen, camera, corner, button, colour, finish, logo, and part options.
- Choose one coherent product idea and preserve a cash reserve.
- Record total displayed cost and the launch price.
- Follow the team development state without buying unrelated upgrades.
- Read marketing cost before choosing a campaign.
- Capture review feedback, live sales direction, and cash after launch.
- Change one major variable for the second phone.
After the second result, continue with the Phone Design guide for deeper design comparisons or the Money guide if cash flow is the immediate constraint.