What Startup Developers Learned: Choosing Mobile & Backend Tech for a Fast‑Track App

Background

In June 2022 I joined a tiny startup whose founder lacked technical and managerial experience but pushed for a quick launch of an Android + iOS app while cutting labor costs.

Initial Tech Selection

With only a fresh front‑end developer and a UI designer, we chose a stack based on our existing front‑end and Node.js experience:

Use

uni-app

to develop the cross‑platform app, allowing future mini‑program extensions.

Use

egg.js

+

MySQL

for the backend, offering fast development and sufficient performance for our niche domain.

Use

antd-vue

for the admin panel to keep the front‑end technology consistent with

uni-app

.

Why Choose uni‑app for App Development

We compared native iOS/Android, Flutter, and React‑Native/Taro. Native development required hiring for both platforms, which the founder could not afford. Flutter required learning from scratch. uni‑app offered the best balance of familiarity and speed.

Why Choose egg.js for Backend

Although Java, PHP, or Go would be more robust, they were too costly.

egg.js

met all functional requirements, was easy to learn for JavaScript developers, and kept onboarding time low.

Mid‑Stage Struggles

Development proceeded on schedule, but the product failed to gain traction. The founder repeatedly brought in unrelated experts, demanded redesigns, and hired then fired staff, leading to constant scope changes and morale issues.

Later Technical Adjustments

Changed the app packaging strategy.

Introduced

midway.js

for new services, building on the existing

egg.js

knowledge.

Created internal npm packages and a component library.

Standardized code style and development processes.

Hiring and Team Management

Hiring

Small startups struggle to attract talent without high salaries, but our unified JavaScript stack allowed developers to contribute to both front‑end and back‑end, reducing resource waste.

Team Management

Adopt a business‑driven, realistic approach in the early stage.

Prefer full‑stack development to avoid coordination bottlenecks.

Define coding conventions based on the team’s habits.

Follow a disciplined workflow: product evaluation → task assignment → technical assessment → development → testing → code review → deployment → issue tracking.

Measure performance by deadline adherence, documentation quality, bug count, and careful database changes.

Encourage knowledge sharing and continuous learning.

Maintain open communication about progress and challenges.

Final Recommendations

Ensure the founder is reliable and decisive; otherwise projects rarely succeed.

Focus on generating revenue; without cash flow a startup cannot survive.

Prioritize core business problems over tooling or code conventions.

Provide timely updates to leadership and stay aligned with their high‑level perspective.

Extract lessons from every experience; each step adds value.