--- title: "Parking lot meetup card" date: "2026-07-12" canonical: "https://raytally.com/en/ideas/2026-07-12-great-lakes-crossing-shooting/" generator: "RayTally · dev-prompt-v4" signal: query: "great lakes crossing shooting" observed_at: "2026-07-12T02:46:56.753Z" window_hours: 168 sources: - url: "https://www.cbsnews.com/detroit/news/police-great-lakes-crossing-shopping-mall-michigan/" boundary: "Published at 2026-07-11." - url: "https://www.clickondetroit.com/news/local/2026/07/11/1-suspect-in-custody-after-2-shot-at-great-lakes-crossing-in-auburn-hills/" boundary: "Published at 2026-07-11." - url: "https://support.google.com/android/answer/9319337?hl=en" boundary: "No publication timestamp is present in the source record." - url: "https://www.facebook.com/help/1302988673145783/" boundary: "No publication timestamp is present in the source record." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-12-great-lakes-crossing-shooting/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Parking lot meetup card Helps people leaving a shopping center create a low-bandwidth meetup card that quickly tells family where they are and whether they are safe. ## Product concept People inside Great Lakes Crossing who evacuate to the parking lot can open the page and select the store they just left and their parking area. The tool generates a minimal meetup card with clothing, group size, vehicle location, remaining phone battery, and statuses such as "safe but unable to call." Users send the card to family by text, so relatives do not need to keep calling and can wait near the right prominent landmark. The page can also combine multiple family members' cards into one "contacted / still looking" list, which helps prevent group-chat messages from getting buried. It does not follow on-site rumors or play videos; it addresses the confusion in the first few minutes after an incident at a large shopping center, when people are already outside but cannot find one another. ## Why now (backed by facts) On July 11, 2026, a shooting occurred inside Great Lakes Crossing Outlets. Two people were injured, and one suspect was detained. As of the trend snapshot on July 12, 2026, "great lakes crossing shooting" had approximately 10,000+ searches in the United States over nearly 168 hours, with an increase of approximately 400%. This suggests that, shortly after the incident, many families were actively seeking information about the shopping center and people’s safety. A low-bandwidth meetup card that can be forwarded directly by text fits that need. ## Direction (model inference, not independently verified) Target user: People who have just evacuated a large shopping center to the parking lot and can send a text but cannot call family right away will open it. Recipients use the card to confirm the person’s status, parking area, and agreed meetup landmark. Minimal entry point: Start with a no-login mobile web page: select the store exit and parking area, enter clothing, group size, vehicle location, battery level, and contact status, then generate a meetup card that can be sent directly by text. Do not build live maps or on-site messages initially. The strongest case against: The strongest case against this is that reach, not functionality, is the main problem: after an emergency begins, most people will not search for a meetup page they have never heard of. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Create searchable parking-area and prominent-landmark template pages for specific shopping centers such as Great Lakes Crossing, then give the QR code to local parent groups, community emergency organizations, and shopping center tenants for testing. People searching for the shopping center name, parking map, or meetup point can enter the relevant page directly. ## Competitors & gaps (model inference) - Google Personal Safety: Google’s approach focuses on continuously sharing live location and battery level. It requires a supported Android device, preset emergency contacts, and an internet connection. The meetup card can be sent by text across devices and describes the on-site location using the store, parking area, and prominent landmark. - Facebook Safety Check: Facebook Safety Check lets people mark themselves as safe publicly or semi-publicly on a specific crisis page, but it does not handle parking areas, vehicle locations, group size, or a family member meetup checklist. ## How it makes money (model inference) Charge shopping center operators an annual fee for branded deployment; keep it free for the public during emergencies. ## Trend background Theme: Great Lakes Crossing shooting Trigger query (original English): great lakes crossing shooting Approx. search volume: 10000+ (approximate) Approx. increase: +400% (approximate) The trend data is a historical snapshot from the moment it was captured; volume and increase are approximate and only explain “why now.” Do not write them into product copy as precise market numbers. ## Sources - 2 injured, 1 in custody, after shooting at Great Lakes Crossing Outlet, deputies say (https://www.cbsnews.com/detroit/news/police-great-lakes-crossing-shopping-mall-michigan/) - 1 suspect in custody after 2 shot at Great Lakes Crossing in Auburn Hills (https://www.clickondetroit.com/news/local/2026/07/11/1-suspect-in-custody-after-2-shot-at-great-lakes-crossing-in-auburn-hills/) - Get help during an emergency with your Android phone (https://support.google.com/android/answer/9319337?hl=en) - Find a Safety Check on Facebook (https://www.facebook.com/help/1302988673145783/) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.