Skip to content
CyanCode Studio

Services

What we build

Six kinds of work, each delivered complete — with source code, documentation, and deployment support. If you're not sure which category your project falls into, just describe the situation.

01

Enterprise Web Applications

We take internal business systems from requirements through to production and ongoing operation. Our specialty is taking processes scattered across spreadsheets, group chats, and paper forms and turning them into something queryable, reportable, and auditable. We walk the workflow through a prototype before writing code — most rework happens because the process itself wasn't settled, not because the technology fell short.

What you get

  • Requirements research and process mapping
  • High-fidelity prototype and interaction design
  • Full front-end and back-end implementation
  • Deployment, launch, and operator training

Typical stack

  • TypeScript
  • React
  • Next.js
  • Node.js
  • PostgreSQL
  • Redis
02

WeChat Mini Programs

Mini Programs need no download — a QR scan is enough — which makes them the easiest product form to adopt in China. We build commerce, booking, membership, and campaign mini programs, connecting to WeChat Pay, WeCom, and official accounts. We also handle the parts that usually stall a launch: category filing, qualification review, and the appeals process when a submission is rejected.

What you get

  • Mini Program registration and category filing
  • Page design and front-end implementation
  • WeChat Pay and subscription message integration
  • Submission, launch, and ongoing iteration

Typical stack

  • WeChat Native
  • Taro
  • TypeScript
  • CloudBase
  • WeChat Pay API
03

Mobile Apps

For most business scenarios a cross-platform build is more than sufficient, and it brings the cost of two platforms close to the cost of one. When a project involves high-performance graphics, complex Bluetooth work, or deep system integration, we'll assess a native implementation instead. We can also handle app store submission and privacy compliance remediation.

What you get

  • Technology selection and feasibility assessment
  • Cross-platform app development
  • App store submission support
  • Crash monitoring and release iteration

Typical stack

  • React Native
  • Flutter
  • Expo
  • Swift
  • Kotlin
04

System Integration

Most companies already run one or more systems, and the new requirement is usually to make them talk to each other. We build API integrations, data synchronisation, and middle-layer services — including the parts that actually take the time: historical data migration, field mapping conflicts, idempotency, and retry handling.

What you get

  • Audit of existing system interfaces
  • Data mapping and migration plan
  • Integration development and joint testing
  • Sync monitoring and alerting

Typical stack

  • REST
  • GraphQL
  • Message queues
  • ETL
  • WeCom / DingTalk APIs
05

Data Visualization

We turn scattered operational data into charts people can actually read. For live wall displays we focus on the refresh strategy and the degradation path — these screens often run for long stretches on unreliable networks, and stability matters far more than visual flourish.

What you get

  • Metric definitions and alignment
  • Wall display visual design
  • Live data pipeline integration
  • Reporting and export

Typical stack

  • ECharts
  • D3
  • WebSocket
  • ClickHouse
  • Three.js
06

Support & Maintenance

We also take on projects other teams have left behind — code handover, technical debt assessment, and urgent incident response. We start with an assessment of where things stand and a prioritised risk list, then decide together whether to refactor gradually or rebuild. We don't tear things down on day one.

What you get

  • Code and architecture assessment
  • Risk register and remediation plan
  • Defect fixes and feature iteration
  • Performance tuning and security hardening

Typical stack

  • Profiling
  • CI/CD
  • Containerised deployment
  • Logging & monitoring

Ways to work together

How a project is structured depends on how well-defined your requirements are, and whether you have engineers in-house. All three of these are on the table.

Fixed-scope project

We handle everything from requirements through to launch, paid by milestone. The most common arrangement, and the right one when the goal is clear and you need a complete delivery.

Monthly collaboration

We contribute capacity by the month and work alongside your own product or engineering team. Suited to requirements that keep shifting and need sustained iteration.

Technical advisory

Architecture review, technology selection, code review, and debugging — per session or monthly. Advisory only; we don't write the production code.

Let's talk

Got something in mind?Let's talk it through

You don't need the details worked out first. Describe the situation and the rough idea, and we'll tell you whether it's feasible, how long it would take, and what budget range to expect. If it turns out we're not the right fit, that's fine too.