Solo App Release Board for Nextcloud Deck
as a free board template.
A release board for solo app developers, from idea to the first 48 hours after launch. Checklists cover release notes, a clean-install smoke test, store metadata, and crash reports.
Last verified
Board preview
App Release
Ideas0
Starts empty. Add your own work here.
Planned2
Write release notes
Draft user-facing release notes before submission.
- Lead with what changed for the user
- Name the fixes people actually reported
- Drop anything invisible outside the codebase
- Keep it short enough to read on a phone
Refresh launch page screenshots
Update product screenshots and page copy after the build is ready.
Building1
Freeze scope before you start the build
One more small feature after the freeze is how releases slip by a month.
Testing1
Smoke test install path
Verify cold launch, login, board load, card create, sync replay, and update path.
- Install fresh on a device that never had the app
- Sign in and load a real account
- Create, edit, and delete a card
- Kill the network and confirm the queue replays
- Update over the previous version and check data survives
Ready1
Complete the store submission checklist
Metadata rejections cost a review cycle. Check them before you submit, not after.
- Screenshots match the build you are shipping
- Description and keywords are current
- Privacy answers match what the build does
- Build number is higher than the last one
Shipped1
Watch the first 48 hours
Crash reports and one-star reviews arrive early. Catch them before they set the tone.
- Check crash reports against the new version
- Read new reviews and reply to the fair ones
- Confirm the update path worked for real users
View the portable v1 template JSON
{
"schema": "deckloud-template-v1",
"schemaVersion": 1,
"slug": "solo-app-release-nextcloud-deck",
"locale": "en",
"title": "Solo App Release Board for Nextcloud Deck",
"description": "A release board for independent app builders shipping fixes, App Store updates, marketing pages, and QA.",
"category": "software",
"tags": [
"release",
"app-store",
"qa"
],
"quickCreateStackKey": "ideas",
"compatibility": {
"requiresBoardCreate": true,
"includesAttachments": false,
"includesComments": false
},
"board": {
"title": "App Release",
"color": "3B82F6"
},
"labels": [
{
"key": "bug",
"title": "Bug",
"color": "EF4444"
},
{
"key": "ux",
"title": "UX",
"color": "8B5CF6"
},
{
"key": "app-store",
"title": "App Store",
"color": "0EA5E9"
},
{
"key": "seo",
"title": "SEO",
"color": "10B981"
}
],
"stacks": [
{
"key": "ideas",
"title": "Ideas",
"order": 1
},
{
"key": "planned",
"title": "Planned",
"order": 2
},
{
"key": "building",
"title": "Building",
"order": 3
},
{
"key": "testing",
"title": "Testing",
"order": 4
},
{
"key": "ready",
"title": "Ready",
"order": 5
},
{
"key": "shipped",
"title": "Shipped",
"order": 6
}
],
"cards": [
{
"stack": "planned",
"title": "Write release notes",
"description": "Draft user-facing release notes before submission.\n\n- [ ] Lead with what changed for the user\n- [ ] Name the fixes people actually reported\n- [ ] Drop anything invisible outside the codebase\n- [ ] Keep it short enough to read on a phone",
"labels": [
"app-store"
],
"dueOffsetDays": 7
},
{
"stack": "planned",
"title": "Refresh launch page screenshots",
"description": "Update product screenshots and page copy after the build is ready.",
"labels": [
"seo"
]
},
{
"stack": "building",
"title": "Freeze scope before you start the build",
"description": "One more small feature after the freeze is how releases slip by a month.",
"labels": [
"ux"
]
},
{
"stack": "testing",
"title": "Smoke test install path",
"description": "Verify cold launch, login, board load, card create, sync replay, and update path.\n\n- [ ] Install fresh on a device that never had the app\n- [ ] Sign in and load a real account\n- [ ] Create, edit, and delete a card\n- [ ] Kill the network and confirm the queue replays\n- [ ] Update over the previous version and check data survives",
"labels": [
"bug"
]
},
{
"stack": "ready",
"title": "Complete the store submission checklist",
"description": "Metadata rejections cost a review cycle. Check them before you submit, not after.\n\n- [ ] Screenshots match the build you are shipping\n- [ ] Description and keywords are current\n- [ ] Privacy answers match what the build does\n- [ ] Build number is higher than the last one",
"labels": [
"app-store"
],
"dueOffsetDays": 2
},
{
"stack": "shipped",
"title": "Watch the first 48 hours",
"description": "Crash reports and one-star reviews arrive early. Catch them before they set the tone.\n\n- [ ] Check crash reports against the new version\n- [ ] Read new reviews and reply to the fair ones\n- [ ] Confirm the update path worked for real users",
"labels": [
"bug"
],
"dueOffsetDays": 2
}
]
}
01
When to use this board
For solo developers whose release checklist lives in their head, where one forgotten step costs a full review cycle.
02
How to run this board
Freeze scope when the build starts.
Move only planned cards into Building. New ideas wait in Ideas for the next release.
Smoke test and check the store submission.
Work through the Testing and Ready checklists on a clean install before you submit.
Watch the first 48 hours after Shipped.
Read crash reports and reviews daily. Turn each real problem into a card in Ideas or Planned.
03
What this creates
6 stacks, 4 labels, and 6 starter cards with 16 checklist steps.
04
Standard Deck objects only
The result is an ordinary Deck board that you edit like any other. With a Nextcloud account, Deckloud writes it straight to your server, with no relay.
05
Safe import rules
The file holds no server IDs. Due dates count from the day you create the board, and checklists are Markdown task lists in card descriptions.
FAQ
Practical questions
Does the template include comments or attachments?
No. Comments need an author, and attachments differ between servers and Deck versions, so v1 templates hold text only.
Why is the store submission checklist a separate card?
Metadata rejections are the most common avoidable delay. On its own card, the list gets read instead of assumed.
Does this assume a particular app store?
No. The stacks are generic release states, and the screenshot, metadata, and build number checks fit any store.
Related
Nextcloud Deck templates, free to download and import.
Free Nextcloud Deck board templates with starter cards and checklists: kanban, GTD, releases, bug triage, incidents, hiring, events, study, and more.
OpenBuild a Nextcloud Deck template in your browser.
Build a simple Deckloud template JSON in your browser for a Nextcloud Deck board. No account, no upload, no server credentials.
OpenCreate templates that stay portable.
Create portable Nextcloud Deck board templates with stack keys, label keys, starter cards, and relative due dates.
Open