hipmi-mobile/tasks/TASK-005-OS-Wrapper-Implementation.md

TASK-005: OS_Wrapper Implementation

📋 Overview

Migrasi dari NewWrapper dan NewWrapper_V2 ke OS_Wrapper yang otomatis menyesuaikan dengan platform (iOS/Android).

🎯 Goals

• ✅ Mengganti penggunaan NewWrapper → OS_Wrapper di user screens
• ✅ Mengganti penggunaan NewWrapper_V2 → OS_Wrapper di form screens (dengan keyboard handling props)
• ✅ Memastikan tabs dan UI konsisten di iOS dan Android
• ✅ Backward compatible (wrapper lama tetap ada)
• ✅ SIMPLIFIED: Satu komponen OS_Wrapper untuk semua use cases (tidak ada PageWrapper terpisah)

📦 Available Wrappers

1. OS_Wrapper (Recommended - Unified API)

Auto-detect platform dan routing ke wrapper yang sesuai:

• iOS → IOSWrapper (berbasis NewWrapper)
• Android → AndroidWrapper (berbasis NewWrapper_V2 dengan keyboard handling)

Props:

// Base props (kedua platform)
withBackground?: boolean;
headerComponent?: React.ReactNode;
footerComponent?: React.ReactNode;
floatingButton?: React.ReactNode;
hideFooter?: boolean;
edgesFooter?: Edge[];
style?: ViewStyle;
refreshControl?: RefreshControl;

// Keyboard handling (Android only - iOS mengabaikan)
enableKeyboardHandling?: boolean;      // Default: false
keyboardScrollOffset?: number;         // Default: 100
contentPaddingBottom?: number;         // Default: 80
contentPadding?: number;               // Default: 16

2. IOSWrapper / AndroidWrapper (Direct Usage)

Untuk kasus khusus yang butuh platform-specific behavior.

📝 Migration Guide

Before (Old Way)

import NewWrapper from "@/components/_ShareComponent/NewWrapper";
// atau
import { NewWrapper_V2 } from "@/components/_ShareComponent/NewWrapper_V2";

After (New Way - Unified API)

import { OS_Wrapper } from "@/components";

// Static mode (simple content)
<OS_Wrapper>
  <YourContent />
</OS_Wrapper>

// List mode (with pagination)
<OS_Wrapper
  listData={data}
  renderItem={({ item }) => <ItemCard item={item} />}
  ListEmptyComponent={<EmptyState />}
  onEndReached={loadMore}
/>

// Form mode (with keyboard handling - Android only)
<OS_Wrapper
  enableKeyboardHandling
  keyboardScrollOffset={150}
  contentPaddingBottom={100}
  footerComponent={<SubmitButton />}
>
  <FormContent />
</OS_Wrapper>

🚀 Implementation Status

✅ Phase 1: Job Screens - COMPLETED (2026-04-06)

Files migrated: 8

Job List Screens (OS_Wrapper):

• ✅ screens/Job/ScreenBeranda.tsx - ViewWrapper → OS_Wrapper
• ✅ screens/Job/ScreenBeranda2.tsx - NewWrapper_V2 → OS_Wrapper
• ✅ screens/Job/ScreenArchive.tsx - ViewWrapper → OS_Wrapper
• ✅ screens/Job/ScreenArchive2.tsx - NewWrapper_V2 → OS_Wrapper
• ✅ screens/Job/MainViewStatus.tsx - ViewWrapper → OS_Wrapper
• ✅ screens/Job/MainViewStatus2.tsx - NewWrapper_V2 → OS_Wrapper

Job Form Screens (OS_Wrapper with keyboard handling):

• ✅ screens/Job/ScreenJobCreate.tsx - NewWrapper_V2 → OS_Wrapper + enableKeyboardHandling
• ✅ screens/Job/ScreenJobEdit.tsx - NewWrapper_V2 → OS_Wrapper + enableKeyboardHandling

Testing Status:

• ✅ TypeScript: No errors
• ✅ Build: Success
• ✅ iOS Testing: Complete ✅
• ✅ Android Testing: Complete ✅

Implementation Notes:

• Semua form screens menggunakan enableKeyboardHandling untuk keyboard auto-scroll di Android
• Semua list screens menggunakan pagination dengan onEndReached
• Floating button dan sticky header berfungsi dengan baik
• Footer component tetap di posisi bawah

⏳ Phase 2: Other User Screens (Priority: HIGH)

Profile Screens:

• screens/Profile/ScreenProfile.tsx
• screens/Profile/ScreenProfileEdit.tsx → pakai enableKeyboardHandling
• screens/Profile/ScreenProfileCreate.tsx → pakai enableKeyboardHandling

Forum/Discussion:

• screens/Forum/ScreenForum.tsx
• screens/Forum/ScreenForumDetail.tsx
• screens/Forum/ScreenForumCreate.tsx → pakai enableKeyboardHandling

Portfolio:

• screens/Portfolio/ScreenPortfolio.tsx
• screens/Portfolio/ScreenPortfolioCreate.tsx → pakai enableKeyboardHandling
• screens/Portfolio/ScreenPortfolioEdit.tsx → pakai enableKeyboardHandling

⏳ Phase 3: Admin Screens (Priority: MEDIUM)

Event Management:

• screens/Admin/Event/ScreenEventList.tsx
• screens/Admin/Event/ScreenEventCreate.tsx → pakai enableKeyboardHandling
• screens/Admin/Event/ScreenEventEdit.tsx → pakai enableKeyboardHandling

Voting Management:

• screens/Admin/Voting/ScreenVotingList.tsx
• screens/Admin/Voting/ScreenVotingCreate.tsx → pakai enableKeyboardHandling
• screens/Admin/Voting/ScreenVotingEdit.tsx → pakai enableKeyboardHandling

Donation Management:

• screens/Admin/Donation/ScreenDonationList.tsx
• screens/Admin/Donation/ScreenDonationCreate.tsx → pakai enableKeyboardHandling
• screens/Admin/Donation/ScreenDonationEdit.tsx → pakai enableKeyboardHandling

⏳ Phase 4: Other Screens (Priority: LOW)

• screens/Investasi/ - Investment screens
• screens/Kolaborasi/ - Collaboration screens
• Other user-facing screens

✅ Testing Checklist

Setiap screen yang sudah di-migrate, test:

iOS Testing

• UI tampil sesuai design
• Tabs berfungsi dengan baik
• ScrollView/FlatList scroll dengan smooth
• Keyboard tidak menutupi input (jika pakai enableKeyboardHandling)
• Footer muncul di posisi yang benar
• Pull to refresh berfungsi (jika ada)

Android Testing

• UI tampil sesuai design
• Tabs berfungsi dengan baik
• ScrollView/FlatList scroll dengan smooth
• Keyboard handling: auto scroll saat input focus (jika pakai enableKeyboardHandling)
• Footer muncul di posisi yang benar (tidak tertutup navigation bar)
• Pull to refresh berfungsi (jika ada)

Common Testing

• Background image muncul (jika withBackground={true})
• Sticky header berfungsi (jika ada headerComponent)
• Footer fixed di bottom (jika ada footerComponent)
• Floating button muncul (jika ada floatingButton)
• Loading skeleton muncul saat pagination
• Empty state muncul saat data kosong

📌 Notes

Usage Pattern:

Untuk List Screen:

<OS_Wrapper
  listData={pagination.listData}
  renderItem={renderItem}
  ListEmptyComponent={ListEmptyComponent}
  ListFooterComponent={ListFooterComponent}
  onEndReached={pagination.loadMore}
  refreshControl={
    <RefreshControl
      refreshing={pagination.refreshing}
      onRefresh={pagination.onRefresh}
    />
  }
/>

Untuk Static Screen:

<OS_Wrapper
  headerComponent={<HeaderSection />}
  footerComponent={<FooterSection />}
>
  <YourContent />
</OS_Wrapper>

Untuk Form Screen (dengan keyboard handling):

<OS_Wrapper
  enableKeyboardHandling
  keyboardScrollOffset={150}
  contentPaddingBottom={100}
  footerComponent={
    <BoxButtonOnFooter>
      <ButtonCustom onPress={handleSubmit}>Submit</ButtonCustom>
    </BoxButtonOnFooter>
  }
>
  <FormContent />
</OS_Wrapper>

Migration Pattern:

// OLD
import NewWrapper from "@/components/_ShareComponent/NewWrapper";

<NewWrapper
  listData={data}
  renderItem={renderItem}
  headerComponent={header}
  footerComponent={footer}
/>

// NEW
import { OS_Wrapper } from "@/components";

<OS_Wrapper
  listData={data}
  renderItem={renderItem}
  headerComponent={header}
  footerComponent={footer}
/>

// OLD (Form with keyboard handling)
import { NewWrapper_V2 } from "@/components/_ShareComponent/NewWrapper_V2";

<NewWrapper_V2
  enableKeyboardHandling
  keyboardScrollOffset={150}
>
  <FormContent />
</NewWrapper_V2>

// NEW (Unified API)
import { OS_Wrapper } from "@/components";

<OS_Wrapper
  enableKeyboardHandling
  keyboardScrollOffset={150}
>
  <FormContent />
</OS_Wrapper>

🐛 Troubleshooting

Issue: Tabs tidak muncul di Android

Solution: Pastikan tidak ada custom padding yang overriding default behavior. Jika masih bermasalah, cek apakah contentPadding atau contentPaddingBottom terlalu besar.

Issue: Keyboard menutupi input di Android

Solution: Pastikan pakai OS_Wrapper dengan enableKeyboardHandling={true}. Adjust keyboardScrollOffset jika perlu.

Issue: Footer terlalu jauh dari bottom

Solution: Kurangi contentPaddingBottom (default: 80). Untuk list screen tanpa navigation bar overlay, bisa set ke 0.

Issue: White space di bottom saat keyboard close (Android)

Solution: Ini sudah di-fix di AndroidWrapper. Pastikan screen pakai OS_Wrapper, bukan NewWrapper langsung.

📊 Progress Tracking

Phase	Total Files	Migrated	Testing	Status
Phase 1 (Job)	8	8	✅ Complete	✅ Complete
Phase 2 (User)	TBD	0	0	⏳ Pending
Phase 3 (Admin)	TBD	0	0	⏳ Pending
Phase 4 (Other)	TBD	0	0	⏳ Pending
Total	8+	8	8	100% (Phase 1)

🔄 Rollback Plan

Jika ada issue yang tidak bisa di-fix dalam 1 jam:

1. Revert perubahan di file yang bermasalah
2. Kembali ke NewWrapper/NewWrapper_V2
3. Dokumentasikan issue di CHANGE_LOG.md
4. Investigasi lebih lanjut dan coba lagi

---

Co-authored-by: Qwen-Coder qwen-coder@alibabacloud.com Created: 2026-04-06 Last Updated: 2026-04-06 Status: Phase 1 (Job Screens) Complete ✅ Next: Phase 2 - Other User Screens