Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 2
Generated: 21:42:32
**How many testers?** I think it's worth to do incremental test sessions to not waste people's time. I would go from groups of 3, to 5 and try to find a limit where the app gets crazy or terribly slow. I didn't implemented any limitations on that sense on purpose for this mather. **How many devices?** The best way to test is 1 device per person. **What types?** Samiz work only on android devices. So far it has been tested in some new and old phones and I barely received bad feedback different from IU misfits caused by small screens. Would be great to spot a table of incompatibilities I can work with. Samiz will probably be necessary in places where people won't have the newest phones in the market. **How much time for each test?** Good question. Taking into consideration what I said about not implementing limitations I would probably try to figure out if the app crashes for memory lack at some point. Other thab that people just need to use nostr as usual. **What distance?** Bluetooth is supposed to have a 100m range in open field. I would say maybe 50m is a more conservative maximum but who knows, also a good thing to test. **Do they need to do a in person meet up?** Definitively they need to meet in person at some point to test the mesh. But having notes created at home and see how they spread would be cool. Remember right now Samiz only synchronize notes created up to 1 hour previous the session has been started but they stay available as long you don't close the same session Another hints: 1. Because the setup is kind of long I would recommend people to make sure their Samiz setup is ready while at home. The app has a view with a step by step tutorial but I'll be happy to support at any time. 2. If any problem appears an screenshot of the logs view will definitively help. It is supposed to catch and display errors too.
2025-06-18 20:30:19 from 1 relay(s) ↑ Parent 1 replies ↓
Login to reply

Replies (2)

OK. So let's design a test framework that looks something like: Test 1: -3 testers -setup at home individual -install test -report bugs -meetup for offline, then online test -test distances offline -Approx time: 2hrs -Budget 100k sats (zapped to testers after completion) Test 2: -5 testers -same as before, but more people, more scenarios -Approx time: 2hrs -Budget 200k sats (zapped to testers after completion) Test 3: -5 testers ... ... -Approx time: 2hrs -Budget 200k sats (zapped to testers after completion) Test 4: -10 testers ... ... -Approx time: 2hrs -Budget 400k sats (zapped to testers after completion) ...This is just a rough approximation. You know better what needs to be tested. Please correct me or add detail where necessary.
2025-06-18 21:15:50 from 1 relay(s) ↑ Parent 2 replies ↓ Reply
Sounds good! The publication to the internet is still not implemented (yet you can recover it with Amethyst and broadcast it manually) so there is really nothing to test online.
2025-06-18 23:47:36 from 1 relay(s) ↑ Parent Reply