5 ms·

Of course but all of the above mentioned can still happen and does happen today with all security measures in place. With the added benefit that we must ask per

by fjabre 8y ago

Of course but all of the above mentioned can still happen and does happen today with all security measures in place. With the added benefit that we must ask permission of a private entity to release an app and we must pay 30% of our profits to the gatekeepers /s I think I like the old way better.

duxup 8y ago
I don't think I understand what the difference is with the "old way" if as you describe it ... there seems to be no difference. You don't have to pay some cert provider under the old or current way.
- fjabre 8y ago
  You do if you want your app not to be flagged as spam. Users are perceptive. They notice when windows brings up a big notice telling them the app is not to be trusted. Perception is everything in those first few moments a user get his hands on your software. But now if I dont pay the entrance fee I potentially get abandoned by said user bc they have been scared off. Its not an app store yet. Give it 5 or 10 years when we no longer have an open web and all we have are walled gardens.
throwawaymath 8y ago
You don't have to do anything you don't want to. No one is forcing you to develop for those platforms. Your old way still exists. Approximately all real world users demonstrably prefer the new way, but if you're set on your old way you can still write software for macOS and Windows. It will pop a warning, but you can make it run anyway. Give your users instructions for bypassing those warnings. If you trust them to manually verify your software then you trust them to follow those directions.
- Wowfunhappy 8y ago
  > Give your users instructions for bypassing those warnings. If you trust them to manually verify your software then you trust them to follow those directions. If your selling software, this probably isn't a good strategy. However, I consider it perfectly reasonable for software that's being created in one's spare time and offered for free. (I think the current situation we have on Windows / macOS is a perfectly fine balance, btw—except for drivers, where installing unsigned copies is way too difficult)

by fjabre 8y ago

duxup 8y ago

I don't think I understand what the difference is with the "old way" if as you describe it ... there seems to be no difference. You don't have to pay some cert provider under the old or current way.

fjabre 8y ago
You do if you want your app not to be flagged as spam. Users are perceptive. They notice when windows brings up a big notice telling them the app is not to be trusted. Perception is everything in those first few moments a user get his hands on your software. But now if I dont pay the entrance fee I potentially get abandoned by said user bc they have been scared off. Its not an app store yet. Give it 5 or 10 years when we no longer have an open web and all we have are walled gardens.

throwawaymath 8y ago

You don't have to do anything you don't want to. No one is forcing you to develop for those platforms. Your old way still exists. Approximately all real world users demonstrably prefer the new way, but if you're set on your old way you can still write software for macOS and Windows. It will pop a warning, but you can make it run anyway. Give your users instructions for bypassing those warnings. If you trust them to manually verify your software then you trust them to follow those directions.

Wowfunhappy 8y ago
> Give your users instructions for bypassing those warnings. If you trust them to manually verify your software then you trust them to follow those directions. If your selling software, this probably isn't a good strategy. However, I consider it perfectly reasonable for software that's being created in one's spare time and offered for free. (I think the current situation we have on Windows / macOS is a perfectly fine balance, btw—except for drivers, where installing unsigned copies is way too difficult)