So, the marketing for a Nostr app would include thoughts like:
Will we expect people to pay for using the app? If so, using what model? If not, how will we pay for the app?
Should we list the app on the Zapstore and Google Play, or is it only going to be offered on Obtanium or GitHub as a binary?
Can the users expect 24-hour turnaround time for issues or is it "every user for themselves" and we address issues at our own leisure?
What functions should our app have? What should we fold in from other projects and what should we build ourselves? Who do we expect to use this app and what are features that they would expect or be "wowed" by? What features would repel them and lead to them bad-mouthing us to their friends?
Should we use our personal npubs to announce releases, or have a company npub?
Where do we store the app? How many different locations should we choose and what git servers should run there? Which of those locations do we make public, and where?
How large and performant should our app be and what sort of infrastructure/hardware will it be run on?
Where will the people live, who use our app? What currencies would they expect us to offer, for transactions or denominations? How do they expect items on the app to be arranged, for easy clicking and reading?
Should we consider accessibility issues? What login options should we offer?
What should be in our app documentation and where will we place that documentation? How will that documentation be formatted?
Etc. Etc. Etc.
Laeserin / Laeserin (Silberengel)
npub1m4…jc2jl
2024-09-04 08:01:40
in reply to nevent1q…z8xt
Author Public Key
npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jlPublished at
2024-09-04 08:01:40Event JSON
{
"id": "b262c2801a0ccd2e112f5186a71262d737344ddfb88b6fbf67fe5d256b0dd0e0",
"pubkey": "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"created_at": 1725436900,
"kind": 1,
"tags": [
[
"e",
"fdcee89d5521ac0c9c21ca06dfcf7430cb33543eb067590edd869878a096bc43",
"",
"root"
],
[
"e",
"fe6fb9adf02c2b8a47cd2eb172fbbbaa650c5ced47343a4b6fbeb6ea63477cab",
"",
"reply"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"fc994dc4d95efe62e5ed1c84542f40a1f513e2c4bf9953003aa4dfe8ad649b11"
],
[
"p",
"a96a35a224402b8075c4da20f0477896afcc3395b6fad63e30a648a8222a6a69"
]
],
"content": "So, the marketing for a Nostr app would include thoughts like:\n\nWill we expect people to pay for using the app? If so, using what model? If not, how will we pay for the app?\n\nShould we list the app on the Zapstore and Google Play, or is it only going to be offered on Obtanium or GitHub as a binary?\n\nCan the users expect 24-hour turnaround time for issues or is it \"every user for themselves\" and we address issues at our own leisure?\n\nWhat functions should our app have? What should we fold in from other projects and what should we build ourselves? Who do we expect to use this app and what are features that they would expect or be \"wowed\" by? What features would repel them and lead to them bad-mouthing us to their friends?\n\nShould we use our personal npubs to announce releases, or have a company npub?\n\nWhere do we store the app? How many different locations should we choose and what git servers should run there? Which of those locations do we make public, and where?\n\nHow large and performant should our app be and what sort of infrastructure/hardware will it be run on?\n\nWhere will the people live, who use our app? What currencies would they expect us to offer, for transactions or denominations? How do they expect items on the app to be arranged, for easy clicking and reading?\n\nShould we consider accessibility issues? What login options should we offer?\n\nWhat should be in our app documentation and where will we place that documentation? How will that documentation be formatted?\n\nEtc. Etc. Etc.",
"sig": "1638413f731497d1a518f39622753c5fdf131b7935d610e8bf3a09a63b4c75c88d94a8bf8ae76d809c32e8847e0c39241b23b6c9b138c40e9e96284c1b652ca4"
}