Wanderful: Orbital construction pick — Juno: New Origins

Most mobile space games ask you to tap a launch button. Juno: New Origins asks you to decide how much combustion pressure your second-stage engine should run at, and then lets you write the program that fires it.

Built by Jundroo, LLC and formerly titled SimpleRockets 2, Juno is a 3D aerospace sandbox in the broadest sense. The vehicle list covers rockets, planes, rovers, cars and ships, and the physics simulation spans land, sea, air and space. A single save can hold a submarine, a supersonic jet and an interplanetary probe. Dropping “Simple” from the name reads as a statement of intent. This is a construction-and-simulation tool first, wrapped in a game made of a Career Mode, contracts and a technology tree.

That positioning puts it in thin company on phones. Most mobile building games stop at snap-together parts and arcade flight. Juno layers on procedural part shaping, a custom engine designer, a visual programming language called Vizzy, realistic orbital mechanics with burn planning, and Planet Studio, a tool for authoring entire star systems. A community hub at SimpleRockets.com hosts user-uploaded crafts, sandboxes, planets and mods. That extends the game’s lifespan well beyond whatever Jundroo ships itself.

Reception tracks that ambition, with a caveat. The store rating sits at 4.4 out of 5 from 1204 ratings. The simulation survives the move to a touchscreen. The editor’s ergonomics do not survive it intact. Mobile feedback praises the graphics, the sandbox depth and the astronaut and rover play. The complaints concentrate on interface friction, crashes on some devices, and an editor that trails the PC version in polish. The design underneath is sound and well regarded. The question for mobile buyers is how much friction they will accept to reach it.

• Procedural part system: Fuel tanks, wings, cargo bays, fairings and nose cones stretch and reshape freely. Solar panels, landing gear and pistons resize, and everything takes custom paint. The parts bin becomes a set of parameters instead of a fixed catalogue.
• Custom engine designer: Rocket and jet engines can be tuned for combustion pressure, power cycle, gimbal range and fuel type. Exhaust effects react to atmospheric pressure.
• Vizzy visual programming: A drag-and-drop scripting language for telemetry logging, custom touch screens and full mission automation.
• Realistic orbital simulation: Time-warp, map-view burn planning and interplanetary encounters.
• Career Mode: Players run an aerospace company through hand-crafted and procedural contracts. Money and tech points unlock a full technology tree, and interactive tutorials onboard newcomers.
• Planet Studio: Players can build custom planets and whole star systems.
• Astronaut mode: Jetpacks and grappling hooks put a pilot outside the vehicle.
• SimpleRockets.com hub: User-uploaded crafts, sandboxes, planets and mods.

The Build Loop

The loop is a classic engineering cycle: design, launch, fail, revise. The procedural part system is what separates Juno from snap-together builders. A fuel tank is a shape you stretch to the exact volume a mission needs, not a pick from three preset sizes. Wings, fairings and cargo bays reshape the same way.

This matters for two reasons. First, it removes the part-hunting busywork that bloats catalogue-based builders. Second, it ties aesthetics to engineering, because a sleeker nose cone and a properly sized tank are the same decision. The gap between the vehicle in a player’s head and the vehicle on the pad is narrow. The limit becomes the player’s grasp of physics, not the parts list.

The breadth of vehicle types is a design risk the game largely justifies. Rovers, cars and ships share the same physics model as rockets, so the lessons transfer. Center of mass, drag and thrust-to-weight apply whether a craft is rolling, floating or climbing. Astronaut mode, with jetpacks and grappling hooks, gives the space side a human scale. It also gives players a reason to land somewhere and explore rather than simply reach orbit and stop.

Career Mode and Onboarding

Pure sandboxes have an onboarding problem: unlimited freedom with no goals tends to produce a blank stare. Career Mode answers with structure. Players get an aerospace company, contracts, and money and tech points that feed a full technology tree.

The tree does real pacing work by gating complexity. New players meet a manageable slice of the toolkit before the whole thing opens up. Interactive tutorials cover the fundamentals, which matters in a game where the fundamentals include orbital mechanics.

Mixing hand-crafted and procedural contracts is the right call. Hand-crafted missions can teach specific skills in a deliberate order. Procedural ones keep money and progression flowing after the authored content runs out. The usual risk with procedural contracts is repetition, and in a sandbox this open, experienced players will drift toward self-set goals regardless. Career Mode works best as a long tutorial with an economy attached, and we mean that as a compliment.

Engines and Vizzy: Depth for the Obsessive

The custom engine designer is where Juno parts ways with most mobile builders. Tuning combustion pressure, choosing a power cycle, setting gimbal range and selecting a fuel type turns propulsion into a design problem with tradeoffs, not a stat block. Exhaust plumes that respond to atmospheric pressure give that tuning visible feedback. The abstract idea of an engine behaving differently at altitude becomes something a player can watch happen.

Vizzy pushes further still. It is a drag-and-drop language for telemetry logging, custom touch screens and mission automation, and it turns the game into a programming sandbox for anyone who wants one. An automated launch profile becomes a project in its own right, separate from building the rocket that flies it.

Choosing visual, block-based scripting over text is the correct accessibility decision for a touchscreen. Typing code on a phone keyboard would be miserable. The flip side is that block programs sprawl as they grow, and a phone screen is a poor canvas for a large script.

Orbits and Planet Studio

Orbits are simulated realistically, with time-warp and map-view burn planning. Interplanetary encounters push the ceiling well past low orbit. This feature is the line between a space-themed builder and an actual space game.

Map-view planning matters most because it makes orbital mechanics readable. Players plan a burn, see the predicted trajectory, and absorb cause and effect without a textbook. Without that tool, realistic orbits would be punishing. With it, they are learnable.

Planet Studio lets players author their own planets and star systems. For most players it will be a curiosity. For the subset who want custom challenges, such as a heavy-gravity world or a crowded moon system, it is effectively a second game. Paired with the community hub’s shared planets and sandboxes, it gives the long tail of the game somewhere to go.

The Touch Editor Problem

The weak link sits between all that depth and a fingertip. A PC-grade editor depends on precision, several open panels, and fast access to many parameters at once. Mobile feedback cites clunky color pickers that require hidden panels and an editor less polished than the PC version.

Those complaints are predictable from the design. Every parameter the procedural system exposes has to live somewhere on a small screen, and burying controls behind panels is the standard compromise. That compromise taxes exactly the activity the game is built around: fine-tuning a craft. The simulation is the draw; the editor is the toll booth.

Mobile feedback singles out the graphics for praise. The smartest visual decision in the package is the atmosphere-reactive exhaust, which is decorative and diagnostic at once. A plume that changes shape with altitude tells a player something about engine behavior that a number in a panel cannot.

Custom paint gives builders an identity layer, which matters in a game with a large sharing community. The UI that drives it, however, is where the presentation falters. Color pickers tucked behind hidden panels are the clearest example of a desktop-born interface that never fully re-shaped itself for touch.

On performance, the expectation is set by the design. A 3D sandbox simulating realistic physics across land, sea, air and space, with player-built crafts of arbitrary complexity, is about as demanding as mobile workloads get. Part count is effectively a performance dial the player controls. Mobile feedback reports frequent crashes on some devices. In a game built around long construction projects and multi-stage missions, a crash costs more than it would in a quick-session game. Players on older or lower-end hardware should temper expectations.

• Input: iOS and Android both rely on touch for everything, from part placement to Vizzy scripting to flight. The editor’s design shows its PC lineage. Panels and parameter-heavy controls assume a pointer, and on mobile they collapse into hidden menus.
• Parity with PC: The described feature set carries over in full: Career Mode, custom engines, Vizzy, Planet Studio and orbital simulation. The editor experience is the reported gap, described as less polished than on PC.
• Screen size: On tablets, the larger canvas should ease the hidden-panel problem and make big Vizzy scripts manageable. On phones, screen space is the defining limitation of the whole experience.
• Stability: The crash reports apply to “some devices.” Android’s wider hardware spread makes that caveat harder to predict before buying.
• Pricing: A one-time $6.99 purchase. The value case rests on depth and longevity, not on content count.

Few mobile games trust their players this much. Juno: New Origins hands over combustion pressure, power cycles, a programming language, realistic orbits and a planet editor. It then supports that freedom with a Career Mode that teaches through contracts and a technology tree. The procedural part system, the engine designer and Vizzy form a toolkit that most mobile builders do not attempt.

The mobile version pays for that ambition at the interface. A desktop-grade editor squeezed onto touch means hidden panels, fiddly color picking and less polish than on PC. Crash reports on some devices add risk to the long construction this game demands.

We rate it Good. We recommend it to patient builders and aspiring engineers, especially on a tablet. Players on older phones, or anyone with little tolerance for UI friction, should expect to work for the payoff.