1,489 karma · joined January 17, 2015
As a business that sends emails infrequently, it's probably saved me hundreds/thousands and it has good instructions to set it up with SES. One-time (ish) fee, until you need to upgrade to the next major version.
[0] https://www.independent.co.uk/life-style/food-and-drink/feat...
I know this because I'm temporarily using a Chrome-based WebBrowser component for called EO.WebBrowser (for edge-case reasons). I'm working on going back to the native WebBrowser control after getting about a few emails a month of emails asking about RAM usage.
It also shows up in the uninstall comments. Quote from a real comment: "The app works, but it uses a lot of RAM."
Slack and Discord are used for work, which might make users think of it a necessary evil. Paying for software yourself that you don't absolutely need and having it use lots of your RAM is a different story.
It's definitely easier for me to develop on Windows. Though, this is mainly because XCode performance is atrocious on my mac mini and packaging apps for outside the app store is pretty tedious. I still use a buggy tool that Apple hides very deeply on their developer portal (it involves installing an ancient version of XCode).
If you require a UI that is pretty heavy, here is my "secret" trick to save time when developing for both Windows and macOS:
1) Buy a basic HTML template online for your app's dashboard.
2) Don't use Electon. Your users WILL notice and complain about performance. Instead, use the native WebBrowser control in .NET for Windows and WebView using macOS to display your UI. Disable right clicking and highlighting using HTML/JS. To the user, it'll feel like any other native app. Add this meta tag to the HTML file to ensure the WebBrowser control knows to use new versions of IE to render the UI: <meta http-equiv="x-ua-compatible" content="ie=edge">
3) Use the built in script calling functions to transfer settings back and forth between the UI and main app in JSON. Do the back end stuff in native code.
4) You can then re-use most of the UI code you wrote to easily port over to macOS. Use the same functions and logic you wrote on Windows to make your Swift functions.
Good luck!
For some reason, it's oddly satisfying to see two concepts merge into one cohesive logo.
Part of respecting user privacy is accepting the fact my tracking scripts will be blocked by most privacy extensions.
I feel Matomo does privacy correctly. By default it continues to use the well known piwik.js filename that extensions block and also respects the DNT (do not track) signal from browsers.
I find it has 80% of the features GA has, it's GPL v3+ and only takes a few minutes to setup.
The plethora of support emails is what motivated me to get one in the first place. I used to get accused of giving users a "virus" and getting into infinite loops on why they should trust me. I'm sure I was wasting more than $100/year of my time responding to these emails, so I just gave in and got one.
Now, I don't know what to do.
Boring maybe, but Bootstrap is extremely practical for non-designers like me.
I feel like Bootstrap captured more than 80% of the features I want for less than 20% of the time (or cost) it would take to make something from scratch.
Second, navigation on websites became much more predictable. The examples they show of Web Design 3.0 look difficult to navigate. Aside from increasing dwell time from confused users, there probably isn't a big benefit.
In the future, I see custom website design being accessible for large companies that need their site to evoke a certain brand image. For the rest of us, Bootstrap will continue to evolve (Web Design 2.5) to provide +80% of what we want.
Oh man. It looks like we've come full circle on well intentioned but poorly implemented EU regulations.
Maybe reducing the max number of recipients to the hundreds would help reduce the chance for abuse while still keeping your core customer base happy? It might also reduce the risk of getting booted off the Chrome Store.
From your comment on the blog: > Like I’ve explained above, cancel@gmass.co is not an email address.
To the average user, it certainly looks like an email address. Maybe just have it act like a normal email and list it under the support section of your website: https://www.gmass.co/#contact
> High volume of device requests predominantly due to stolen devices investigations.
> High number of financial identifier requests predominantly due to iTunes Gift Card and credit card fraud investigations.
"Our 3D rendering engine currently uses a Chrome-only technology called Native Client to power Earth Studio. However, we’re closely tracking the evolution of WebAssembly (especially threading). Stay tuned!"
Competing with Alibaba. Amazon seems to have decided to increase product variety (through increasing foreign based stores) at the cost of losing quality control.