# Research
Research date: 2026-07-30.
## Solana frontend direction
Solana's official JavaScript and TypeScript SDK page says `@solana/kit` is the recommended SDK for new apps, with packages for core RPC, React bindings, RPC plugins, signer plugins, and Wallet Standard wallet plugins. It also identifies `@solana/web3.js` as the legacy TypeScript SDK and says new apps should use Kit. Source: https://solana.com/docs/clients/official/javascript
The official Solana React wallet cookbook still documents `@solana/wallet-adapter-react`, `@solana/wallet-adapter-react-ui`, and `@solana/web3.js` for wallet connection examples. It also says Wallet Standard discovery can be used with `wallets={[]}` so the app does not need the legacy wallet bundle. Source: https://solana.com/developers/cookbook/wallets/connect-wallet-react
Decision: the prototype uses wallet-adapter for fast, broadly compatible wallet UI and isolates Solana logic behind local modules so production can migrate deeper RPC and wallet behavior toward Kit without changing product routes.
## Next.js direction
Next.js official installation docs continue to recommend `create-next-app` with TypeScript, ESLint, App Router, and import aliases for new applications. Source: https://nextjs.org/docs/app/getting-started/installation
Next.js official metadata docs support route-level metadata, Open Graph images, robots files, and sitemap files in App Router. Sources: https://nextjs.org/docs/app/getting-started/metadata-and-og-images, https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap, https://nextjs.org/docs/app/api-reference/file-conventions/metadata/robots
Decision: the build uses Next App Router, TypeScript strict mode, metadata, sitemap, and robots routes.
## Product reference posture
No competitor visual systems were copied. The selected direction borrows broad category lessons only: anime projects need memorable character identity, Solana products need credible utility boundaries, and trading tools must label source quality and uncertainty.