I'd say it stands to reason that people didn't want to miss the outcome.

You could imagine someone casually watching the game is now suddenly riveted to what he or she is watching since the intensity and drama just spiked.

Millennia of imbalance towards men having the upper hand in just about all societies is a plain fact.

However, progress and equality is not the reversal of an imbalance - it's the leveling of a playing field and accepting that to achieve real meaningful change, the notion of retribution must be taken off the table.

Either it's ok for both genders to have a service like this, or it is not ok for either gender to have a service like this. End of story.

Personally I'd find any site like this reprehensible for either gender (or any other biologically or socially discernable metric, for that matter).

Could not agree with the sentiment of this article more.

Do not copy and paste code when you're trying to learn

Always type it out

Off the cuff, I'd suggest something like #2

Charging per client will probably lead to people getting clever, and simply giving multiple clients the same login, that they themselves own and consider as the cost of the service.

Also, it seems like a per-client pricing directly "punishes" people who work on larger, multi client projects, whereas a flat rate for a tiered product encourages them to make the most of what they've been given.

Just my 2 cents, take it for what it's worth.

That definitely makes sense. Thank you!

Is this HTML that you control?

If you're loading it through a C# WinForm control, you might be able to do something like pre-inject a hidden input tag onto the page with a particular name/value, and then in the javascript on the actual page, check for that tag to determine if the page was loaded via a form... I'd guess you'd make a HttpWebRequest out to the resource you want, manipulate the response in some way, then load it into your viewable control... I'm shooting from the hip here, so this is just a guess. I haven't worked in WinForms for a while now.

You might want to look at your approach, however... Are you absolutely in need of having this page be loaded through a WinForm?

Edit: Also the dude suggesting you post this on SO is correct

I have only control on the web app, not the clients.

It is posted on SO in parallel, but there is no help at there, so I thought to try my luck in this community.

Might be able to do UserAgent parsing then... since you're doing a very specific target, it might (keyword might) be simple to do a string compare against whatever the UserAgent of the WinForm app is (I have no idea what it would be, but you could test this very easily), and use that as how you detect.

I hate to hijack the comments with a response that doesn't address the OPs question at all, but I felt like that wasn't necessarily a fair comparison.

ASP.NET Webforms? Yes, huge mistake you'll regret

ASP.NET MVC? Fantastic choice, you will not regret it so long as you're a microsoft based shop

You can't make a blanket statement like that about ASP.NET, since it's effectively a bifurcated ecosystem at this point (and we're all hoping the WebForms fork dies a quick death).

I have a Bachelors in CS

If I had to give a simple, concise answer: Yes, it helped.

If I had to give a longer winded, more precise answer, summed up by a simple, concise answer: It's ultimately debatable, but I'm glad I have it.

If I had to take a stab in the dark, I'm picturing your target audience being someone who owns and manages their condo (not the individual tenants) or a number of condos.

If I had to further guess, these probably aren't the kinds of people who are very technologically savvy, and thus are very unlikely to find your service (even through google awords), let alone realize the potential and why they'd need it.

You say you had a startup before where you physically got in touch with potential customers... this may be the case for another approach like that.

You might consider setting up a demo where you show them an example of a "Condo" already running in your system, the benefits, etc etc, then show them how to get set up on their own. In other words, show them why they'd want to sign up, then show them how easy to get going it is.

But you might still be a step before that process, if you feel you need to improve the app a bit (which is something you'll always need to focus on, anyways). Maybe try reaching out to some people who own / manage condos in your area, explain the service, and offer them a free trial. Draw up some promotional material to give to their tenants, explaining how this will help them get things done, meet neighbors, etc etc, to help those people get going with the system, and then keep a constant and frequent feedback loop with all of them.

Best of luck!

I thought I was the only one...

Slightly off topic - would you mind describing how you host and run the python/flask app?

Do you use uWSGI with apache / nginx in front of it? I dabble in python web apps and wanted to get some insight into how other people had them hosted

Its running via gunicorn (socket) behind nginx (proxy). We also utilize celery and rabbitmq for workers (emails, pdf generation etc.) - besides that, nothing too magical. We use fabric+git to allow for quick hot-fixes and new releases.

Thanks for the feedback!

My cofounder Gavin (@geekforbrains) is better suited to answer this - but I know we're not running apache - it's nginx and gunicorn on a rackspace cloud box.