I’m a writer and editor with an interest in content strategy and a technical bent. I am especially good at pulling together the threads of tech history (which you may have seen on my newsletter Tedium, which periodically shows up on HN) but also have two decades of work history in marketing and journalism. As a freelancer, I’ve written many popular stories for Vice’s Motherboard and just published a story in Fast... - Source: Hacker News / over 2 years ago

Newsletter author here. I run two actually—Tedium (https://tedium.co/) and MidRange (https://midrange.tedium.co). Yes, they work. Beyond the ROI benefits already mentioned by other folks, it’s seen as an “owned” platform, something that you control, versus social media, where the platform is operated by someone else. You can make changes and adapt more efficiently to subscriber needs than somewhere like social... - Source: Hacker News / about 4 years ago

I have been using Craft to run my newsletter, Tedium (https://tedium.co), since the start of 2019. I moved from Ghost, which at the time was not really designed for newsletters at all. I find Craft an amazing tool when I want to add new things—a big difference from Ghost, where everything is just kind of set for you and you have to rely on external integrations to expand functionality. I custom-code my emails and... - Source: Hacker News / about 4 years ago

Https://tedium.co A newsletter that also has a website attached. I set up the backend so it spits out full code for a newsletter in a specific backend view. - Source: Hacker News / over 4 years ago

I run Craft CMS for Tedium (https://tedium.co). I could push it further but one way I use it is by creating a custom view that “spits” out a completed email template with all of my desired layout considerations and quirks already considered. I could push it further and run the newsletter through Craft itself, though I’ve chosen to pay someone to manage the sending of the email. (And while not particularly... - Source: Hacker News / over 4 years ago

This creates Flutter's fundamental limitation: no code push capability. React Native developers can update JavaScript bundles at runtime through services like Microsoft's CodePush. Flutter's compiled Dart code is static machine code. There's no runtime interpreter in release builds. Once you publish an app, fixing bugs requires a full app store submission. That's typically 1-7 days for Apple review and hours to a... - Source: dev.to / 7 months ago

In my opinion it doesn't make any sense you can use https://microsoft.github.io/code-push/ which is free. I use this for my apps android/ios and works fine.. I hope it helps. Source: about 3 years ago

I come from smartphone app development and now moving to chrome extensions I miss something called CodePush which would push Javascript changes live to app store, but not native code so we could hot fix critical stuff without waiting for store reviews... Source: over 3 years ago

One feature I feel holding Flutter back compared to ReactNative and other options is Code Push. I really enjoy writing Flutter apps but the ability to push updates and bypass store reviews has been extremely valuable for multiple companies I've built apps for. https://microsoft.github.io/code-push/. - Source: Hacker News / over 4 years ago

Couldn't you just add the adults as testers to the Google Play app, avoiding oversight? The problem with breaking off from Google Play is you lose the ability to send push notifications. You could look at Code Push [0] for seamless updates. TBH its not the easiest to integrate with. [0] - https://microsoft.github.io/code-push/. - Source: Hacker News / over 4 years ago