07 / 07In designConcept 04
Developer Tools / Productivity
SHIPLOG
A release journal for builders
SH
Capture build decisions, screenshots, and milestones as you work—then publish a clean devlog when it matters.
iPhone · iPad · macOS/ Product thesis
Builders want to share progress but documenting work competes with doing the work. Shiplog turns tiny private captures into useful release notes, portfolio stories, and launch content.
01Target user
Indie developers, designers, students, and small product teams building in public or maintaining a portfolio.
02Core problem
The reasoning and progress behind a product vanish across screenshots, commits, notes, and chats, making launches and case studies harder than they should be.
03Differentiator
Private-first capture that understands product milestones and produces editable narratives—not an auto-posting social scheduler.
/ Minimum viable product
Small enough to learn.
Strong enough to keep.
- 01Fast text and screenshot log entries
- 02Milestones, decisions, bugs, and wins
- 03GitHub release and commit linking
- 04Editable weekly devlog draft
- 05Markdown and image export
/ Product system
The loop behind
the interface.
RETENTIONCapture while building → see a weekly progress reel → edit a useful update → publish or archive it → start the next milestone with continuity.
BUSINESS MODELFree single-project journal. Pro adds unlimited projects, GitHub sync, branded export themes, collaboration, and scheduled publishing packs.
APP STORE POSITIONThe build journal that turns product progress into launch-ready stories without forcing you to become a content machine.
/ SwiftUI architecture
Native by design.
A practical starting architecture, intentionally sized for an MVP and ready to evolve after real usage.
- SwiftUI multiplatform scenes↗
- SwiftData local-first entries and attachment metadata↗
- GitHub OAuth and REST client in an isolated integration module↗
- Share Extension for screenshots and links↗
- Background draft generation with user-controlled prompts↗
- CloudKit sync and conflict-aware editing↗
/ Realistic launch path
Evidence before expansion.
Timelines assume a focused solo or very small team.
01Weeks 1–2
Concierge
Manually turn five developers’ raw notes into devlogs to test desired output.
02Weeks 3–7
Capture MVP
Entries, media, milestones, weekly grouping, and Markdown export.
03Weeks 8–12
Integration beta
Add opt-in GitHub linking and test draft usefulness with 30 builders.
04Weeks 13–16
Launch
Ship on iPhone and Mac with three premium export themes.
Projects reaching a second weekly logCaptures per active build weekGenerated drafts substantially retainedExports or shares per milestone