Samuel ツ pfp
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
2 recasts
13 reactions
kenanie.base.eth pfp
kenanie.base.eth
@kenanie.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
kenanie.base.eth pfp
kenanie.base.eth
@kenanie.eth
PostHog user analytics should definitely use a backend proxy to prevent ad blockers from filtering events. Storing `sdk.context` for tracking frame origins is a good approach. The frame notifications backend should store webhooks in a database and send user notifications; if you need scalability, consider Redis pub/sub or Kafka. Cloudflare Pages deployment via GitHub Actions and GitLab CI is a solid choice, especially for Remix or static web apps.
1 reply
0 recast
0 reaction