把日常软件
做得更有分寸
Software made
with restraint.

本网站 dctyym.cn 由广州华任通网络科技有限公司运营。我们从事移动应用与软件服务,把 App 开发、接口设计、上线运维看成一条完整链路,也持续关注云原生架构与 AI 接入的可用边界。 This website, dctyym.cn, is operated by Guangzhou Huarentong Network Technology Co., Ltd. We build mobile apps and software services — from client and API design to operations, with a clear eye on cloud-native architecture and practical AI.

iOS 原生体验优先Native-first
API 服务端协同Backend in tandem
AI 按需接入Added with care

公司信息Company

dctyym.cn 是广州华任通网络科技有限公司的官方网站 dctyym.cn is the official website of Guangzhou Huarentong Network Technology Co., Ltd.

本站由广州华任通网络科技有限公司独立运营,简称:华任通。用于发布公司介绍、软件与 App 产品、隐私政策、服务条款,以及 App Store 开发者支持入口。网站域名、企业邮箱与 ICP 备案主体均为同一家公司,办公地址与联系电话如下。 This site is operated solely by Guangzhou Huarentong Network Technology Co., Ltd. It publishes company information, software and app products, privacy policy, terms of use, and App Store developer support. The domain, company email, and ICP filing belong to the same legal entity. Office address and phone are listed below.

公司全称Legal name
广州华任通网络科技有限公司 Guangzhou Huarentong Network Technology Co., Ltd.
品牌名称Trade name
华任通 Huarentong
官方网站Official website
企业邮箱Company email
联系电话Phone
办公地址Office address
经营范围Business
移动应用开发、软件服务、接口与运维、App Store 产品支持 Mobile app development, software services, APIs and operations, App Store product support
ICP 备案ICP filing
粤ICP备2026152669号-1

关于我们About

小团队,把每件事做完整 A small team that finishes the work.

广州华任通网络科技有限公司是一家软件服务公司。需求、架构、发版、监控、客服和合规,都算交付的一部分。我们不追求堆功能,而把产品做成可长期运行的服务。 Guangzhou Huarentong Network Technology Co., Ltd. is a software services company. Requirements, architecture, release, monitoring, support, and compliance are part of delivery. We treat a product as a service that must keep running.

为什么做应用Why we build

很多好用的 App 被淹没在商店里。体验官希望把「发现、试用、反馈」连成一条清楚的路径:你按自己的节奏参与,规则事先讲明,过程可以回看。 Useful apps are easy to miss. 体验官 connects discovery, trial, and feedback into one readable path: join at your own pace, with rules stated up front and progress you can check.

「认真体验,值得被看见」 “Careful use deserves to be seen.”

广州华任通网络科技有限公司 Guangzhou Huarentong Network Technology Co., Ltd.

软件服务Software services

把应用做成可运行的服务 Ship apps as running services.

软件服务行业常见的交付不是一份安装包,而是持续可用的能力:客户端、接口、数据、发版和响应。华任通围绕移动应用,把开发、上线和运维放在同一条链路上。 In software services, delivery is rarely just a binary. It is a living system: client, API, data, release, and response. We keep mobile development, launch, and operations on one path.

App

移动应用开发Mobile apps

覆盖 iOS / Android 客户端:页面、账号、推送、深链、权限说明与商店上架。原生优先,保证系统能力用得完整;双端重复度高时,再评估跨端框架。 iOS and Android clients: screens, accounts, push, deep links, permission copy, and store listing. Native first, so system APIs stay complete; cross-platform only when duplication is high.

API

后端与接口Backend & APIs

用 REST 或 gRPC 提供稳定契约,配合鉴权、限流、对象存储和消息队列。业务规则尽量放在服务端,客户端负责体验,避免把核心逻辑写死在 App 里。 Stable REST or gRPC contracts, with auth, rate limits, object storage, and queues. Keep domain rules on the server; the app owns experience, not irreplaceable business logic.

Ops

运维、发版与合规Ops, release, compliance

CI/CD、崩溃与日志、灰度发布、隐私协议和备案,都是软件服务的日常。上线只是开始,可观测性和客服入口决定服务能不能长期用。 CI/CD, crash logs, staged rollout, privacy text, and filings are daily work. Launch is the start; observability and a reachable support path keep the service usable.

架构Architecture

常用开发技术架构 Familiar structures, plus what we use now.

架构是给变化留空间。客户端先把界面和业务分开;服务端按规模选择单体、拆分或按事件协作。没有万能图纸,只有适不适合当前产品。 Architecture is room to change. Clients separate UI from domain; servers stay a modular monolith until scale, team, or traffic asks for more. No universal diagram — only fit.

客户端常见分层Client layering

MVC

Model–View–Controller。数据、界面、控制流程分开,适合页面不多、逻辑直接的模块。 Model–View–Controller. Splits data, view, and flow. Fits modest screens with direct logic.

MVVM

Model–View–ViewModel。用可观察状态驱动界面,减少「巨型控制器」,在 SwiftUI / 声明式 UI 里更常见。 Model–View–ViewModel. Observable state drives the UI, which keeps view controllers small — common with SwiftUI and other declarative UI.

Clean / Hexagonal

业务规则放在内核,UI、数据库、网络当作可替换插件。测试和换实现时,不必重写整套页面。 Domain rules sit in the core; UI, storage, and network are replaceable adapters. Tests and swaps do not rewrite every screen.

服务端与现行架构Server-side and current practice

分层单体Modular monolith

一个可部署单元,内部按模块切开。业务未拆清之前,先保证边界清楚,比过早微服务更稳。 One deployable unit, cut into modules. Clear boundaries first; split services only when the seams are real.

微服务Microservices

按业务边界独立部署和扩容。适合多团队并行,但会换来分布式事务、链路追踪和运维成本。 Independently deployed slices. Good for parallel teams; you pay with distributed data, tracing, and ops.

BFF

Backend for Frontend。为 App 单独做一层聚合接口,少打几次网,字段按端来裁。 Backend for Frontend. A client-shaped API that aggregates and trims fields so the app makes fewer round trips.

事件驱动Event-driven

审核、通知、结算等异步步骤用消息传递。主流程先返回,后续靠队列推进,避免把用户卡在等待上。 Review, notify, and settle over messages. The main flow returns first; queues finish the rest without blocking the user.

Serverless

云函数按调用扩缩,适合回调、验证码、轻量任务。冷启动和超时要设计进去,不适合长事务硬塞。 Functions scale per call — callbacks, codes, light jobs. Design for cold starts and timeouts; do not force long transactions in.

云原生Cloud-native

容器、编排、声明式配置,让测试和生产尽量同一套描述。配合 CI/CD 和可观测性,发版才可重复。 Containers, orchestration, and declarative config keep environments alike. With CI/CD and observability, releases become repeatable.

前瞻Looking ahead

AI接入,建立知识模型库 AI should be optional, and explainable.

模型可以写草稿、做检索、帮客服分类,但不能替代审核和责任人。我们把 AI 当成可插拔能力:数据最小化、日志脱敏、关键步骤仍由人确认。 Models can draft, retrieve, and triage. They do not replace review or ownership. We treat AI as a plug-in: minimize data, redact logs, and keep a person on the critical step.

LLM API

调用大模型接口做摘要、改写、客服草稿。只传必要上下文,不把完整账号或证件原文送出去。 Use large-model APIs for summary, rewrite, and support drafts. Send only needed context — never full accounts or ID documents.

RAG

检索增强生成。先查自己的文档和规则,再让模型组织语言,减少凭空编造。 Retrieval-augmented generation. Look up our docs and rules first, then let the model phrase the answer — less invention.

端侧推理On-device ML

分类、建议尽量在手机上完成。数据不出设备,延迟更低,也更适合隐私敏感场景。 Classify or suggest on the phone when we can. Data stays on-device, latency drops, and private cases stay private.

Agent

把多步操作串成可监督流程,例如整理材料、起草回复。付款、删除、对外发送仍需人工确认。 Chain steps into a supervised flow — gather files, draft a reply. Payments, deletion, and outbound send still need a person.

可观测性Observability

指标、日志、链路追踪。没有这些,微服务和 AI 调用出了错,只能猜。 Metrics, logs, traces. Without them, a broken microservice or model call is guesswork.

CI / CD

持续集成与交付。测试、签名、商店包和后端发布走同一条流水线,减少「只有某台电脑能发版」。 Continuous integration and delivery. Tests, signing, store builds, and backend deploys share one pipeline — no single magic laptop.

术语Terms

软件团队常听到的词汇 Words you hear on a software team, in one line each.

SDK
软件开发工具包,把推送、登录、支付等能力封装成可调用的库。A packaged library for capabilities like push, sign-in, or payments.
API
应用程序接口。两端约定路径、字段和错误码,才能各自改实现而不拆掉对方。A contract of routes, fields, and errors so each side can change internals without breaking the other.
Native
原生:直接使用系统提供的语言和控件,系统新能力通常最先在这里出现。Native: system languages and controls. New OS features usually arrive here first.
Cross-platform
跨端:一套业务代码跑双端,省重复,但系统深度能力往往要再写原生插件。One business layer on two OS. Less duplication; deep system APIs still need native plugins.
SaaS
软件即服务。用户用账号使用在线能力,而不是只买一份装在本地的安装包。Software as a service: an account and a running system, not only a local installer.
IaaS / PaaS
基础设施即服务、平台即服务。前者租机器和网络,后者直接用运行环境和中间件。IaaS rents machines and networks; PaaS gives you a runtime and middleware without owning the metal.
Container
容器:把程序和依赖打成可移动的运行单元,减少「我这能跑、服务器不行」。A portable runtime with dependencies packed in, so “works on my machine” is less of a surprise.
gRPC / REST
两种常见接口风格。REST 偏资源与 HTTP;gRPC 偏强类型、高性能内部调用。Two API styles: REST over HTTP resources; gRPC for typed, high-throughput internal calls.
OAuth / JWT
授权与令牌。用来证明「是谁、能做什么」,而不是把密码传来传去。Auth and tokens: prove who someone is and what they may do, without shipping passwords around.
SLA
服务级别约定。软件服务行业里,可用性、响应时间往往写进对客承诺。Service-level agreement. Availability and response time are often part of the customer promise.

产品Selected work

体验官,以及同系列应用 体验官, and apps in the same line

当前上架的 iOS 应用是体验官。运营侧用 MVC 管理后台审核任务、处理账号与客服。同系列还规划了试用手记、应用雷达和支持匣,界面与接口约定尽量对齐,方便以后共用账号与支持入口。 The current iOS app is 体验官. Operations use an MVC admin console to review tasks, accounts, and support. The same line also includes Trial Notes, App Radar, and Support Case — aligned UI and APIs so accounts and support can stay shared.

iPhone · iOS · 当前上架iPhone · iOS · Live

体验官

应用体验任务平台 An app-experience platform

在 App 内浏览体验任务,了解参与条件与步骤,完成体验后提交真实反馈,并在任务记录中查看审核进度。客户端负责体验;任务、提交材料和审核状态走服务端接口,由管理后台处理,便于追踪和后续维护。 Browse experience tasks, read the requirements, try the app, submit honest feedback, and follow review progress in your task history. The client owns experience; tasks, submissions, and review status sit behind APIs and the admin console so we can trace and maintain them.

  • 先看规则,再决定是否参与Read the rules before you join
  • 提交材料与进度都留在账号内Submissions and status stay in your account
  • 审核在 MVC 管理后台完成,App 内可回看结果Review happens in the MVC admin; results are visible in the app
获取支持Get support
Web · MVC

体验官管理后台 体验官 Admin

用 MVC 拆开数据、页面与操作 MVC: data, screens, and actions kept apart

管理后台给运营使用,不面向普通用户。体验官 iOS 客户端只负责浏览、提交和查看进度;任务配置、材料审核、账号处理、客服工单和系统日志放在后台。采用经典 MVC,避免把审核规则写进 App,也避免运营直接改数据库。 The admin is for operations, not end users. The iOS app handles browse, submit, and status; task setup, review, accounts, support tickets, and logs live in the console. Classic MVC keeps review rules out of the app and keeps operators off the raw database.

Model

任务、用户、提交材料、审核状态、奖励与配置。iOS 与后台共用同一套 REST 契约。 Tasks, users, submissions, review state, rewards, and settings. iOS and admin share one REST contract.

View

列表、筛选、详情、审核台和设置页。运营只看界面,关键字段有校验和权限。 Lists, filters, details, the review desk, and settings. Operators see screens; fields are validated and permissioned.

Controller

领取审核、通过或驳回、账号处理、策略配置。操作写日志,角色决定能做什么。 Claim a review, approve or reject, handle accounts, change policy. Actions are logged; roles decide who may act.

  • 任务管理:创建规则、步骤说明与审核标准Tasks: rules, steps, and review criteria
  • 任务审核:查看截图等材料,通过、驳回并回写进度Review: inspect materials, approve or reject, write status back
  • 用户、客服反馈、消息通知、法律文档与系统日志Users, support tickets, notices, legal docs, and system logs

同系列 iOS 应用 iOS apps in the same line

这三款与体验官同一产品线:先看规则、少收集、人可以找到我们。客户端走原生 iOS,业务状态仍由服务端和 MVC 后台保管。 Three apps in the same line as 体验官: rules first, collect less, stay reachable. Native iOS on the client; business state stays on the server and in the MVC admin.

iPhone · iOS

试用手记 Trial Notes

把一次上手拆成可回看的步骤:时间线、截图草稿和备注。适合在提交体验官任务前,先在本地整理材料,不把半成品直接送进审核。 Break a first-run into a timeline of screenshot drafts and notes. Useful before submitting a 体验官 task — keep unfinished material on-device instead of sending it into review.

  • 步骤可增删,提交前可再编辑Steps can be edited before you send
  • 相册权限仅在你选择配图时申请Photos permission only when you add an image
iPhone · iOS

应用雷达 App Radar

浏览待体验的应用清单,按类型筛选和收藏。每条先展示权限、用途和参与说明,你看完再决定是否打开体验官去领取对应任务。 Browse apps you might try, filter by type, and save a shortlist. Each row states permissions, purpose, and how to join — then you can open 体验官 to take the matching task.

  • 说明写在前面,不默认开始体验Copy comes first; a trial does not start by default
  • 收藏留在账号内,可随时取消Saves stay in your account and can be cleared
iPhone · iOS

支持匣 Support Case

把账号、任务进度和隐私请求收成可追踪的工单。提交后可在 App 内查看状态,后台客服与企业邮箱 postmaster@dctyym.cn 走同一套记录,避免口头承诺无法核对。 Turn account, task, and privacy requests into trackable cases. Status is visible in the app; support and postmaster@dctyym.cn share the same record, so verbal promises are not the source of truth.

  • 工单编号可回看,处理结果会写回Cases have IDs; outcomes are written back
  • 删除账号等敏感请求仍会核验身份Sensitive requests, like deletion, still verify identity

原则Practice

我们怎么做软件 How we make software

01

说明写在前面Say it first

权限、用途、奖励与限制,尽量在使用前讲清楚。架构选型也同样:先写清约束,再决定单体还是拆分。Permissions, purpose, rewards, and limits are explained before use. Architecture is the same: write the constraints, then choose a monolith or a split.

02

只收集必要信息Collect less

不为营销档案而收集数据。能留在设备上的,就不放进额外档案。接入模型时也一样,上下文能短就短。We do not collect data to build marketing profiles. If it can stay on-device, it should. The same rule applies to model context: keep it short.

03

人可以找到我们Stay reachable

隐私请求、账号问题和产品咨询,可通过企业邮箱、电话或办公地址联系我们。自动化不能替代可追责的入口。Privacy requests, account issues, and product questions can reach us by email, phone, or at our office. Automation does not replace an accountable door.

支持Support

需要帮助时 When you need us

这是广州华任通网络科技有限公司的 App Store 支持页。账号、任务、隐私或使用问题,可通过企业邮箱、电话与我们联系,也可前往办公地址。 This is the App Store support page for Guangzhou Huarentong Network Technology Co., Ltd. For account, task, privacy, or product questions, reach us by email or phone, or visit our office.

常见问题FAQ

这个网站和开发者是什么关系?How is this site related to the developer?

dctyym.cn 是广州华任通网络科技有限公司的官方网站。华任通是本公司品牌名。企业邮箱 postmaster@dctyym.cn 与网站域名属于同一主体。dctyym.cn is the official website of Guangzhou Huarentong Network Technology Co., Ltd. Huarentong is our trade name. The mailbox postmaster@dctyym.cn uses the same domain as this site.

如何联系开发者?How do I contact the developer?

可通过企业邮箱、座机电话联系,或前往办公地址。来信请注明 App 名称、设备系统和问题描述。Contact us by company email, phone, or visit the office. Please include the app name, device, iOS version, and a short description.

如何删除账号或个人数据?How do I delete my account or data?

请发邮件至企业邮箱说明删除请求。我们会在核实身份后,按隐私政策处理账号与相关数据。Email a deletion request to the company mailbox. After identity checks, we process account and related data under the Privacy Policy.

应用目前支持哪些设备?Which devices are supported?

体验官当前面向 iPhone,系统版本以 App Store 页面显示为准。同系列的试用手记、应用雷达、支持匣同样以 iPhone 为主。体验官 currently supports iPhone; the minimum iOS version is listed on the App Store product page. Trial Notes, App Radar, and Support Case in the same line are also iPhone-first.

你们提供哪些软件服务?What software services do you provide?

移动应用开发、后端接口、发版运维与合规支持。详见本页「服务」与「架构」两节。Mobile apps, backend APIs, release operations, and compliance. See Services and Stack on this page.

产品会接入人工智能吗?Will the product use AI?

会按功能需要接入,例如草稿、检索和分类;关键操作仍由人确认,不会把完整隐私数据送进不可控模型。Where it helps — drafts, retrieval, triage. A person still confirms critical actions, and we do not send full private records into uncontrolled models.

联系我们Contact us

工作日通常会回复。涉及账号安全或隐私权利请求时,可能需要额外核验。 We typically reply on business days. Account-security and privacy requests may need extra verification.

开发者Developer
广州华任通网络科技有限公司 Guangzhou Huarentong Network Technology Co., Ltd.
官方网站Website
企业邮箱Email
座机电话Phone
办公地址Office
发送邮件Send email