Jump to content

Community

Morgin

+Clients
  • Content Count

    651
  • Joined

  • Last visited

  • Days Won

    3

Morgin last won the day on April 18 2014

Morgin had the most liked content!

1 Follower

About Morgin

  • Rank
    Community Regular

Recent Profile Visitors

7,585 profile views
  1. @stoo2000 not to pile on but also wanted to see if you might be open to adding Mailgun support? It has replaced Sparkpost for me given it has a free tier up to 10k emails a month. Thanks!
  2. @Callum MacGregor Any chance you'd be willing to update this to add Mailgun API support and/or Amazon SES email support? @Mark Flagging you in case you guys had plans to add other e-mail delivery API's in an upcoming update so no duplication of work.
  3. For what it’s worth, they have answered that question before too. They are simply taking a different path than xenforo, which has splintered support for PWAs/push. Invision wants to roll it out when it works and is stable for everyone, regardless of device/browser. Its probably not what you and others prefer (and since I’m not an android user I’m fairly ambivalent), but it’s their strategy and their call to do it that way. I trust they have the data and metrics we all have access to (and more) to have made that judgement call.
  4. Yes? There are no notable PWA improvements in 13 or 13.1. You can literally test this yourself on an iOS13.1 device using the testing tool on the site I linked. Look, I know the point you are trying to make. @Matt can confirm how many times I’ve slid into his DMs trying to nudge him to be loud and obnoxious with Apple on behalf of Invision Community clients regarding the slow uptake of PWAs. I’ve been beating that drum here for a long time and I’ll be the first to be back on their case if and when Apple ever decides to join the rest of us in the modern age. Until that time, there’s no path to a viable one size fits all native app for individual communities. We’re having our lunch eaten by other social platforms that can gamify user behavior with frequent pushy native notifications. People complain they don’t like that, but it’s wildly popular, so seems like it works. I want my users to be able to get push notifications so they keep coming back and don’t forget about my site. This seems like literally the only solution that is viable and hits the minimum requirements for a native app. I think everyone would love a world where each of our communities got their own app and it was cost effective and easy to support. We don’t live in that world until PWAs are universally supported. So here we are. This solution will at least work for some people, overlaps with technology goals of future development in any event, and long term could be a springboard for other improvements. There’s no downside in my opinion because for me at least, a native mobile app even with all these compromises is still much more important than updates to blogs which as far as I’m aware is a pretty niche and minimally utilized part of the platform.
  5. https://medium.com/dev-channel/progressive-web-app-progress-in-ios-12-2-beta-1-build-16e5181f-a18cd05ca361 theres a lot more missing in webkit’s PWA implementation than push notifications. There has basically been no progress on this list in a year. So I reject your claim that Apple is coming around on this. They have shown zero interest aside from some responses on Twitter that they are starting to look closer at it now.
  6. I don’t think you are giving enough credit to how much of a game changer being able to maintain the app codebase in react native is vs. having to support separate android and iOS codebases using somewhat proprietary languages. I believe Invision has spoken of this before and my recollection is they are very upfront why their previous efforts failed - they are first and foremost a web application company, and not an app company, and they underestimated the work involved in maintaining those codebases and planning features under mobile app constraints. An enhanced API being developed to permit a react native app codebase is hugely beneficial to the platform as a whole. It’s going to open up all sorts of additional neat ways for developers to interface with the platform using modern web first tools. There’s ultimately also a fair bit of overlap with some of the foundational work that has to be done to expand PWA support, so this isn’t like they are focusing on one technology for the detriment of another.
  7. As a strategy, it certainly would make sense too - there’s a lot of money to be made in taking what you’ve done with Invision cloud and commoditizing it to cannibalize communities from competing global platforms. I mean, tapatalk tried to give that a go with acquisitions like Yuku among others and they offer a turnkey community solution now, it’s just not very good. There’s room for that type of product to exist alongside providing the platform itself as sort of a white label community solution for others. Given I’d like to see Invision around for a long time, I’m fully aware that on the business and revenue side you may need to look at Invision itself becoming the community that serves up turnkey subcommunities while handling all the messy account and admin stuff. As long as there always remains some separation for those that need it between Invision as a Reddit/Facebook type of omnibus platform (if or when you make any moves that direction), and Invision the neutral decentralized community software provider, I think we’ll be in a good place.
  8. I guess this is a good stopgap. The fact you can do it in react native makes sense. Philosophically, I think I’ve probably said enough times that from where I sit as an admin, part of the long term success of Invision Community seems to me will rest on maintaining the decentralized and ad hoc nature of communities (as compared to Facebook, Reddit, etc.) That is, as more people realize that the “platform communities” have significant downsides from a privacy and control perspective, we can operate our boutique communities to fill that niche and promote our decentralized nature as a reason to join a community. For that reason, I’m still all in on PWAs precisely because they don’t intermingle or confuse Invision as being akin to a reddit with one app with a bunch of subcommunities. I’d be nervous promoting an app that works across multiple communities precisely for the optics that creates of being part of a larger platform/user worries about who controls the data/etc. However, Apple does what apple does, and I need mobile push notifications, so I’ll take what I can get. The comments about ads are fairly relevant and high priority for me though. Anything that reduces the profitability of my community serves to disincentivize me from grinding it out and trying to compete. If this swallows up all my mobile ad revenue (which >50% of total ad revenue) I’m going to be in a tough spot. All said, it’s exciting to see these efforts. Looking forward to the launch.
  9. Sidebar: people still print stuff???? (good luck with modifying though!)
  10. And there likely won't be until native webkit supports emerges. Focus your efforts there.
  11. Specifically, I’d love to see a site that integrates this for a landing page along with utilizing the styled pages blocks.
  12. No, and browsers don’t really adhere to that anymore anyway. It’s a bad user experience Why do you want right click disabled?
  13. Also echoing if anyone has made some real life examples with active content, I’d love to see it!
  14. "Increasing subscription costs by 6000%: A primer in enhancing our retirement plans" 100% open rate.
  15. It’s an assumption that increasing engagement decreases substance. I disagree with that assumption for my own community, but I suppose that is very dependent on each community and the type of content you have to begin with.
×
×
  • Create New...