Updated
A podcast archive or education community becomes a product when people can save content, follow a learning journey and participate as members. Editors need a reliable publishing workflow while learners need their activity to stay attached to the right account. Treating both as ordinary website pages makes ownership and release decisions harder.
Curiosive's published This is HCD project is recorded in Ireland. Its platform combines a Human-Centered Design podcast archive, free courses, learning journeys and a designer directory. We use that delivered experience to frame projects for US content and community teams, with the project's Irish origin stated explicitly.
Define a complete task: find an episode, open its transcript, save it, join a course or resume progress. Identify which content is public, which actions require an account and who can change the course structure. An editorial publish action and a learner completion event need different owners. Agree those boundaries before choosing the first screens or promising a platform replacement.
The published This is HCD case describes a complete platform remake with episodes and transcripts, free courses, learning journeys and a global designer directory. Members can bookmark, comment, follow others and track course progress. Administration includes moderation of community posts and profiles. A separate worker assembles learning-journey audio from episode segments. Next.js, Sanity, Supabase, TypeScript and Tailwind CSS form the delivered stack.
In the published case, Sanity holds curated episodes, courses and editorial posts; Supabase holds accounts, progress, comments and directory profiles. For a new platform, map who edits each record, how a revised lesson affects saved progress and how moderation changes become visible. Decide how a member corrects a profile and how staff review a reported item. The public content model should support useful destinations and updates without requiring editors to change application code.
For a new learning platform, distinguish a correction to the lesson from a change to the learning requirement. Decide which edits retain a member's completion, which require another review, and what staff see for the previous version. Bring an already completed lesson, a bookmarked episode and a revised course order to discovery. Ask the first release to handle those examples without silently replacing a learner's history. This is an acceptance decision for your platform; the published This is HCD case establishes course progress and editorial ownership, not a particular progress-versioning policy.
For a new membership product, define an access grant's exact end time, time zone and the event that supplies it; cancellation can take effect immediately or at a scheduled boundary. Decide which public archive pages and community spaces remain available after that grant ends. Evaluate other active grants before blocking a shared lesson or space. Keep lesson completion attached to the learner account under an agreed retention policy; access expiry, account deactivation and deleting history are separate decisions. On a return visit, agree what same-account re-enrollment restores and apply the lesson-version policy above. Thinkific documents retained progress for same-account re-enrollment after expiry. Circle documents subscription cancellation separately from account deactivation, with other active paywalls able to preserve overlapping access. These are public product examples, not Curiosive integrations. This is HCD's published case is recorded in Ireland and covers free courses and learner progress; paid-entitlement rules would be new scope.
A public archive refresh can begin with approved episode content and stable destinations while member features stay in their current system. A platform remake needs a separate plan for account references, saved items, course progress and moderation. Before estimating the larger option, inventory the records to retain, identify who can approve a representative migration, and agree how failed or unmatched records are reported. The This is HCD example separates curated content in Sanity from member activity in Supabase. Use that boundary to discuss your own ownership decisions, rather than assuming that copying public pages also moves community history.
The This is HCD example places audio assembly in a separate worker. A new project's media processing needs its own input, completion and failure rules: who requests a job, what a learner sees while it runs and how staff recover from a failed output. Agree a representative media example and the boundary between the web application and processing service. A successful page render alone does not verify that an assembled learning resource is ready to use.
For a new engagement, bring a representative episode or lesson, the member actions around it and the roles that can edit or moderate it. Proposed acceptance examples: an editor can publish approved content without changing member records; a learner can save and resume progress on the agreed course; a member cannot perform moderator actions; and a failed media job leaves a visible status and a staff recovery path. Agree what happens to existing progress when a lesson changes. These are proposed checks for your platform, not retrospective claims about This is HCD's acceptance process.
Curiosive LLC is a US company; engineering is led from Ankara, Türkiye. We agree a written scope, capacity, review windows and release responsibilities before work starts. Monthly AI-accelerated development starts from $2,000. Bring the existing system, the person who owns the workflow and examples of a successful task. A bounded first increment is easier to review than a replacement of every tool at once.
Senior engineers building your product with AI coding agents: web, mobile, SaaS or browser extension, reviewed before anything ships.
AI-accelerated development, billed monthly. We confirm scope, capacity and start date in writing before checkout.
The published portfolio records This is HCD in Ireland. This page offers a relevant learning-platform delivery example for US teams and keeps that country label explicit.
Start with its current content model, URLs, media and editorial ownership. Identify which records can be reused and which need migration; agree how a representative public item and its member actions will work before expanding the scope.
This is HCD's published scope includes free courses and community learning. Paid enrolment, accreditation requirements or a specific LMS integration need their own agreed scope and are not inferred from that example.
Agree the policy before changing course content: which edits preserve completion, which introduce a new requirement, and how staff and members see the previous version. Review completed and partially completed sample records in the first release. This is proposed product guidance, not a claim about This is HCD's historical versioning behavior.
A representative episode or lesson, the course structure, member and moderator roles, examples of saved progress and any media processing tasks. Describe how editors publish today and what must remain working during a release.
Use a fictional learner who completed lesson L-01 through two access grants under an agreed any-active-grant policy. End grant A while B remains active: the lesson still opens and completion remains. At B's agreed expiry time, the lesson becomes unavailable while retained progress and the allowed public/community destinations remain distinct. Re-enroll the same account and check that approved completion restores for the matching lesson edition; another account must not inherit that history. Review account deactivation separately. These are proposed acceptance checks for a new paid-access workflow, not claims about This is HCD's free-course delivery.
One paragraph on what you are building, roughly when you need it, and who it is for. No brief, no form with fifteen fields.
From the engineer who would do the work, not a sales team. If we are not the right fit we say so, and where possible we point you somewhere better.
Scope, price and timeline in writing before anything is committed. You decide with the numbers in front of you.
No long contract to begin, no lock-in to our tooling, and the code is yours from the first commit.
Start a conversationA short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.
Ankara / Türkiye · Working across European and US time zones