Development of personalized homepage for 'Mausam' mobile application:

The receipts 🧾

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

1. Exhibit A

   Pollen count is listed for the health-conscious profile and India has no operational pollen monitoring network, so that data simply does not exist to display

2. It gets worse

   A configurable widget dashboard is a low-ceiling product and a panel will see a rearranging homepage rather than anything technically substantial

3. Still reading?

   The description is only a persona list with no background or expected solution, so what the sponsor actually wants beyond the widget arrangement is left unstated

4. And the finisher

   Personalising the homepage risks burying a warning under someone's tide chart, so the priority override is a requirement rather than a nice touch

The damage report 📉

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

• Feasibility

  4/5

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

  Most of what the eight profiles need is genuinely available — forecast variables, air quality station data, UV, tide and sea state, and satellite soil moisture are all obtainable — with the notable exception of pollen counts, since India has no operational pollen monitoring network to draw from.

• Innovation scope

  3/5

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

  The eight user profiles and the variables to show each are dictated, but nothing says how personalisation is chosen, whether profiles are declared or learned, or how the derived indices are computed, and those derivations are where the real design work sits.

• Clarity

  3/5

  Clear enough to start, vague enough to drift. Write the scope down and stop reinterpreting it weekly.

  Unusually concrete about what each profile should see, but the description consists of nothing except that persona list — there is no background, no expected solution, no statement of how the homepage assembles, and no mention of the constraints of the existing application it is meant to slot into.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  This is a personalisation layer for an app that already exists, and a configurable widget dashboard has a very low ceiling — the derived indices are the only place real work can go, and most teams will display raw values and call it personalisation.

• Effort

  Medium

  Manageable — which means the bar for polish just went up, because you have no excuse left.

  A widget library, a profile model, a layout engine and a set of derived index calculations over a weather backend is a contained build with no technically deep component, which is unusual on this portal.

• Demo-ability

  Easy

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

  Toggling between profiles and watching the same forecast reassemble into different cards is immediate and self-explanatory, and the warning override gives you a second clean moment.

• 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 160–360 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 eight personas and their variables are enumerated, so requirements ambiguity is zero and you can go straight to building
• The derived indices are the real opportunity — best running hours and a comfort index computed from temperature, humidity, wind and radiation are genuine calculations, and a team that derives them properly rather than displaying raw values has something to show
• The scope is genuinely modest by the standards of this portal, so a small team can finish and polish rather than stub