Amazing feedback Niel, thank you!
The logo does need a lot of work indeed 😉
The upper navbar has space reserved for at least a couple more icons (wallets, relays), and the bottom one too (tab switcher, tab reactions). I honestly really want to have just a single navbar, but can't come up with a good way to achieve that. Maybe if we discover that most of those buttons aren't really used often then we'd fold them...
The graph-based app recommendations are definitely coming, right now the density of the app usage graph is just not good enough to make anything interesting.
I also have doubts about the idea that people really do need advanced app categorization. NIP-89 should allow us to reduce the need for app categorization - you'd browse content and discover apps contextually when you're viewing/creating/editing some event kind. At least that's the theory.
You're asking a great question of 'what's the focus of this thing? what's the problem it's solving?' I honestly don't have much of a clear answer. Just like nostr itself, it seems to try to solve too many interconnected problems. We'll try to figure things out as we go, so thank you for your perspective, noted!
We tried to avoid focusing on the duties of apps - the content section is very light and is just an invitation to dive into one of the apps. We could just fill the whole screen with app icons, but that's so boring and identical to your existing static smartphone screen... Nostr's data portability is one of the key features, allowing you to have a dashboard of most interesting things happening across the apps. What do you think?
brugeman
npub1xd…mntxy
2023-08-27 13:21:45
in reply to nevent1q…z3wa
Author Public Key
npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxyPublished at
2023-08-27 13:21:45Event JSON
{
"id": "0ec4465bb4e2a5338c718bc78039472f798e845aa4e856040168082d3910eca4",
"pubkey": "3356de61b39647931ce8b2140b2bab837e0810c0ef515bbe92de0248040b8bdd",
"created_at": 1693142505,
"kind": 1,
"tags": [
[
"e",
"edbdf2c84399d1ffc0b2ab66a2bb54e5dbbc19b152b61044014ba6d002ca8fa5",
"",
"root"
],
[
"e",
"f2b7ab666e504f08540b7a75ece9d87f8c89764cd39e6933428aaa3834fce8c5",
"wss://nos.lol/",
"reply"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
]
],
"content": "Amazing feedback Niel, thank you!\n\nThe logo does need a lot of work indeed 😉 \n\nThe upper navbar has space reserved for at least a couple more icons (wallets, relays), and the bottom one too (tab switcher, tab reactions). I honestly really want to have just a single navbar, but can't come up with a good way to achieve that. Maybe if we discover that most of those buttons aren't really used often then we'd fold them...\n\nThe graph-based app recommendations are definitely coming, right now the density of the app usage graph is just not good enough to make anything interesting. \n\nI also have doubts about the idea that people really do need advanced app categorization. NIP-89 should allow us to reduce the need for app categorization - you'd browse content and discover apps contextually when you're viewing/creating/editing some event kind. At least that's the theory. \n\nYou're asking a great question of 'what's the focus of this thing? what's the problem it's solving?' I honestly don't have much of a clear answer. Just like nostr itself, it seems to try to solve too many interconnected problems. We'll try to figure things out as we go, so thank you for your perspective, noted!\n\nWe tried to avoid focusing on the duties of apps - the content section is very light and is just an invitation to dive into one of the apps. We could just fill the whole screen with app icons, but that's so boring and identical to your existing static smartphone screen... Nostr's data portability is one of the key features, allowing you to have a dashboard of most interesting things happening across the apps. What do you think?\n",
"sig": "422adb32462c1e79872e06c52166b7457adcf23e2787bf35a905d90b8d1ba25813b346672d051188aa738ff8b6650da0603f21f7e44b1b5437ca77c9634da62a"
}