Skip to content
SIH Buddyby Ganeev Singh
Dev

🔥 Roast My Pick · SIH26003

AI-Based Cognitive Gaming and Memory Assistance Platform for Elderly Dementia Patients in North Eastern Region (NER)

Ministry of Development of North Eastern Region (MDoNER)

Mild17/100

Good pick. Genuinely. Now sit down, because the judges are going to try anyway — and this is what they will try.

Strong pick. The safest high-ceiling pick in the MDoNER block, but the description asks for five components rather than a games app, so budget for the reminder and caregiver halves from the start. Roughly 95–220 teams are expected to go here.

The receipts

Every red flag on this statement, in full. These are the four places it bites.

  1. Exhibit A

    Evidence that brain-training slows dementia progression is genuinely contested, and a clinician judge will ask what your games are grounded in — have MoCA or ADAS-Cog domain mapping ready

  2. It gets worse

    Elderly UI is a real discipline most student teams fail: small fonts, low contrast, swipe gestures and timers are all disqualifying for this user

  3. Still reading?

    The NER framing plus the multilingual requirement implies Assamese, Manipuri, Khasi and Mizo support, which is substantial content work teams discover late

  4. And the finisher

    The description asks for games, reminders, voice, offline sync and caregiver analytics — that is five components, and a team that polishes the games and stubs the rest has answered a fraction of the statement

The damage report

Every score this statement earned, and what each one actually costs you.

  • Feasibility

    5/5

    Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

    There is no model to train, no dataset to source and no hardware to buy — the description asks only for adaptive game logic, reminders, a voice interface and a dashboard, all of which are application-layer work.

  • Innovation scope

    3/5

    Mildly interesting. The novelty will not carry the room; the build has to.

    The description prescribes the game domains, the reminder categories, the offline requirement and the caregiver dashboard, so the shape is largely fixed and your room is confined to the adaptive difficulty policy and the cultural localisation.

  • Clarity

    5/5

    The ask is unambiguous, which quietly removes your favourite excuse.

    The description enumerates the cognitive domains, the reminder types, the multilingual and offline requirements and the caregiver monitoring separately, leaving almost nothing about the deliverable to interpretation.

  • Acceptance potential

    5/5

    Strong footing before you have written a line. Try not to waste it.

    A clear hidden gem — pure software with zero data risk, a hands-on demo, obvious human impact, and the portal has filed it under Space Technology, so teams browsing MedTech or Smart Education will never find it.

  • Effort

    Heavy

    Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

    Four game domains, a reminder system, a voice-enabled multilingual interface, offline sync and a caregiver analytics dashboard is a lot of separate surface area even though no single piece is technically deep.

  • Demo-ability

    Easy

    Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

    A judge can pick up the tablet and play the game themselves within thirty seconds, which is the strongest demo format available and almost no other PS in this ministry offers it.

  • Data

    None supplied

    No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

    Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen

Somewhere around 95–220 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives

The ground worth standing on when the questions start.

  • The theme mislabelling is a genuine competitive advantage — anyone filtering for MedTech or Smart Education will not see this PS at all
  • The description explicitly requires offline functionality, which means the rural connectivity question every judge asks is already answered by the spec rather than by you improvising
  • Zero dataset dependency, so the project cannot collapse because a data source fell through

Nothing here is fatal. It is just the list of places this statement pushes back, and you now get to push there first.

Full analysis ↗Roast another

The framing is a joke. The findings are not — they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.