Samuel ツ on Warpcast

Samuel ツ pfp

@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

Bounty Bot pfp

Your bounty deadline just passed (2 week default unless specified). If you'd like to edit the bounty amount or deadline, please update through the bounty frame "admin" button If the bounty was completed, please update through the "admin" button

0 reply

0 recast

0 reaction

Bounty Bot pfp

Confirmed! On your bounty page, you can pay users and view their bounty completion history Frame buttons - Admin: manage bounty status (in progress, complete), edit amount and deadline - Boost: get more attention on your bounty 🤖 commands - @bountybot cancel - @bountybot in progress - @bountybot complete (optional: tag winners) - @bountybot shoutout (optional: tag winner and write a positive review)

0 reply

0 recast

0 reaction

dylan pfp

on the first part expo router is solid enough that you can prolly do it all there now, will look a bit into the rest later!

1 reply

0 recast

5 reactions

ren.eth pfp

1.I personally think retaining the remix sample provides more flexibility for developers and also I feel using remix offers a more optimized stack for applications and also better backend logic interaction 2.According to what I checked using remix is just fine as it really simplifies development adhering to remix's conventions , also there is no really any specific requirement that specifies the need for HTTPApi 3. the repo's main focus is providing production grade templates with backend so integrating @effect/platform HTTPApi will definitely offer a consistent functional programming model across both web and mobile but it is not a necessity , using remix's inbuilt might suffice because of the native backend handling and server-side executions it provides

1 reply

0 recast

0 reaction

deeghost.base.🎩 pfp

deeghost.base.🎩

This is what I think 1. Remix vs. Expo Router • If everything needs web and mobile, Expo Router is better. • If some apps are web-only, Remix makes sense for simplicity. 2. Remix Features vs. @effect/platform HTTPApi • Remix’s built-in backend features are fine for most cases. • If you need strong type safety and functional programming, @effect/platform HTTPApi is a solid choice. 3. Effect HTTPApi for Backend? • Not required, but useful for consistency if deploying standalone Expo backends. Feature Implementation • PostHog Analytics → Use a backend proxy to bypass ad blockers. • Frame Notifications Backend → Store webhooks in a DB for user notifications. • Cloudflare Pages Deployment → Automate with GitHub Actions/GitLab CI. Would you like a deeper dive into any part?

1 reply

0 recast

0 reaction

William Inifit pfp

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

kenanie.base.eth pfp

kenanie.base.eth

You don’t strictly need the Remix sample if Expo Router can cover both web and mobile, but keeping Remix is useful for web-only apps where developers don’t need React Native. Some apps might be simpler to build without Expo, and Remix’s SSR capabilities make it a better fit for certain projects. The Remix app is fine as it is, using Remix’s native features like loaders and actions. If the backend logic is simple, this approach is sufficient. However, @effect/platform HTTPApi offers better modularity and reusability, so if scalability is a concern, moving backend logic to Effect makes sense. Not everything needs to be Effect/platform HTTPApi. For Expo, it makes sense to build with Effect HTTPApi so that backend logic can be deployed as a standalone service. For Remix, it depends on complexity—small apps can stay within Remix’s built-in features, but anything requiring more structured backend logic benefits from using Effect. check the next reply (exhausted my characters)

1 reply

0 recast

0 reaction