UX/UI wise the design is already provided where I work currently, so there is not much need for the devs to prototype (the designers do it though). If I do it for my own projects I prototype in paper, I draw around a credit card with a pencil for my "phone screen" (I'm an android dev)
I prototype new tech or integrations though. The current app I work on is so insanely large, over complicated, slow and flaky that when adding any significant new piece of tech, it can be hard to tell if the problems are due to the new tech, or due the legacy code that's broken for an unrelated reason.
So I've found myself doing more and more standalone prototype POC style apps to quickly settle on an optimum implementation of the new tech without being bogged down in all the cruft and 20 minute build times. It's worked really well - at the end we can almost copy and paste the implementation in to the main app, and then spend time polishing the UI instead of fixing crashes and weird bugs.
For a more reasonable app, I might do this kind of thing in a branch, but the advantage of having it separate is clarity - especially if you need to explain the implementation to someone else (or explain it to yourself ;))
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
UX/UI wise the design is already provided where I work currently, so there is not much need for the devs to prototype (the designers do it though). If I do it for my own projects I prototype in paper, I draw around a credit card with a pencil for my "phone screen" (I'm an android dev)
I prototype new tech or integrations though. The current app I work on is so insanely large, over complicated, slow and flaky that when adding any significant new piece of tech, it can be hard to tell if the problems are due to the new tech, or due the legacy code that's broken for an unrelated reason.
So I've found myself doing more and more standalone prototype POC style apps to quickly settle on an optimum implementation of the new tech without being bogged down in all the cruft and 20 minute build times. It's worked really well - at the end we can almost copy and paste the implementation in to the main app, and then spend time polishing the UI instead of fixing crashes and weird bugs.
For a more reasonable app, I might do this kind of thing in a branch, but the advantage of having it separate is clarity - especially if you need to explain the implementation to someone else (or explain it to yourself ;))