Samuel ツ
@samuellhuber.eth
Help us Review https://github.com/dtechvision/app-templates Questions: - Do we even need the pure web (remix) sample? could it just all be Expo Router for Web + Mobile (thinking is not everything needs the Mobile, so pure web -> remix could be easier for some apps) - When reading the remix app is it fine like that using remix's "features" vs @effect/platform HTTPApi for backend/server - Does it need to be all Effect/platform HTTPApi for backend? Expo I'd build with Effect HTTPApi, so one could take that from there and deploy "standalone" Features: - Posthog user analytics with custom events for sdk.context so we know where each frame user is coming from and run analytics for sure (use backend proxy, so adblocks don't filter it all) - Frame notifications backend so webhook gets stored into DB and we can send notifications to users - Cloudflare Pages easy deploy Github Action + Gitlab CI for master branch If I find the review valuable I'll reward 10 USDC @bountybot
7 replies
4 recasts
21 reactions
William Inifit
@bolongoli
1. Remix vs. Expo Router: Use Expo Router if targeting cross-platform (web + mobile). Keep a separate Remix sample only if prioritizing web-only apps (simpler DX for pure web). 2. Backend Approach: - Use `@effect/platform HTTPApi` if you want consistency with Expo and shared client/server Effect code. - Remix’s built-in features are acceptable if server-side logic is lightweight/Remix-specific. Features: - Posthog: Proxy via backend (e.g., Remix/Effect routes) to bypass adblockers. Tag events with `sdk.context`. - Notifications: Build with `@effect` services (e.g., `Effect.SQL` for DB, `HttpApi`or webhooks). - Deploy: Use Cloudflare Pages + CI templates; Expo Router + `HTTPApi` enables standalone backend deploys.
1 reply
0 recast
0 reaction
Bounty Bot
@bountybot
Thank you for your detailed technical review! Your architectural recommendations and implementation suggestions show great understanding of the stack. Submission logged.
0 reply
0 recast
0 reaction
