GPF Docs
Guide to Feature Tasking
Guide to Feature Tasking
GFP streamlines the process of building features. It emphasizes testability and enforces a clean separation between state and view. The sequence of steps below provides guidance for breaking up a feature into tasks.
| Phase | Resource | Description |
|---|---|---|
| 1. Design SOs | Architect | The major nouns of your domain are good candidates to be ServerObjects. Design out what state each SO is responsible for, the messages they receive, the payloads within those messages, and how handling those messages should impact that SO's state. Your own design document can be laid out with sequence diagrams and tables like our Leaderboard Game Walkthrough. |
| 2. Develop SOs | Sr. Dev | Create unit tests to check whether the SOs implement their design correctly. Run these tests against the simulated backend and build out SOs until all tests pass. See ServerObject Guide. |
| 3. Test SOs | Dev | Once your tests pass locally you will want to deploy your ServerObjects and test them against your unit tests against the real cloud. |
| 4. Hook Up UI | UI Dev | Once your SOs are working correctly, it's time to Hook them up to UI. At this point, the feature can be handed off to UI Developers for completion. Use the supplied ViewBindings and the inspector panel bind to the properties on the SOs you want the UI to reflect.See Hooking Up UI |
| 5. Test Feature | UI Dev | Once your UI is hooked up, you can create several test accounts using the test account UI to help you with play-through tests. Our test account system lets you load old accounts or create new ones when testing locally. It also allows you to enable and disable progress saving, so you can create test accounts that target different parts of your game. |
© 2023 Launch It Labs INC