Consider monetization opportunities

[nizarmah]

If we can monetize an alternative solution that's closely related, it can fund the R&D of Igatha.

Possible solutions:

1. Safety for factories, construction sites, oil rigs, off-sites and mines (Sakthimm)
2. Safety and wellness system for elderly (daveguy)
3. ...

Acceptance criteria:

1. Look into existing suggestions
2. Research other opportunities
3. Decide on one or two paths to take

[nizarmah]

We decided we can make more impact by working on the safety tech, and licensing it to phone manufacturers.

It's hard to convince people to eat their vegetables. And it'll be too late when people realize they should've eaten their vegetables.

So, phone manufacturers would take the role of guardians/parents, preparing people for the worst.

We didn't consider other solutions, because the more we can focus on one, the better job we'll do with it. And as we move, we can learn and identify new options.

Check https://igatha.io/partners (Thu Apr 17, 2025 — use wayback machine is changes happen)

[nizarmah]

Re-opening.

Startups get rolling with early adopters, which huge slow-moving phone makers aren't.
— pg

That was the best advice I've gotten yet.
Our next release with phone makers would be next year.

---

1. Where can we re-iterate fast?
2. Who would early adopt this?

Then, we can think of monetization again.

[nizarmah]

Current early adopters were from HackerNews — https://news.ycombinator.com/item?id=43551767.

Where are our users from?

1. Most of our users are from: United States (~137), Germany (~78), Iran (~38), Morocco (~21).
2. No users in Lebanon, even though it was to help rescue people under bombed buildings.

What's stopping me from selling to users?

1. People in third world countries who need it most can't pay online for it.

Yet, most of my users are from the US and Germany...

Is it used for a different purpose?

1. It's hard to reach out to people who installed my app.

Let's start here...

1. Add a form for users to submit their contact info.
2. Reach out to users.

---

There has to be a form of monetization here to fund development.

1. On one side, charging users a very low fast.
2. On the other side, targeting businesses.

The problem with charging users:

1. Not everyone can pay, even if it's only a dollar.
2. Slow iteration because emergencies aren't that often. (TODO: Research how often they happen)

The problem with charging businesses:

1. Use cases don't transfer directly to users.
2. Faster iteration but more competition.

In the meantime, I'll keep thinking of this. But first we really need to talk to some users.

[nizarmah]

The best way to iterate is if my users use the product frequently, unlike the current flare-gu.

If we can understand why our current users use the app, then maybe we can understand how we can extend it with something to be used more common.

A great example is: Apple's Health app, which I personally use daily. 🤔

[nizarmah]

Here's the data we have today (Sat 19 Apr).

Takeaways:

1. People love it and want it on their watches.
2. We have a good conversion rate from page view to install.
3. No real in-store discoverability yet — they're only referred by links.
4. Growth has stopped — very few new installs.

---

From the Play Store:

1. Reviews and ratings:
   1. Rating: 5
   2. Users: 2
   3. Ratings with reviews: 1
      1. Rating: 5
         1. Title: "fantastic creation"
         2. Date: "Apr 2, 2025"
2. Downloads:
   1. Total: 165
   2. By territory (top 4):
      1. Iran: 39
      2. United States: 28
      3. Morocco: 20
      4. Germany: 13
3. Devices and OS:
   1. Mainly samsung.
   2. Android 13, 14, and 15.
4. Store listing performance:
   1. Store listing visitors: 660
   2. Store listing acquisitions: 204
   3. Store listing conversion rate: 30.91%
5. Acquisition:
   1. Google Play explore: 23
   2. Total: 210

---

From the App Store:

1. Reviews and ratings:
   1. Rating: 5
   2. Users: 1
   3. Ratings with reviews: 1
      1. Rating: 5
         1. Title: "Love the concept for the app!!!"
         2. Message: "It's one of those things which you should have, in case of emergency you'll be able to use it - not as much, hopefully like the torch but great work. Personal thoughts - would also be great to have this adapted to watchOS."
         3. Date: "Apr 2, 2025"
2. Downloads:
   1. Total: 238
   2. By territory (top 5):
      1. United States: 107
      2. Germany: 62
      3. Russia: 10
      4. Switzerland: 8
      5. France: 7
3. Devices:
   1. iPhone: 96.2% (229)
   2. iPad: 3.8% (9)
4. Store listing performance:
   1. Impressions: 897 (+272%)
   2. Product Page Views: 591 (+3.84K%)
   3. Conversion Rate: 38.3% (+2.03K% Daily Average)
5. Acquisition:
   1. Web Referrer: 42% (100)
   2. App Referrer: 34.5% (82)
   3. App Store Search: 18.5% (44)
   4. App Store Browse: 5% (12)

[nizarmah]

Okay, so as next step, I'm going to add a user feedback form — a very basic one.

This will help us understand who our early adopters are. Then, we can understand what additional features could be monetized.

To clarify though, I will not monetize a life-saving feature.

[nizarmah]

Okay, so to collect user feedback we've added:

1. ios: Add user feedback form #27
2. android: Add user feedback form #28

Now what's left is: sending a notification to ask users to submit feedback.
I'm wondering if it should be dynamic, using something like Firebase. I've decided to keep it simple.