I was excited see what this could do, but the moment I saw it was a one day trial, I was so turned off that I didn't even bother wasting my time even looking into it and just removed it.
If you want people to invest time investigating your product to see if it's a good fit, don't rush them. I know you are probably eager to turn this into a profitable product, but this is not how to approach people like me if you want to see any sort of return.
Maybe make a lite version that is free and make your paid option have all the extra bells and whistles in it, but please, don't do this.
Apart from the obvious question of why you didn't opt to open source the tool :), I'm genuinely curious about how you approached development.
How did you decide for this feature A: "I'll just spawn child processes and read the output of `x-y-z` and `a-b-c` CLI tools, while for feature B: "I'll drop-down to BSD sockets"? Perhaps you have a performance budget: if using the Apple-provided CLI utilities are not fast enough then you drop down to writing BSD sockets?
So, I struggled with that route so much. I've benefited from open source software throughout my entire life (and have contributed to it as well), and I am truly indebted to it. It is my goal in the future to make this open source, but for now, frankly, the money helps set the time aside needed to make this better. Again, I will revisit this once I hit a goal I have in mind.
So yes, performance budget was a key factor. Some CLI tools provide standard, predictable answers in a set amount of time. Others are all over the place on answers and time. Some commands have options to set timeout, size, syn options, and such, while others do not. I have a few commands that are on my short list to replace with custom code - especially around mDNS.
I think your market would open up and grow spectacularly if you could make a version of this for Linux (and possibly BSD). OpenSwiftUI might be a great start for research.
Thank you for pointing this out! These are future goals, but not yet. The plan is macOS, then iOS (started), Android, then maybe Windows. But we are not there yet. About us page updated.
I quite often login to routers/firewalls to pull the ARP and Route Tables. If there was an option to add an API Key + REGEX + HOST/s for processing with a one-click button that'd be rad
I have not seen it until just now, but graphs are coming! I don't think they will be quite as front-and-center as PingDoctor, but you will clearly see history.
Hmmm... explain more. API key for what? Are we talking about looking into a Meraki or Juniper platform using API and pulling those? Or logging into a local device?
I don’t know if this will be useful for me (on a phone right now and need to see the details on a Mac). I was intrigued as well as surprised by a “one day trial” offer. I’ve usually seen seven day trials, 30 day trials, etc. One day seems too short to me. A longer trial and/or based on number of launches may be better.
The software actually looks really cool but I would question if the name is working in your favour. "Stalker" is a very loaded word and many people will have negative emotional reactions to it. It feels like one step away from "NetworkRapist."
Yeah, I've heard that a couple of times lately. Appreciate the honest feedback. The hope was that it would be more memorable than creepy, but I think that word has stronger meanings for some than others. I think there might be a name change in the future... Hopefully I'll get a few more steps away :)
Yes, many features:
- Continuous ping of the network after scanning
- Addition of visuals like history and timing graphs
- DNS troubleshooter
- More logos for vendors
- Full port scans (on request)
- Visual traceroute
- mDNS browser
And I'm always on the lookout for more...
I'll also be adding a second tier for Wi-Fi related functions - such as report cards, roaming reasons (based on OS logs), pcap analysis, history graphs, and much more.
Cool. For a moment I got excited and thought someone built an alternative to the crazy-spendy Ping Plotter. An always-running statistical view of traceroutes for multiple sites is something only they seem to be doing well.
This should be working for you - please make sure you have "5 GHz" or "6 GHz" selected - and then you should get 80 and 160. You can see this in the screen capture here:
https://pingstalker.com/help/wifi-capture/
I was excited see what this could do, but the moment I saw it was a one day trial, I was so turned off that I didn't even bother wasting my time even looking into it and just removed it.
If you want people to invest time investigating your product to see if it's a good fit, don't rush them. I know you are probably eager to turn this into a profitable product, but this is not how to approach people like me if you want to see any sort of return.
Maybe make a lite version that is free and make your paid option have all the extra bells and whistles in it, but please, don't do this.
Thank you for the feedback! As mentioned below, I’ll be making the change to a 7-day trial shortly. Makes sense!
Congrats on shipping!
Apart from the obvious question of why you didn't opt to open source the tool :), I'm genuinely curious about how you approached development.
How did you decide for this feature A: "I'll just spawn child processes and read the output of `x-y-z` and `a-b-c` CLI tools, while for feature B: "I'll drop-down to BSD sockets"? Perhaps you have a performance budget: if using the Apple-provided CLI utilities are not fast enough then you drop down to writing BSD sockets?
Thank you!
So, I struggled with that route so much. I've benefited from open source software throughout my entire life (and have contributed to it as well), and I am truly indebted to it. It is my goal in the future to make this open source, but for now, frankly, the money helps set the time aside needed to make this better. Again, I will revisit this once I hit a goal I have in mind.
So yes, performance budget was a key factor. Some CLI tools provide standard, predictable answers in a set amount of time. Others are all over the place on answers and time. Some commands have options to set timeout, size, syn options, and such, while others do not. I have a few commands that are on my short list to replace with custom code - especially around mDNS.
I think your market would open up and grow spectacularly if you could make a version of this for Linux (and possibly BSD). OpenSwiftUI might be a great start for research.
Good luck!
Interesting!! I’ll take a look at what it would take! Thanks.
Looks cool, but what do you mean by cross-platform?
PingStalker is a modern, cross-platform network scanning app inspired by the specialized needs of IT, engineering, and network professionals.
Thank you for pointing this out! These are future goals, but not yet. The plan is macOS, then iOS (started), Android, then maybe Windows. But we are not there yet. About us page updated.
Understood … I was so curious to learn about your cross platform stack that creates such a beautiful interface.
I'm curious. Do you know any good equivalent for linux? It looks like a great software in term of UI
I don’t know if anything off hand unfortunately. Maybe worth porting if there is enough interest…
Looks like a great and useful app. I'll definitely buy it.
Have you seen PingDoctor? https://apps.apple.com/us/app/pingdoctor/id1350044974?mt=12
I quite often login to routers/firewalls to pull the ARP and Route Tables. If there was an option to add an API Key + REGEX + HOST/s for processing with a one-click button that'd be rad
Thank you!
I have not seen it until just now, but graphs are coming! I don't think they will be quite as front-and-center as PingDoctor, but you will clearly see history.
Hmmm... explain more. API key for what? Are we talking about looking into a Meraki or Juniper platform using API and pulling those? Or logging into a local device?
I don’t know if this will be useful for me (on a phone right now and need to see the details on a Mac). I was intrigued as well as surprised by a “one day trial” offer. I’ve usually seen seven day trials, 30 day trials, etc. One day seems too short to me. A longer trial and/or based on number of launches may be better.
Valid point… I’ll make an adjustment.
The software actually looks really cool but I would question if the name is working in your favour. "Stalker" is a very loaded word and many people will have negative emotional reactions to it. It feels like one step away from "NetworkRapist."
Yeah, I've heard that a couple of times lately. Appreciate the honest feedback. The hope was that it would be more memorable than creepy, but I think that word has stronger meanings for some than others. I think there might be a name change in the future... Hopefully I'll get a few more steps away :)
Maybe "Pingachu" if you want to go in the opposite naming directly. lol
Would you consider extending the trial to 7-days so I don't have to urgently make it the whole focus of my day?
Yes! By Tuesday this will be the case!
Congrats on shipping! Looks like a great tool to add to my toolkit for a very modest price!
Any big significant other features planned on the roadmap? Would be interesting to know what else you are planning to add over time. (If any)
Thank you so much!
Yes, many features: - Continuous ping of the network after scanning - Addition of visuals like history and timing graphs - DNS troubleshooter - More logos for vendors - Full port scans (on request) - Visual traceroute - mDNS browser
And I'm always on the lookout for more...
I'll also be adding a second tier for Wi-Fi related functions - such as report cards, roaming reasons (based on OS logs), pcap analysis, history graphs, and much more.
Cool. For a moment I got excited and thought someone built an alternative to the crazy-spendy Ping Plotter. An always-running statistical view of traceroutes for multiple sites is something only they seem to be doing well.
Charting will be coming, but not at the visual cost of losing the overall dashboard. Stay tuned!
Can you add wider channel width for wireless network captures? Your tool only offers 20 MHz and 40 MHz, but wdutil also offers 80 MHz and 160 MHz.
This should be working for you - please make sure you have "5 GHz" or "6 GHz" selected - and then you should get 80 and 160. You can see this in the screen capture here: https://pingstalker.com/help/wifi-capture/
Ahh! Thanks for that... Yep, was it.
I should have had more coffee before replying. Sorry!
Looks very cool. I'm especially impressed with the extensive documentation on day one. Well done!
Thank you! Now to keep it updated as new features launch :0
Thanks for supplying it outside Apple’s store!
Thank you for supporting it outside Apple's store :)