Project
PROJECT NAME
A floating picnic platform built under $100.
DIY river-ready pontoon built from 55-gallon HDPE barrels and a reinforced frame, designed to carry a full picnic table and multiple passengers.
Why
I wanted a way to turn a cheap, rough river float into a full picnic experience, under strict budget and material constraints.
- Goal: what “success” looked like.
- Constraints: budget, tools, material availability, deadlines.
- Users: who this was built for (you, friends, a client, a class).
What
At a high level, this project is a [device/system] that does X for Y, while satisfying Z constraints.
Key requirements
- Requirement 1 (e.g., must safely support 4 adults and a table).
- Requirement 2 (e.g., must stay under $100 in materials).
- Requirement 3 (e.g., must be buildable with basic shop tools).
Schematic & Plan
The design started with a simple plan that balanced weight distribution, stability, and ease of assembly.
Schematic / plan (placeholder):
Component Selection
Each component was chosen to balance performance, cost, and ease of integration.
Major components
- Component / material 1 — why you picked it over alternatives.
- Component / material 2 — tradeoffs and reasoning.
- Component / material 3 — reliability, availability, or safety considerations.
Bill of Materials (BOM)
The build was kept within budget by reusing materials where possible and choosing cost-effective components.
| # | Item | Specification | Qty | Cost |
|---|---|---|---|---|
| 1 | Example part | Size / rating / part number | x1 | $0.00 |
| 2 | Example part 2 | Details here | x4 | $0.00 |
| Total | $0.00 | |||
How
With the design locked and parts in hand, the build moved through fabrication, assembly, and testing.
Build process
- Step 1: prepare materials / cut stock / initial wiring.
- Step 2: assemble main structure / PCB / frame.
- Step 3: integrate components and perform basic checks.
- Step 4: final assembly, sealing, and safety checks.
Testing & Results
The system was tested in realistic conditions to verify stability, performance, and safety.
- Test scenario 1 and what you observed.
- Test scenario 2: edge cases, overloads, or failure modes.
- Final outcome: did it meet or exceed the original “Why”.
What I'd Do Next
With more time and budget, I would iterate on durability and user experience, and explore how to turn this into a repeatable build.