Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question - Licensing #16

Closed
sgruby opened this issue Nov 19, 2021 · 5 comments
Closed

Question - Licensing #16

sgruby opened this issue Nov 19, 2021 · 5 comments
Labels
question Further information is requested

Comments

@sgruby
Copy link
Collaborator

sgruby commented Nov 19, 2021

Have you thought about your plans for licensing PulsePro? If I wanted to distribute the app to some members of my QA team, how would I go about licensing it? I'm the only iOS/Mac developer, but work with a handful of QA/support folks that I'd like to be able to read logs. With NSLooger, I just sent them the app and was good.

@kean
Copy link
Owner

kean commented Nov 19, 2021

It'll depend on how it goes. I might either make it free or turn it into a proper commercial product. As for now, please feel free to distribute it to the QA team. Do they need the app though? The scenario I had in mind was: QA uses a build with Pulse installed, when they see a defect, they export the logs and attach them to the ticket. A developer can them download and view the logs using the app.

@sgruby
Copy link
Collaborator Author

sgruby commented Nov 19, 2021

My setup is quite unique; I'm trying to make QA (they also handle support sometimes) more self sufficient so that they can do testing and grab what they need in real time without having to grab the log off the device. By reading the logs, they can determine if the problem is an app problem or an API problem so that I don't have to be the gatekeeper for every issue!

Pulse's network logging is the reason I switched loggers...makes it easy for them to see what is going on!

@kean
Copy link
Owner

kean commented Nov 19, 2021

In our team, the QA folks use the in-app logs browser. We added an option to display it using a shake gesture. Usually, all they need is to just check the latest network requests and the in-app browser is sufficient for that.

@sgruby
Copy link
Collaborator Author

sgruby commented Nov 19, 2021

In our team, the QA folks use the in-app logs browser. We added an option to display it using a shake gesture. Usually, all they need is to just check the latest network requests and the in-app browser is sufficient for that.

I use the shake gesture in sort of a similar manner in that it grabs a screenshot (or video) as well as the log and sends them via an internal API. I'll have to see if that will suffice and have them read logs later; the remote logging makes it easier to see lots of data at once when they're running the apps.

@kean
Copy link
Owner

kean commented Jul 24, 2022

The recent version uses MIT license. I'm going to close it.

@kean kean closed this as completed Jul 24, 2022
@kean kean added the question Further information is requested label Jul 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants