The story behind the product · 3 min read
Aim, physics and visual feedback in one scene.
Shooting is considered alongside physics, camera and cannon selection. Development notes distinguish in-game economy from publishing preparation.
01 / Experience
A game where shots change the scene
Read the target
The cannon and scene indicate where to aim. Camera and trajectory presentation make the choice readable.
Take the shot
CannonController and BallController separate firing and ball behavior. Physics feedback shows the effect.
Choose a look
Local Cannon Shop work includes previews, gold prices, ownership and saved selection. This in-game choice is not the same as a real-money purchase.
02 / Product structure
What sits behind the screen?
These areas support one experience through different responsibilities, keeping the user-facing flow simpler.
Shooting
CannonController and projectile behavior.
Camera & physics
Camera layout and performance management.
Cannon Shop
Preview, gold, ownership and selection.
Flow
Home, world selection and return flow.
For the technically curious: code and architecture
Unity source separates gameplay, physics and camera responsibilities. The Cannon Shop list marks catalog, purchase/selection, persistence and prefab integration as implemented, with icons, balancing and broader tests pending. This newer status is distinguished from the older separation note.
03 / Commercial structure
Revenue paths: what exists and what is preparation?
Unlocking cannons with gold is an in-game economy. Real-money IAP and production ads require separate store/account preparation. The reviewed separation note identifies test ads and pending products; active sales are not asserted.
04 / Publishing & growth
How does the product reach its audience?
Work follows an independent Carnival Blast identity. Dedicated icons, splash and store visuals are preparation items. Unfinished checks are not replaced with a guessed live URL.
05 / Development
From one idea to a product flow.
There is no independent Git history; separation and Cannon Shop documents show progress. They support a story about an isolated shooting flow and later cannon-selection economy, while release verification remains separate.
Based on reviewed local source, available Git messages and product records. Development features may differ from the store version; where available, screenshots come from the existing store presentation; module cards are explanatory diagrams.