Name	Ge Xianjing (葛娴静)
Student ID	0377636
Company	Nanjing Youqifu Information Technology Co., Ltd. (南京优企赋信息技术有限公司)
Role	UI Design Intern
Product	Youqifu / Youqi Asset APP (优企赋 / 优企资产app)

2026-09-14

Daily work

Visited the company, learned about the overall business, and met colleagues.
Handover and business review: On day one, completed handover with the previous designer—project source files, design specifications, and version iteration details. Reviewed the V2.5 task list from the product manager, clarified the business positioning, page scope, and core logic of the Authenticity Guarantee (保真保障) module, and quickly built an overall understanding of the platform’s asset-trading business. Coordinated with UI teammates on onboarding and app setup, and worked against the product manager’s functional specifications.
High-fidelity prototype delivery: Based on the existing Axure low-fidelity framework, used Adobe XD to refine high-fidelity UI for the Authenticity Guarantee module across about eight core pages—product management, listing/delisting, payment-to-recovery, refund request, product detail, info page, payment-success asset page, and list page. Delivered the Authenticity Guarantee modal component in high fidelity and standardized layer structure, control styles, and modal logic.
Design-tool evaluation: During prototyping, assessed Adobe XD limits around component-library growth, complex animation, and multi-user collaboration. Discussed alternatives with the product manager and earlier developers; concluded that Figma is better for collaboration and decided to continue with Figma.

**Fig. 1.** Authenticity Guarantee / Deposit module WIP

**Fig. 2.** Handover meeting with UI colleagues

**Fig. 3.** Team communication / alignment

**Fig. 4.** Onboarding / joining the company team

**Fig. 5.** App / mini-program environment setup

**Fig. 7.** Work-in-progress UI screen from this period

Learning

Quickly grasped the industrial trading platform’s business logic and understood Authenticity Guarantee as trust infrastructure; learned to scope UI needs from business goals rather than visuals alone.
Became familiar with converting low-fidelity prototypes to high-fidelity ones, and with how component reuse and a unified grid improve efficiency in platform products.

Reflection / Improvements

Insufficient grasp of business rules and terminology; information hierarchy for rules in early drafts was unclear. Need to read PRDs earlier to remove ambiguity and reduce rework.
Underestimated tool fit before kickoff; evaluate tool vs. project complexity up front to avoid mid-project switches that hurt schedule.

2026-09-15

Daily work

Iterated login/registration, Authenticity Deposit / Authenticity Guarantee flows, the assets module, and the overall UI system; completed a prototype iteration of the V2.5 Authenticity Deposit management module (first in Adobe XD, then remade in Figma).
Login/registration redesign: Redesigned login, registration, and related modals; unified type scale, font specs, and grid; strengthened the blue–purple brand layout and added industry-themed backgrounds for a more professional, consistent look. Simplified earlier “clubby” screens that lacked brand character.
Business naming and tag standards: Unified naming for Authenticity Guarantee / authenticity deposit and related terms; refined visual weight and styles of Authenticity Guarantee tags for clearer recognition and global UI consistency; confirmed the final solution after several rounds.
Assets module expansion: Added an asset search page and improved discovery/browse paths; aligned information architecture and module layout with industrial-goods positioning to raise search efficiency.
Global UI components: Tuned buttons, tags, and base components under a blue/purple brand system to reinforce professional and enterprise-service attributes.
Payment detail and rules modals: Improved layout of business fields, status, and actions on payment detail; raised readability of rules modals with consistent padding, heading hierarchy, and text structure; used distinct colored tags for jumpable clause links.
Product detail module restructure: Removed the top deposit-payment button and replaced it with a brand-guarantee banner (including brand-guarantee iconography) to present platform safeguards more clearly and build trust.

**Fig. 8.** Adobe XD source files before Figma rebuild

Fig. 11. Before: old login/membership UI (needs brand simplification)

**Fig. 13.** Label exploration — draft options

**Fig. 18.** Note: tappable legal clauses need distinct link colour

Learning

Applied global layout standards for B-end products and saw how component reuse and style consistency speed multi-page iteration.
Reinforced “design serves business goals”: detail-page changes optimized the trust-conversion path by surfacing guarantee information earlier.
Rule-oriented information design: hierarchy, whitespace, and sectioning improve long-text modal readability.

Reflection / Improvements

Asset search logic is still incomplete for multi-dimensional industrial filtering; will extend filters per PRD.
Weak habit of depositing components into the design system the same day; will follow “iterate once, deposit once” to grow the component library.

2026-09-16

Daily work

Business-rule check: Fully reviewed clause annotations in the Authenticity Guarantee module, verified design vs. business rules, and fixed mismatched wording and inconsistent information hierarchy.
Design-process training: Attended foundational design training covering the full path—requirements review → prototype → interaction review → visual delivery → development review—and delivery standards.
Competitive UI study: Analyzed four peer asset-trading mini-programs (JD Auction, Alibaba Auction, Hotel Home, China Auction Platform) across layout, button interaction, forms, modals, and filters; distilled reusable points into a competitive-analysis brief for the redesign.
Login UX: Redesigned the login modal. After comparing peers, adopted lightweight one-tap phone login, dropped cumbersome account/password registration, shortened the path, and locked the final simple login page.

**Fig. 22.** Final simplified one-tap phone login

Learning

Built awareness of a standardized design process: UI is requirements-centered functional design, balancing business logic and UX.
Learned to dig beneath surface style into interaction logic when studying competitors.
Understood lightweight entry design: shorter login paths lower barriers for transaction products.

Reflection / Improvements

Competitive analysis still leans visual/interaction; need deeper business-logic and persona inference tied to product positioning.
Requirement gaps were caught late in review; will do fuller requirements review before design starts.

2026-09-17

Daily work

Deep page analysis of about six peer products including Alibaba.com (International) and Zhidian mini-program; focused on Alibaba.com’s overall design process—information presentation, layout logic, and navigation patterns—and formed a same-day learning summary with design insights.

Learning

High-density information pages: prioritize content over decoration; balance completeness and browsing comfort via whitespace and structure.
User-centered design: simplify flows and lower comprehension cost while guiding conversions (order, register) aligned with business goals.
Modal & navigation strategy: deep-level nav can be hidden and recalled via a floating control to reduce visual load without breaking the task path.

Reflection / Improvements

Past density control was imprecise (stacking or excess whitespace); will prioritize information by scenario.
Navigation lacked systemic thinking; will design for end-to-end navigation, not single-page looks.

2026-09-18

Daily work

Personal/enterprise identity selection: Designed identity selection and routing to support both personal and enterprise users, matching different paths and permissions and improving first-entry experience; confirmed final style after comparing options.
Competitive intent analysis: Studied identity-selection patterns (e.g., Beike/KE) for layout, copy, and feedback; extracted identity-routing methods suitable for an industry consulting platform and applied them.

**Fig. 24.** Identity selection — layout options

Learning

Identity routing is a critical node for B+C hybrid products—match scenario at entry so each identity gets the right IA and presentation.
Design-intent inference: look past surface style to user scenarios and business goals behind competitor screens.

Reflection / Improvements

Visual differentiation between personal and enterprise was weak; will strengthen via icons, copy, and visual weight.
B-end scenario understanding is still shallow; will learn enterprise habits and decision paths more actively.

2026-09-21

Daily work

Mini-program UI design-system consolidation: Referenced mature commercial UI specs on ZCOOL (https://www.zcool.com.cn/) and related articles; systematized mobile UI basics across size system, type, buttons, containers, icons, and grid for a trading mini-program.
Baseline & control sizing: Defined structure rules for a 375×812 artboard; fixed status / nav / tab bar heights and safe areas; established three-level type scale and weights for title, body, and helper text.
Componentization in Figma: Deposited reusable components covering proportion, related layouts, icon consistency, text legibility, and button priority to speed later pages.
Page information organization: Documented IA logic and methods for grid focus and layered visual hierarchy under high-density business content.
After company/side tooling defined UI standards, subsequent pages can be produced strictly to those requirements.

**Fig. 26.** Reference: commercial UI spec study (ZCOOL)

Learning

Design specs are foundational infrastructure for consistency and team efficiency—not scattered style notes.
Mastered common mobile mini-program standards (safe areas, control heights) to deliver development-ready comps.
Deepened “design once, reuse many” for B-end iteration by extracting shared components from single pages.

Reflection / Improvements

Specs lean generic; some components underfit high-density industrial display—will tune to business scenarios.
Component naming/structure not standardized enough for team reuse; will apply atomic-design structure and naming.

2026-09-22

Daily work

Full-sequence page design for the platform quotation workflow; delivered high-fidelity core quotation pages and components while unifying layout standards for clearer, more consistent operation paths.
Core business windows: Quotation detail, edit-quotation modal, cancel-quotation confirm, and purchase-related modal covering key operation nodes.
Extension modules: Linked asset display, fixed bottom action bar, and asset-sale detail modal to strengthen information linkage along the path.
Horizontal list interaction: For multi-field quotation lists on narrow mobile widths, designed horizontal scroll with slide hints and column presentation to balance completeness and browsing.
Architecture simplification: Clarified relationships and jump hierarchy among product detail, personal center, my orders, product management, and merchant center.
Delivery & component output: Applied 375×812 specs across configs, buttons, modals, status tags, tables, and metrics; prepared SVG components importable into Figma (initial version pending product alignment).

Learning

B-end trading page logic: organize around business flow; separate core actions from secondary info to close the operation loop.
Experience with dense mobile tables—when horizontal scroll / collapse fit multi-field display.
“Design first, specs in sync”: deposit components during iteration to avoid later visual drift.

Reflection / Improvements

This is only the first product-side draft and will need further updates; strengthen modal visual weight and secondary confirms by risk level.
Jump logic incomplete for exceptions/edge cases; will add empty and error states from the PRD flow.

2026-09-23

Daily work

Focused on the auction mall’s dual modes—“quotation + purchase contact”—and designed the full user operation path into a closed trading loop.
Quotation flow mapping: Full sequence for ordinary asset users—product detail, view quotation history, fill/submit quotation, personal quotations, edit, and supplement—aligned with product requirements.
Quotation module UX: On product detail, horizontal-scroll presentation of quotation list, amount, time, and user info to solve multi-field space limits.
Status system: Quotation detail/ops pages with tags for In progress / Revoked / Expired and matching permissions.
Purchase-contact flow: Purchase-contact modal, price/quantity, order, payment, and post-payment unlock of contact details.
Order system: “My purchases” with Pending payment / Paid / Completed / Closed, plus detail, cancel, and contact seller.
Icon system & brand exploration: Unified quotation, contact, and mall icons (stroke, size, radius, weight); multi-option exploration for enterprise app-store icons.
Path-centered design linking View asset → Quote → Manage quotes → Purchase contact → Pay → Contact seller; emphasized convert actions (submit quote, buy now, pay) and de-emphasized/warned high-risk actions (revoke, cancel) to cut mis-taps.

Learning

Trading-loop thinking: experience hinges on the full path, not single-page beauty.
State-driven design: status tags lower comprehension cost when info and permissions change by state.
Action-weight design guides conversion while mitigating operational risk.

Reflection / Improvements

Dual modes still look too similar; need stronger visual/action differentiation between quote and purchase.
Enterprise store icons under-express industrial brand professionalism; refine against brand tone.

2026-09-24

Daily work

Focused on visual-asset quality upgrade, icon system optimization, home navigation restructure, ops popup design, and continued Quotation V2.6 iteration.
Home category nav icons: Replaced cluttered, weakly recognizable icons with blue–purple 3D-style icons tied to business categories; moved to no-background style for clearer category bar. Iterated with Photoshop and Doubao AI (e.g., removed unprofessional “glasses” elements) and checked effects in backend version testing.
Newbie welfare popup: First version of “Newbie welfare · claim cash rewards” popup for ops/procurement campaign needs; compared minimal vs. high-stimulus variants.
Quotation V2.6: Continued related design; finalizing after product supplies remaining business details; leftover features planned for the next day.

**Fig. 38.** Original admin / homepage category icons

**Fig. 39.** Icon draft 2 — unified blue–violet palette (PS + AI)

**Fig. 40.** Staging test — checking icon scale and colour

Learning

Fine icon craft and multi-device pixel precision—from sketch to shippable icons.
Nav icon principles: recognition first, business-linked, on-brand, without stealing focus from content.
Ops popup experience: brand tone, motivation, and message efficiency affect conversion.

Reflection / Improvements

First popup lacked pixel/output rigor; will set ops-asset output standards (size, DPI, format).
Product info sync lagged for Quotation V2.6; will proactively track requirements to avoid idle wait.

2026-09-25

Holiday

2026-09-28

Daily work

Delivered high-fidelity iteration for Youqi Asset Cat mini-program—about 20 designs covering category home, category modal, product list, filters, category nav, empty states, category-switch interactions, lottery popups, and quotation-related pages.
Category system replacement: Per backend old/new category tables, replaced old categories (plants, construction firms, etc.) with logistics & supply chain, media/ads, film & manufacturing, F&B/culture-tourism, commerce & trade, etc.; updated tables, icons, and spot illustrations; optimized oversized images that hurt title/page load.
Lottery popup visual upgrade: Richer style and layout; copy revised per request; manager-approved. High-pixel assets needed compression for runtime.
3D drawing assets: ~90 architecture-related 3D drawings designed, pushed to the test build, and verified on-device.
Quotation V2.6: From product walkthrough, listed UI change points and pending design tasks.
Page & state QA: Fixed long category-name wrapping and nav precision; polished default/selected/expand-collapse states; unified category modal, side nav, and filter interaction against backend data; multiple backend checks for icon color sampling.
Self-check & handoff: Verified page inventory, information consistency; delivered development-ready Figma high-fidelity sources.

**Fig. 42.** Category system / navigation

**Fig. 46.** Staging checks — icon colour absorption / contrast

Learning

Category redesign must match backend architecture and browse habits—not cosmetics alone.
Pre-delivery self-check: specs, states, and logic validation for shippable HF comps.
Performance belongs in design: asset size/format affect load; balance look and performance early.

Reflection / Improvements

Global color system still messy—need a fixed brand palette and primary/secondary roles.
Quotation V2.6 features incomplete; accelerate detail polish for on-time delivery.

2026-09-29

Daily work

Audited home test-build color issues—inconsistent saturation and mixed warm/cool tones across combo recommendations, category entries, sorting, etc.—and defined a cleanup toward a more professional business look.
Around brand primary #254BFF, defined a unified cool-tone saturation system (~15 standard values across brand/gradients, neutral text, and low-sat functional colors; functional saturation ~5%–18%).
Module-by-module finals: combo recs = white ground + cool micro-tags; sliding category entries in blue / blue-purple / cool cyan / cool teal; promo modules replaced orange with cool cyan-blue to reduce “e-commerce” feel; goals/service blocks in blue-gray with low-sat gray-gold accents.
Validated visual weight order: primary category nav > secondary filters > content; replaced Tab bar icon default/active styles.

**Fig. 47.** Category navigation after taxonomy update

**Fig. 48.** Homepage primary category icons after colour system

Learning

Low-saturation cool systems strengthen B-end professionalism and information clarity—richer color is not always better.
Color gradients/saturation can encode information priority so visual guidance matches IA.
Brand color architecture = primary steps + secondary + functional layers, not painting everything with the brand hue.

Reflection / Improvements

Over-unified category entries lost some distinction; keep cool family but use subtle hue shifts.
Colors not yet Design Tokens in Figma—manual tweaks are error-prone; will publish tokens for one-click reuse.

2026-09-30

Daily work

Designed the primary “Lottery” red-envelope floating entry—lightweight red-packet form with campaign copy, matching ops style while keeping visual weight low so it does not disrupt core browsing.
Received product’s Quotation V2.6 plan confirmed on 18 Sep; diffed old vs. new requirements, clarified page restructures, and started the redesign.
Drove overall rebuild of detail modals with simplification plus added detail content; iterated interaction and visual logic for the redesign.

Learning

Faster response to requirement change: split add/modify/delete and plan design priority.
B-end iteration often means subtraction for core-path fluency—not feature pile-up.

Reflection / Improvements

Before making, reference more peer floating-entry visuals from similar apps.

2026-10-01~07

Holiday

2026-10-08

Full quotation page-sequence audit against the structure tree: Product detail → Quotation list → View quotation → Quotation detail → Confirm order; aligned naming, hierarchy, and business flow; handled delete-state updates and related cleanup.
App & mini-program icon finalize: AI-generated icons had blurry type/pixels; redrew in Photoshop for crisper subject and type. Leadership asked to combine auction/quotation/shopping attributes with the cat mascot; tried Illustrator (unfamiliar), then Photoshop. Later guidance: do not combine with the cat (avoid cat-ear effects). Finalized “Youqi Asset” App icon.
Ops floating entry polish: Lottery side float to right-edge style (arc + straight right edge), shorter copy, light coin accents, unified red–gold ops colors with the mall block.

**Fig. 57.** App icon iteration — cat-ear direction later dropped

**Fig. 58.** App icon — switched from Illustrator to Photoshop

**Fig. 59.** Final App / mini-program icon — Youqi Asset

Learning

Clear IA and unified page naming underpin collaboration and lower maintenance cost.
Mobile table components: graphic area, density, and action weight—horizontal layout and de-emphasizing secondary actions help usability.
Micro-consistency (radius, spacing, type) across a series strongly lifts perceived craft.

Reflection / Improvements

Earlier lack of naming rules forced heavy cleanup; will standardize page/layer names from the start.
High-risk actions were only de-emphasized without secondary confirm; will add confirms/warnings by risk level.

2026-10-09

Daily work

Replaced experience-build assets and the second home icon with formal versions; advanced online testing to verify color/icon rendering in the real product.
Designed and uploaded cartoon characters for seven lottery-wheel prize tiers; unified campaign visual language for ops feedback.
Continued product-catalog replacement; backend test environment unfinished—planned to continue next day.

**Fig. 60.** Lottery / campaign floating entry

Learning

Differentiated multi-tier campaign assets quickly while balancing efficiency and variety.
Design landing must flex with engineering/test cadence, environment, and schedule.

Reflection / Improvements

Pre-launch full checks incomplete—resource swaps can desync; will use a launch checklist.
Multi-task priority control weak on catalog replacement; will forecast collaboration risks and buffer time.

2026-10-12

Daily work

Quotation list module (core): Unified visual design—header columns User / Quotation / Time; light gray-blue rounded header + bold blue + sort arrows; time as single-line 2026/07/28 12:31 (slash-separated, no seconds), right-aligned; before/after comparison completed.
Requirements alignment with product: Walked the full quotation flow; confirmed buyer/seller role boundaries and copy (e.g., “Contact seller / View contact”, “Unlock seller / buyer contact”); edited narrative text for consistent dual-role wording.
Full-path design walkthrough (~21 pages): Product detail (with/without quotations), fill-quotation modal, my quotations, quotation detail, re-quote/delete modals, confirm order, payment success, order states (not received / received / completed), view contact, quotation history, product management, merchant/ownership center, my orders, personal center, etc.

**Fig. 69.** Before: quotation list layout

Learning

Dual-role B-end design: buyer vs. seller differences show up in copy and information priority, not only permissions.
Full-path walkthrough from the business flow catches omissions better than page-by-page spot checks.
Horizontal tables on narrow screens: scroll balances density and efficiency; keep core actions fixed and reachable.

Reflection / Improvements

Role differentiation still shallow on some pages (copy-only); deepen information priority per role.
Walkthrough under-covered trading logic, exceptions, and empty states; expand checklist and talk more with product.

2026-10-13

Daily work

Organized previously produced files and completed backup/archiving.

2026-10-14

Daily work

Reviewed frontend implementation of the V2.5 Authenticity Deposit management module: compared live UI with high-fidelity Figma—icon size, dimensions, type, image placement, and button layout.
Found and fixed issues including icon style/size drift and action buttons placed too low; improved Authenticity Deposit management page visuals, icon sizing, and functional icons; addressed tilt/size issues in the App from the UI side and continued follow-up against post-launch results.

**Fig. 72.** Authenticity Deposit page — after UI fixes

**Fig. 73.** After: quotation list (User / Quote / Time)

**Fig. 74.** Live / shipped result on device

**Fig. 75.** Functional icons redrawn to match the set

**Fig. 76.** Device QA — size / UI-level adjustments

Learning

High-fidelity comps do not always match on real devices; proportions that look right in Figma can shift on phones—early communication with frontend is essential.

Reflection / Improvements

Need closer attention to proportion, spacing, and device testing. V2.5 issues forced extra frontend tweaks and reinforced the value of design specs.
For V2.6, adopt a more unified size system and a final check path: Figma → frontend implementation → mobile test → requirements check → review, to cut rework and raise design–product consistency.

2026-10-15

Daily work

Primarily designed the new mini-program Due Diligence Report (尽调报告) module; most of the day was spent producing its pages.
Aligned requirements with product, especially dual-role copy: seller vs. buyer see different narrative text on the same screen (e.g., “Contact seller” vs. “View contact” must not be mixed). Started pages after alignment.
Eight pages on 375×812 (content width ~351):
Publish asset (5 pages): (1) Default—enterprise category selected, no enterprise chosen; (2) Related-enterprise dropdown—after typing “Youqi Chuanglian”, show three Tianyancha-matched companies (name + tax ID); (3) With reports—list sorted by generation time descending; (4) No report—prompt “You can run due diligence at this enterprise~” with “Go to due diligence”; (5) Personal mode—hide enterprise name; prompt to upload a due-diligence report for personal assets.
Asset detail (2 pages): (6) With report—“Due diligence done” badge under price plus PDF entry; (7) Without report—no due-diligence notice.
Quick entry (1 page): (8) Row of Home / Search / Profile plus “Go to due diligence” jumping to the Youqi Report mini-program.
Color hierarchy: white ground / gray text; blue for primary, purple for personal; blue/cyan distinguishing report list items; orange for no-report prompts. Type ~12px, consistent with the earlier quotation-list system.
Also delivered a contact-support float on the deposit confirm-payment page (bottom-right), styled to the blue system.

Issues encountered

Status tags such as “Due diligence done” on asset detail are not yet fully specified. Plan a dedicated tag area for “Due diligence done”, “Due diligence completed”, “Near first-hand asset”, etc., so they do not clutter price/title—scheduled for the next day.

2026-10-16

Daily work

Detail polish on the Due Diligence Report module. With yesterday’s master set ready, reordered blocks per feedback: moved “Go to due diligence” to the top—Asset category → Enterprise name → Select report—so the primary action is visible sooner and the flow feels smoother.
Separated merchant-side vs. user-side design logic: different screen sizes mean one master cannot be reused; merchant side is denser/ops-oriented, user side is display/guidance-oriented—field order and trading focus differ.
PDF indicator: Replaced document icon with tag styles and locked a tag system—full-pill capsules; light fill + deep text = default; solid fill + white text = emphasis; fixed color semantics (green = due diligence done/certified, blue = service, orange = scarce/feature); heights 20/24/28, type 10/11/12, horizontal padding ~8px.

**Fig. 83.** Due diligence — before reorder

**Fig. 84.** Due diligence — after reorder

**Fig. 87.** Status tag design specification

**Fig. 88.** Tags applied on product cards

Learning

Base pill style: default light fill + same-hue deep text (e.g. #E8F3FF + #165DFF); emphasis = solid + white (e.g. green “Due diligence done” with check); secondary = light fill + matching stroke.
Fixed color semantics: green = status/certification; blue = guarantee/service (Authenticity Guarantee, nationwide sale, self-operated); orange = scarce/feature (near first-hand); red = warning/promo.
Size ladder: heights 20/24/28 with type 10/11/12; radius = half height; padding 8px; icons 14px with ~4px gap to text.
Layout: tag gap ≥ 8px; left-to-right wrap; guarantee/status tags before service tags; max 3 per row, else “+2” fold.

Issues encountered

Merchant vs. user sizes/fields differ—reusing one master caused misalignment until logic was designed per side.

Apply the new content order and tag styles in mobile comps, then review with product.

2026-10-19

Daily work

Completed planned due-diligence work (including before/after checks).

Fig. 90. Work-in-progress UI screen from this period

Fig. 91. Work-in-progress UI screen from this period

Due to mini-program store review requirements, some feature blocks had been removed earlier; restored the corresponding blocks and advanced block replacement.
Exported Due Diligence module UI for deployment so engineering can proceed.

**Fig. 94.** Due Diligence Report module

2026-10-20

Daily work

Looked at how different WeChat mini-programs handle the "select city / location" section, and compared two common patterns: a province sidebar with a city list, and location + popular cities + an A–Z index.
Noted the key parts: current location, quick selection, popular cities, province/city/district browsing, the letter index, and the selected-state feedback.
Designed and built the location and city selection section for our product.

Reflection

A city picker that covers every city in the country needs both a quick path (location / popular cities) and a full browsing path (province levels or a letter index). One long list isn't enough.

2026-10-21

Daily work

Started designing the homepage carousel banners for 优企资产猫 (优企赋), aiming to deliver usable final versions within two days.
Clarified the requirements. The three banners are "Zero down payment for commercial property", "Company introduction / 就上优企赋", and "Upload assets and earn commission".
Used the same left-text, right-image layout for all three and settled on a professional B2B palette of light purple, blue and gold (light purple background, blue-purple gradient buttons, gold accents), avoiding a dreamy illustration style. For banners with many selling points, I layered the content as headline, subtext, three checkmarked selling points, a data bar at the bottom, and then the button.
Finished a complete first draft of the "Zero down payment for commercial property" banner in Canva and 稿定设计, with the copy and selling-point tags matched to the business wording.

2026-10-22

Daily work

Finished all three homepage carousel banners. The 3D tech-style visuals on the right were AI-generated, and the copy and buttons were laid out in PS / Canvas.
- Zero down payment for commercial property: headline and selling-point tags on the left, a building with keys and gold coins on the right. It highlights zero or low down payment, rent reduced by 50%–70%, and annual returns of 6%+.
- 优企赋 company introduction: "Buy businesses · Buy projects · Buy commercial property" with nationwide resource selling points, and a data platform with buildings on the right.
- Upload assets and earn commission: aimed at service providers joining the platform, stressing the 50/50 split, T+1 settlement and platform support, with a cloud asset library scene on the right.
Made a left-right text-and-image recruitment template in soft purple-blue ("好资产，上优企赋", "Good assets, on 优企赋") plus matching transparent flat assets.
Produced a 750×350 business-tech version based on the latest copy. The main visuals were selected, the copy finalised and the banners completed, so they're ready for cropping and launch.
Studied six banner composition types and made a quick-reference sheet.

Reflection

The more selling points a banner has, the more it depends on hierarchy. When the headline, selling points, data and button each have a clear role, the layout doesn't feel crowded.
Keeping the same composition, colours and button style across one carousel makes the brand feel consistent as the slides change.

2026-10-23

Daily work

Adjusted the homepage carousel banners based on feedback. On the zero down payment banner, I made the tag text larger, stretched the row wider to the right, and made the button taller.
Exported a 750×350 version and a high-resolution version.
Uploaded compressed images for the mini-program.

2026-10-26

Daily work

The project was paused because some colleagues were on leave.
I used the day to study website layout techniques.

2026-10-27

Daily work

Organised the copy for a long promotional poster for the 优企赋 property mall mini-program. I gathered all the text for the main business, resource coverage, platform support, asset services and the three types of recruitment support. I kept the original text without cutting anything and only improved the layout hierarchy.
Did a compliance self-check on the poster content, went through the advertising risk points, and added a disclaimer.
Set the visual style: light blue with dark blue for a business feel, a blue-and-gold city building main visual, and rounded information cards. Planned the page structure: homepage main visual, a separate platform support page, an asset services page, and a recruitment support page.
Finished the homepage main visual page in 稿定设计 and planned platform support as a separate second page. The full poster set is about half done.

Reflection

A commercial poster can't just aim to look impressive. Any figures or claims about returns need risk control, and a disclaimer should be planned in from the start.
A long landing image needs good page planning. Putting each module on its own page makes it easier to read on a phone.
The whole poster should keep the same colours, card style and type hierarchy, and the lighting effects should be kept under control so they don't get in the way of reading.
Long copy is easier to read when it's split by logic (core positioning, business support, value to partners), even without deleting any of the original text.

Progress: the long poster is about half done. Next I'll finish designing the platform support page, the asset services page, and the three-type recruitment support page.

2026-10-28

1. Long poster integration: I merged the three sections I designed separately yesterday into one complete long poster. In order, they are Platform Empowerment, Asset Services, and Join Us (the three-empowerment recruitment section). While merging them, I made the colours, spacing and heading levels consistent across all sections, and adjusted the transitions between modules so the poster reads smoothly from top to bottom.

2.Logo revision: I adjusted the Youqifu logo in Photoshop so it looks clearer and fits better on the dark blue background.

3. Main headline update:I replaced the hero headline with "找企业、找项目、找经营性物业，就上优企赋" ("Find companies, projects and commercial properties, all on Youqifu"). I also adjusted its font, size and layout in Photoshop so the headline stands out more.

Tools:Photoshop

Progress:All four sections of the Youqifu long poster are now combined, and the overall design is basically complete.

2026-10-29

1. Work content
Today I focused on visual assets for the Youqifu official website. I reviewed the current page structure and listed the image slots that need replacing (homepage banner, five business-ecosystem cards, three empowerment modules, etc.), then produced several mood-board directions and draft backgrounds (minimal geometry, dark cinematic looks, black-and-white line art, transitional color blocks) for later selection.

Website: Youqifu Asset Service Platform

2. Progress
The goal is clear: replace all preliminary images on the site. I finished a fairly complete first round of mood-board exploration and drafts, but the final set is not locked yet. The plan is to align style and color first through the mood board, then pick the final images and swap them onto the live pages later.

3. What I learned

Website imagery has to match each section’s job (banner space for white text, cards tied to each business type, empowerment panels matching the title meaning)—not just look good alone.
Building a mood board before locking finals is faster and easier for team alignment than forcing one finished asset too early.
On dark backgrounds, cutouts need to be clean, with clear layers and color-block transitions; otherwise the graphics look muddy or flat once placed on the page.

2026-10-30

1. Work content
Continued work on Youqifu official-site visuals. Focused on a set of red-derived background plates built from the site’s main brand red (light trails, people silhouettes, buildings, network nodes, etc.), and also prepared materials for other sections using soft hazy gradients plus asset-building imagery that better fits the corporate look.

Website: Youqifu Asset Service Platform

2. Progress
A comparable mood-board set of red-derived backgrounds is ready, and I checked the first selection with a teammate (they said these are enough for now). Other sections stay on the hazy-gradient + asset-building direction so the style feels more consistent. Final replacements still need to be picked from the mood board and locked later.

Oct 14, 2026 (EN)

Work done

1. Reviewed “water jelly”–style enterprise analysis report screenshots and mapped the report page IA: navy header + company name white card + tabs (Basic / Tax / Invoice / Suppliers) + tables and two-column metrics, noting share highlighting, related parties, and “View” link patterns.

2. Mapped that structure onto the upcoming eight-area due-diligence UI: reuse the existing due-diligence shell (pick company → overview → area forms → report preview); carry each area with white cards + field pairs + completion tags; make the report reading area follow the water-jelly tab + table density. Hold high-fidelity screens until product prototypes arrive.

3. Opened the Youqifu mini-program Figma and estimated design tokens for engineering: type (page title 18 / card title 15–16 / body 14 / label 12 / tag 10–11), spacing (page margin 16, in-card 12, between cards 8), primary blue `#254BFF` (also `#165DFF` and other variants in file), page background `#F7F9FC`, status green/orange/warning red; converted to mini-program rpx (1px ≈ 2rpx) for later eight-area design and handoff.

Learning

- The live mini-program CTA is mainly sapphire blue; legacy brand red fits warning states better and should not be the primary button. Lock one primary for the new due-diligence module so multiple blues do not coexist.

- Water-jelly reports are “reading tables”; current Youqifu screens are “action cards.” Split the eight-area work: action flows keep existing tokens; report flows borrow tabs + tables—do not restyle the whole product.

2026-10-15

Today’s Work

Researched B-end financial & tax app references (Electronic Tax Bureau App, Kingdee Jindouyun, Haokuaoji, FineReport Mobile) for mobile pages carrying massive tax statements and account details, and sorted out design solutions for high-density data pages on mobile.
Delivered the full design strategy for mobile financial & tax statements. Defined page hierarchy: metric dashboard → statement list → single-row detail. Adopted progressive drill-down information architecture to avoid directly squeezing PC-style tables onto mobile screens.
Summarized UI design rules for big-data mobile tables, covering information hierarchy, table interactions, filter & search, color status, form validation, typography and performance, and compiled concise design guidelines for subsequent component library development.
Identified common pitfalls of mobile tax statements: gesture conflicts, bulk data loading and information overload. Confirmed mobile-side positioning: for viewing, checking and simple approval; complex form filling to be redirected to PC.

Problems Encountered

Tax statements contain numerous fields. It is challenging to balance information completeness and readability within limited screen space; conflicts between horizontal table scrolling and page vertical scrolling.

Solutions

Keep only 3~4 core fields on the first screen. Secondary fields are placed in expandable rows or detail pages. Enable horizontal scrolling only inside the table area instead of the whole page.
Adopt summary cards at the top with progressive drill-down to details.
Use lazy loading + pagination for large datasets, paired with skeleton screens to improve loading experience.

Reflection

For B-end data pages, readability and business accuracy take priority over visual decoration. Colors are only used to indicate business status rather than decoration. The core of mobile design is simplifying information hierarchy instead of migrating PC content as-is.

Daily Log — Oct 16

Today:

Reviewed the previous 「优企报告」 design (XD “优企报告7.3”)—query flow (company authorization → smart collection → generate analysis) and report structure (overall score/grade; tabs for basic info, value analysis, tax, invoices, supplier/customer analysis; normal/abnormal indicators)—as reference for next week’s due-diligence / report UI.

Next week:

1. Draft information architecture and priorities for the eight-zone due-diligence pages from the old report tabs

2. Once product prototypes are ready, start the new report screens (score header, tab nav, indicator tables)

3. Align type, spacing, and primary color with current tokens; unify abnormal and empty states

Oct 19, 2026 (Mon) — Analysis + seminars

Today’s work

Analysis: Mapped the Youqi Report XD main flow (home logged-in/out → login → query/history/smart search → data collection → payment → report) and listed report tabs (basic info, tax, value, cost, finance, credit, invoices, suppliers, customers) as this week’s baseline for due-diligence UI.
Learning: Searched and booked online industry talks for Assessment 3 (~5h); checked Udemy/Coursera/YouTube against the brief and a senior’s sample; sent recording screenshots to the supervisor for proof rules.

Issue
Supervisor rejected recording-only screenshots; needs verifiable online attendance.

Action
Keep daily XD comparison for product work; switch learning to free live sessions or ones with registration/viewing records and a gradable report. Started UXPA registration.

Oct 20, 2026 (Tue) — Analysis + recorded/live options

Today’s work

Analysis: Compared XD “Me / orders / order detail / settings / about” with current Youqifu mini-program overlap; drafted first-pass high/mid/low priorities for moving report tabs into the eight-zone due-diligence UI (vs last week’s Report 7.3 notes).
Learning: Kept hunting sessions with view/registration records; checked free Udemy courses (UX Fundamentals, AR/VR) for topic fit; started the Weinschenk UX Fundamentals write-up (LO from course only; reflection tied to Youqifu / spatial projects).

Issue
Free on-demand courses often fit by topic but lack certificates / live proof.

Action
Live webinars first for proof; recordings only as graded-report material. Left the tab-priority draft ready for Wednesday’s deeper comparison.

October 26, 2026 (Monday)

Followed up on a product-direction change for due-diligence features on 「优企赋」. The earlier plan was a report flow where users enter content and the system generates a structured report; UI work had been moving along that path. The product has shifted toward AI Q&A instead, so the previous input-and-generate-report UI needs to be overturned. Design on this side is on hold until the product iteration is settled, then we’ll restart from the new flow.

Also noted which existing screens and flows are affected so the next round can rebuild against the updated path.

Product direction
Form-based due-diligence reports → AI Q&A. Users ask about their own company’s finances; after binding the company, they get a visual result, can follow up, and can revisit history.

Main user path
Enter Q&A → prompt chips / free-form question → confirm binding → generating → report card (KPIs + bar/pie charts + risks + full report / keep asking) → history (session-level cards).

Shipped today

Hi-fi: Enterprise Due Diligence · AI Q&A 375×812 (page: Confirmed Screens)
Lo-fi board: user flow + prompt screen; result/history locked as wireframes (session cards, tabs All / Finance / Due Diligence, swipe-to-delete, empty state)

Later derivatives (after product iterates)
Typing → ask for company → generating → report card → detail → valuation branch → empty / error states

Worked on extending the Asset Due Diligence AI Q&A input area. Referenced Doubao, ChatGPT and similar products for the “+” attachment panel, album/file upload, and post-select thumbnail-before-send pattern, then mapped features fit for due diligence: album, camera, financial statements, ownership certificates, appraisal reports, and general files; after picking, show removable thumbnails above the input with optional caption before send. Discussed this direction with the manager; we will define the feature system on Monday. Also decided to drop voice input and keep text + attachments only.

2026-11-02

Today’s work

Meeting: plan how to split human service vs AI service under financial-market regulation. Human side mainly gives concrete advice; AI mainly replies with existing/authorized data (charts, structured facts). Further routing and handoff rules still to be defined.
UI: prompt dialogs for empty state, unbound company, incomplete materials, and no permission—aligned title/body, primary/secondary actions (Confirm / Cancel), dismiss behavior, and brand blue.
Documented authorized data sources and light integration checks: reviewed tax/finance fields and sample payloads, updated the field map, and listed mismatches vs AI Q&A report cards for next week’s product/dev sync.

Notes

Need clear jump UI when AI hits advice-only territory → hand off to human (entry, copy, confirm).
Keep AI answers data-bound; avoid advice-like wording that triggers compliance risk.
Dialogs stay short; Confirm/Cancel hierarchy must match mini-program components.
Only authorized sources; flag field gaps early for the feature-system pass.

我为你整理了正式工作英文日报，贴合今日核心工作：推翻优先AI逻辑、调整产品迭代策略、参考蚂蚁阿福交互、双端UI低保真梳理、优先上线专家咨询模块，可直接复制粘贴。

Daily Work Report

Today, I conducted in-depth research and analysis on the AI question-and-answer and expert consultation interaction logic of the Ant Afu app. Combined with the due diligence consultation module of our platform, I optimized and adjusted the product iteration strategy.

In order to avoid excessive development complexity and invalid time cost caused by early access of AI interactive interfaces, we overturned the previous product solution dominated by AI guidance interaction. We have confirmed the new phased development priority: take the expert consultation module as the core pioneer function for the first launch, and the AI assisted guidance function will be iterated and optimized in the subsequent version.

In addition, I sorted out the differentiated UI design logic of mobile mini-program and PC expert backend: the mobile terminal is oriented to user consultation and information collection, while the computer terminal is used by professional experts for information viewing, data analysis and file transmission. Meanwhile, I completed the low-fidelity prototype sorting of the dual-terminal page framework, sorted out the business process of the expert consultation module, and assisted product and UI teams in docking subsequent visual design and function development work.

Work Plan for Tomorrow

Further polish the page layout and interactive process of the expert consultation module.
Cooperate with product personnel to confirm the final business logic and launch standards of the pioneer version.
Promote the UI design landing of dual-terminal official consultation pages.

Daily Work Report

Work Plan for Tomorrow

Further polish the page layout and interactive process of the expert consultation module.
Cooperate with product personnel to confirm the final business logic and launch standards of the pioneer version.
Promote the UI design landing of dual-terminal official consultation pages.

Daily Work Report

Ant Afu app

Ideas for mobile devices

Web based approach

Work Plan for Tomorrow

Further polish the page layout and interactive process of the expert consultation module.
Cooperate with product personnel to confirm the final business logic and launch standards of the pioneer version.
Promote the UI design landing of dual-terminal official consultation pages.