https://github.com/sixelasacul/tft-double-up-companion

A simple, real time companion app for double up games. Built with TanStack Start, Ably, and Neobrutalism.
https://github.com/sixelasacul/tft-double-up-companion

ably community-dragon neobrutalism react shadcn tailwindcss tanstack-start teamfight-tactics websocket

Last synced: 6 days ago
JSON representation

A simple, real time companion app for double up games. Built with TanStack Start, Ably, and Neobrutalism.

• Host: GitHub
• URL: https://github.com/sixelasacul/tft-double-up-companion
• Owner: sixelasacul
• License: gpl-3.0
• Created: 2025-04-15T14:16:20.000Z (10 days ago)
• Default Branch: main
• Last Pushed: 2025-04-15T15:39:43.000Z (10 days ago)
• Last Synced: 2025-04-15T15:45:27.232Z (10 days ago)
• Topics: ably, community-dragon, neobrutalism, react, shadcn, tailwindcss, tanstack-start, teamfight-tactics, websocket
• Language: TypeScript
• Homepage: https://tft-double-up-companion.vercel.app
• Size: 0 Bytes
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# TFT Double up companion

A simple, efficient website to share and keep track in real time of champions you and your partner are looking for during Team Fight Tactics Double up games. Especially useful for people that have difficulties memorizing what others are looking for while still playing, or when playing with more people in voice chat than your partner.

Built with:

- [Ably](https://ably.com/) for web sockets

- [CommunityDragon](https://www.communitydragon.org/) for the game assets

- [TanStack Start](https://tanstack.com/start/latest) for the [React](https://react.dev/) framework

- [Neobrutalism](https://www.neobrutalism.dev/) for an opinionated style using [TailwindCSS](https://tailwindcss.com/) and [ShadCN](https://ui.shadcn.com/) registry

- [Vercel](https://vercel.com) for the deployment platform

## Notes

- should use better auth and have anonymous login to have some rate-limiting? probably not needed for now

- since I can't use Ably Realtime in SSR, is Start really needed? I could just deploy a function wherever I can

  - downside of this is that the function will depend on which hosting solution I use

- how the search should behave depending on the filters? and should we filter this way?

- what about SSE using TS Start instead of WebSockets using Ably? would need some kind of history too

## TODO

- eslint, prettier, lint-staged

- drag'n'drop (dnd-kit) for

  - champion priority

  - from grid to list

- larger champion list item

- champion grid selected style