feat: `GET /cards` endpoint has no pagination — a user with 50+ cards receives all cards in a single response, causing excessive payload sizes and slow mobile load times

[divyanshim27]

🚀 Problem Statement

The README documents GET / as: "List all cards for the authenticated user." The current endpoint returns ALL cards in a single array with no limit, offset, or cursor-based pagination.

While the typical user may have 3-5 Context Cards (Professional, Hackathon, Community), the README documents: "Context Cards — Different cards for different situations." Power users can create many cards, and there is no enforced card limit documented in the API.

More importantly, each card response includes links[] — an array of all platform URLs. A user with 20 cards × 15 links each = 300 link objects returned on every single GET /cards call. This is significant unnecessary payload for a mobile app (React Native) on a cellular connection.

Proposed Fix

Add page and limit query parameters with sensible defaults:

// apps/backend/src/routes/cards.ts — update GET / handler

const schema = z.object({
  page:  z.coerce.number().int().min(1).default(1),
  limit: z.coerce.number().int().min(1).max(50).default(20),
});

fastify.get('/', { preHandler: [authenticate] }, async (request, reply) => {
  const { page, limit } = schema.parse(request.query);
  const skip = (page - 1) * limit;

  const [cards, total] = await Promise.all([
    prisma.card.findMany({
      where: { userId: request.user.id },
      include: { links: true },
      orderBy: [{ isDefault: 'desc' }, { createdAt: 'desc' }],
      skip,
      take: limit,
    }),
    prisma.card.count({ where: { userId: request.user.id } }),
  ]);

  return reply.send({
    data: cards,
    pagination: {
      page,
      limit,
      total,
      totalPages: Math.ceil(total / limit),
      hasNextPage: page * limit < total,
    },
  });
});

Update the README API docs to document the new query parameters and response shape.

Files to Modify

File	Change
apps/backend/src/routes/cards.ts	Add page/limit query params, paginated Prisma query, pagination response field
README.md	Document pagination in the GET / endpoint section
apps/mobile/ (cards list screen)	Implement infinite scroll / load more using hasNextPage

Suggested labels: enhancement, backend, performance, level: intermediate

I would like to work on this. Could you please assign it to me?

[github-actions]

Hi @divyanshim27,

Thanks for opening this issue.

Please reply with one of the following areas so the issue can be routed to the appropriate team member:

- /backend
- /web
- /mobile
- /devops

Once an area is selected, the corresponding label will be added automatically.

[divyanshim27]

Hey @maintainers,
Please assign it to me under GSSoC 2026.
/claim /assign /claim-assignment

[Harxhit]

@divyanshim27 I have assigned this issue to you.

[github-actions]

Hey @ShantKhatri (Project Admin) and @Harxhit (Maintainer),

This issue (previously assigned to @divyanshim27) has been automatically unassigned because no linked pull request was found within 5 days of assignment.

If work is in progress, please open and link a PR to keep the assignment active.