Build WishKit
KINDAreplaces $15/mosaves $180/yrback to the verdict
Before step 1
you will need
- A place to host a small Node service with persistent disk
- A domain or subdomain your shipped app can call
- Xcode if you want the SwiftUI widget compiled and tested
- Basic rate limiting or a proxy in front of the write endpoints
Delivery order
Scaffold the smallest runnable application and document its commands.
done whenThe project starts from a documented command in a clean checkout.
Implement the primary data model and core workflow.
done whenThe main object can be created, read and changed end to end.
Add validation, safe failure states, and persistence.
done whenBad input is refused with a readable message and nothing is left corrupted.
Cover the critical path with automated tests.
done whenThe highest-risk behavior fails the suite when it breaks.
Exercise a clean install from the README and fix every missing step.
done whenA fresh clone reaches the first successful workflow using only the README.
That is the whole plan for WishKit. What it deliberately does not cover is below · check the gaps before you call it a replacement.
- A maintained SDK per platform, so every new client is your code to write and version
- Anti-abuse that someone else already tuned: duplicate votes, spam floods, garbage submissions
- Uptime you did not have to think about for users running an old build of your app
- Email or push notifications when a request they voted for ships
- Duplicate merging, tagging and the other board hygiene features that only matter once you have hundreds of wishes
Need the files? The project pack on the verdict page hands your agent the whole brief · more user research.