Jump to content

Invision Community Blog


Managing successful online communities

Rikki
 

Invision Community Apps for iOS & Android

I'm excited to reveal that we are making Invision Community native apps for iOS and Android!

For the past few months, our staff has been using an internal test build right here on our community. Now we are ready to widen testing to a larger pool of customers. Information on how to become a tester is at the end of this post. But first, let's take a look at the app itself.

Technology Preview
We have a lot of exciting plans for the Invision Community app.

We wanted to take full advantage of a clean slate and build a brand new experience that embraces a native app's interfaces. While the app is unmistakably Invision Community, it features new ways of interacting with your content.

We want the app to help shape the future of Invision Community, and we're asking for you to help.

What we are opening up for testing today is a technology preview. This slim app covers the essentials with a view to much more expansion later.

The technology preview is locked to our community. The app we will release will be a 'multi-community' app; a directory of communities users can browse and save.

We’ve taken this approach because the app stores have clamped down on ‘template’ apps, and the cost involved in building and maintaining a separate app per-community won’t be an option for many of our customers. A multi-community app is a great approach for most: simple setup, minimal cost, still fully-featured, and a great way for new users to find your community too.

What The App Does
For the initial phase of this technology preview, discussions are the main focus which is the foundation of every Invision Community. Also available are profiles, streams, search and notifications - including (at last!) push notifications.

Any areas that the app does not currently support will open seamlessly in a web view within the app. As we build new functionality into the app over time, users will encounter fewer of these hybrid views.

Your feedback will allow us to target the highest priority areas during the technology preview phase.

Pricing
Note: The information below outlines our current intentions, but may change as we finalize the app's release to app stores.

The good news is we intend for the app to be free to both our customers with active licenses and their end-users. In time, we will offer a premium option to communities. This funding will secure the app's long-term future.

The premium option could enhance their listing in the directory, or provide special functionality when users use that community in the app.

iPhone Xs.pngiPhone Xs 2.png

Availability

We intend to release the app alongside the next significant point release of Invision Community, expected to be 4.5. Communities will need to upgrade to this version to allow their users to use the app.

Questions?

Why not a PWA (progressive web app)?
Invision Community 4.4 already supports several PWA features. However, until iOS supports Push Notifications (and other features) in PWAs, we don't feel they are a fully-rounded solution to using communities on a phone. Building native apps allow us to experiment with new interfaces and approaches. As PWA support improves in the years to come, we'll feed what we learn back into the main product for the benefit of all users.

Why now?
Those with a long memory will recall that we've had a few attempts at providing an app in the past that weren't successful.

We are great at building apps with web technologies but creating native apps ourselves wasn't sustainable.

Enter React Native.

React Native is an open-source technology for building native apps. React Native allows teams to build native apps using web technologies, but crucially, React Native doesn't build hybrid apps. They are compiled into real native apps - not browser wrappers, but native buttons, text, dialogs, animations and more.

A year or so ago, we started experimenting with React Native to see if it might be a viable approach for us. And it was. Finally, there was a technology that enabled web engineers to build delightful cross-platform native apps.

As we can build native mobile apps using the technology we are familiar with allows us to incorporate mobile app development into our existing processes.

Why just forums?
Invision Community is a large, fully-featured platform, and building the entire platform in a native app from the get-go didn't seem to be the best approach. Instead, we've focused on the most active area of most communities - forums - with other areas still supported in the app via webviews. Over time, additional features and tools will be built into the app so that it eventually reaches feature-parity with the web version. We'll take feedback from our customers to determine which areas to support next.

How will I add my community to the app?
The next significant point release of Invision Community (expected to be 4.5) will have app support built-in. Including your app in the directory will be as simple as enabling the feature in your AdminCP and configuring a few options. 

Is the app ad-supported?
There are no ads of any kind in the app right now. We may include ads or allow communities to run their own ads as a premium option in future.

Can I get a white-label version for my community?
We aim to offer a white-label option in the future.

Will my plugins work in the app?
Probably not. We're intentionally building the app to work with standard Invision Community features and apps right now. If your plugins add new UI elements or change the functions that users interact with it's likely they will not work with the app.

What about themes?
Themes won't work in the app because the app doesn't use HTML. However, some branding/customization will be available via the AdminCP, and we may expand upon this in future.

Have other questions? Let us know in the comments, and we'll answer them!

Sign Up For Testing
For the next stage of our testing process, we will be inviting several customers to try the app and provide feedback/bug reports. As part of the sign-up process, we'll ask for some information about your own community. We'll use this to select further testers once we begin testing of the 'multi-community' version of the app later. The answers you provide will not affect your chance of testing the app on our community.

Interested in joining the testing group? Click here to sign up.

iPhone-6.png


Comments



Recommended Comments

29 minutes ago, opentype said:

Sure, if asked, they would of course all want their own app, but interest alone doesn’t mean that it would be feasible on a large enough scale. Just look at the previous attempts, including those of 3rd-parties. Once admins understand the costs involved in distributing their own app, the interest quickly vanishes. A multi-community app is a compromise, but one that can actually work for many admins.  

Not necessarily. I stopped using Tapatalk and I will (very likely) use the IPS app. It’s far from being the same. Tapatalk was buggy,  a privacy and security nightmare and a third-party solution, which is a problem of its own because there was no priority for the IPS platform and because of the delayed reaction to the native developments. IPS can potentially do so much better than what Tapatalk offers. 

Potentially they may be able to, but at what cost? Less time sorting the gallery etc and other web based features needing attention? And all (by the sounds of it) for the sake of push notifications on iOS, which if some rumours are to be believed will be available in pwa's by the end of the year. It just feels like a waste of time to aid less than 50% of mobile users for what could be a short period of time.

And as for the app itself. It'll be competing with tapatalk which has 1000's of communities signed up and 100's of thousands of installs. It'll not really have a unique selling point beyond what tapatalk does. So, for a user it's a reasonably hard sell to get them to install it.

So, for it to be a success it needs a wide take up from community owners. But it'll have no white labelling and no revenue opportunities at the start, so that'll put plenty off. Then you have those who were keen enough to have an app which already have tapatalk, they're going to need a reason to switch. What's that going to be?

I get that you and others may be keen, I get why that's the case too. But I think, for the reasons I've given, there'll be lots who aren't. 

Then in 6 months if/when iOS sort push notifications, what then? Even less reason for sites to use it, so less take up. Wonder what ips may do at that point? Maintain two code bases which do essentially the same thing or head back to plan a and concentrate on what their strengths were in the first place and focus just on web based apps again? I know what my money would be on. 

I may be being overly sceptical here, but we have been here before and now there's less reason to have a native app than there's ever been. 

Share this comment


Link to comment
Share on other sites
2 minutes ago, Dll said:

I may be being overly sceptical here, but we have been here before and now there's less reason to have a native app than there's ever been. 

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. 

Share this comment


Link to comment
Share on other sites
10 minutes ago, Dll said:

Then you have those who were keen enough to have an app which already have tapatalk, they're going to need a reason to switch. What's that going to be?

This part alone is enough reason for us to provide an app, I think. Many admins that offer TapaTalk have been itching for a first-party (or even a third-party) alternative. They view TapaTalk as a necessary evil, not something they're legitimately pleased to offer their users. We hope to be different in that regard.

Regarding web vs. not web. If web apps on their own were perfect, there'd be no market for TapaTalk, for example - but as you say yourself, there clearly is. The lines are blurring though; the codebase we have for the native app can be transformed into a web app with a little effort. It is, after all, built on a framework originally designed for the web. We will be able to take what we learn from building a new native app, and apply that to the regular web view. Probably not in the 4.x line at this stage, but certainly in the 5.x+ lines. Some of the work may even be directly beneficial. For example, with the new API, we or third-party developers could build entirely new ways of using the Invision Community platform on the web.

Finally, we know the app won't appeal to all communities, for various reasons. That's OK. The app won't stifle any potential PWA work (and as I said, it'll actually make it better), so those that don't want to use the app won't lose anything. Those that do will gain a new way of offering their community to users.

Share this comment


Link to comment
Share on other sites
2 hours ago, Matt said:

Apple don't want to flood the store with copy and paste apps

Apple does not want... Apple has zero interest... Apple has a worlwide coverage of about 10%... BUT iOS is the most popular in USA... Rather complicated.

Share this comment


Link to comment
Share on other sites
1 hour ago, Rikki said:

This part alone is enough reason for us to provide an app, I think. Many admins that offer TapaTalk have been itching for a first-party (or even a third-party) alternative. They view TapaTalk as a necessary evil, not something they're legitimately pleased to offer their users. We hope to be different in that regard.

Regarding web vs. not web. If web apps on their own were perfect, there'd be no market for TapaTalk, for example - but as you say yourself, there clearly is. The lines are blurring though; the codebase we have for the native app can be transformed into a web app with a little effort. It is, after all, built on a framework originally designed for the web. We will be able to take what we learn from building a new native app, and apply that to the regular web view. Probably not in the 4.x line at this stage, but certainly in the 5.x+ lines. Some of the work may even be directly beneficial. For example, with the new API, we or third-party developers could build entirely new ways of using the Invision Community platform on the web.

Finally, we know the app won't appeal to all communities, for various reasons. That's OK. The app won't stifle any potential PWA work (and as I said, it'll actually make it better), so those that don't want to use the app won't lose anything. Those that do will gain a new way of offering their community to users.

Web apps aren't perfect right now, but they're getting there quickly. The trend right now is for more money and time to go into developing pwa's than native, for that reason. Apple starting to wake up more to PWA, as they have recently is an indicator of that as well. 

For me, Tapatalk is a legacy product, it has a wide user base because it's been around years but it doesn't seem to be pulling up trees or doing anything dramatic right now. So the demand for it was probably a reason to develop an app 5 or so years ago rather than now. Plus, if a forum has 100's / 1000's of users using tapatalk, even if it's not completely ideal, it just feels like a stretch to get them to invest the time in pushing an invision version (especially with a lack of monetisation), so your most likely takers are already taken.

5-10 years ago, the reason for making an app were numerous. Slower phones and internet connections meant native was a massive improvement for the user. Responsive design wasn't mainstream, so mobile only sites were often just cheaper, uglier and less feature packed versions of the web version. Native features like location, photo uploads etc weren't available to browsers either. That's all in the past now. 

Essentially, all that's missing from that list on pwa is push notifications on IOS. And that's probably going to change relatively soon. 

I just don't really understand what your aims are with this app. From what's written above, the only usp is notifications. There's nothing else ground breaking or unique in there and I can't think of any functionality in the web version right now, apart from notifications, which doesn't function as needed on mobile.

You've also implied that the future is pwa, and that you'll feed back what you learn into the web product. But what do you want/need to learn from it? Also, at what point does pwa become mature enough for you to decide there's no advantage to maintaining the app? 

It just feels confused, you've introduced it without really explaining the purpose or (more importantly) the advantages for a community owner or community member to install it. Like yourselves, I'm part of a relatively small business, and development time and budget is finite. So, from the outside looking in admittedly, it just appears you're wasting precious time on this, which ultimately has to be to the detriment of other aspects of the software. 

Just my opinion of course, but I'm intrigued as to the thinking on this one. 

Edited by Dll

Share this comment


Link to comment
Share on other sites
16 hours ago, Rikki said:

This part alone is enough reason for us to provide an app, I think. Many admins that offer TapaTalk have been itching for a first-party (or even a third-party) alternative. They view TapaTalk as a necessary evil, not something they're legitimately pleased to offer their users. We hope to be different in that regard.

Yes, this!

There seems to be a lot of focus on "my users don't want a multi community app" and "PWAs are coming". It's not that simple in either regard.

The users of my community with Tapatalk often used it for only one community... Mine. They treated it as an app for my community, and therefore it became a single community app. It did not bother them that they could add other communities nor did they care about the fact that it was as generic as possible in order to work on different software. The pain was felt by me, in keeping Tapatalk working and up to date. Eventually it became too much hassle, so it was removed much to the ire of many users. An app offering would be a welcome return.

The use of PWAs is increasing, so I will not argue the semantics of that. I haven't yet, however, met a single one of my users who knows what a PWA is, how a PWA works, how to add a PWA to their device, etc. In fact, when I advised certain staff members of my community about PWAs they tested them and were not impressed. In short, they'd prefer what they termed "a proper app". I've no doubt that PWAs will improve over time, but for now it's not there.

Share this comment


Link to comment
Share on other sites

So, good news to hear you are doing something positive, however its not ideal for me personally as I currently use a tapatalk BYO app. I really would want the ability to add adverts into any app were I to change.

 

That was until this morning however, when i received an email from tapatalk saying they were discontinuing support for their branded BYO! 😡

Share this comment


Link to comment
Share on other sites
1 hour ago, Steve Bullman said:

So, good news to hear you are doing something positive, however its not ideal for me personally as I currently use a tapatalk BYO app. I really would want the ability to add adverts into any app were I to change.

 

That was until this morning however, when i received an email from tapatalk saying they were discontinuing support for their branded BYO! 😡

According to the announcement, its a major goal of IPS to support both advertisements and white label.  

Share this comment


Link to comment
Share on other sites

We are currently using the premium tapatalk app which they just announced they are sunsetting. We want new apps but HOPE there is an option for a page to pull in from our RSS feed. We use WordPress and would love a page to pull in our "Front Page" posts to go along with the forums. Functionality like that would be great, as would being able to pull in our social media posts from Twitter and Instagram at least. 

Thanks.

Share this comment


Link to comment
Share on other sites
On 9/12/2019 at 1:49 PM, jair101 said:

Thanks, Rikki, thats reassuring! My point was simply that tapatalk did a lot of shady stuff and I wanted to make sure, you are not following in their footsteps. It is easy to say - if you don't like the app, then remove it, but it is not as simple as that. Many users are getting used to tapatalk and they don't care it is more or less a trojan horse in your community. If those users are a very vocal minority/majority the entire community can be held as a hostage to them. 

For me, if I make the app avaialble, I want to make sure it will stay available for the foreseeable future, thats why I asked slightly paranoid questions 🙂

Totally agree on Tapatalk, the experience there has been miserable. A few simple bugs that they could never fix.

Share this comment


Link to comment
Share on other sites
21 hours ago, The Heff said:

The use of PWAs is increasing, so I will not argue the semantics of that. I haven't yet, however, met a single one of my users who knows what a PWA is, how a PWA works, how to add a PWA to their device, etc. In fact, when I advised certain staff members of my community about PWAs they tested them and were not impressed. In short, they'd prefer what they termed "a proper app". I've no doubt that PWAs will improve over time, but for now it's not there.

Why would they though?

But since a PWA can be installed with a single click from a website rather than a visit to an app store and will then act and look like a 'proper app', I'd assume they'd readily use it if the option was available. 

Share this comment


Link to comment
Share on other sites
Just now, Dll said:

But since a PWA can be installed with a single click from a website rather than a visit to an app store and will then act and look like a 'proper app', I'd assume they'd readily use it if the option was available. 

I’ll reiterate: they tested it.

Issues were numerous, including lack of push, odd navigation problems (e.g. going back was counterintuitive compared to a native app experience), the PWA shortcut needing to be removed to resolve caching issues, etc.

As I said, and in my opinion, PWAs aren’t there yet.

Share this comment


Link to comment
Share on other sites
2 hours ago, opentype said:

It IS available right now. That was the point. 

So the issue isn't PWA per se then, it's whatever implementation of it being tested. 

Have a look at the ever growing list of major websites using PWA. Most are seemless.

https://appsco.pe/toplist

Many companies / websites are getting great results from them also - but again, it's all about the implementation. 
https://www.pwastats.com/

I'm not saying PWA has everything native has at the moment, we all know the limitations in terms of notifications etc. But my point is that IPS's core is the web app, the skill set within the company is clearly web based, and there's a ton more that has been left on the table in terms of PWA with it so far. There's also parts of the software which are really in need of some love - gallery, blogs and clubs are under developed as three examples, and newer community software like discourse and Flarum have moved the game on in terms of forum layouts and features.

So, even with react native helping, lurching off to spend valuable time on a native app just as PWA is maturing quickly, getting more Apple support and so on just seems backward. 

Share this comment


Link to comment
Share on other sites
22 minutes ago, Dll said:

So the issue isn't PWA per se then, it's whatever implementation of it being tested. 

Or that many users simply don’t get the this middle-ground solution between website and app and just don’t use it (enough). 

38 minutes ago, Dll said:

Have a look at the ever growing list of major websites using PWA. Most are seemless.

And others are seeing great results with native apps. This kind of argumentation is going nowhere. 

Share this comment


Link to comment
Share on other sites
1 minute ago, opentype said:

Or that many users simply don’t get the this middle-ground solution between website and app and just don’t use it (enough). 

And others are seeing great results with native apps. This kind of argumentation is going nowhere. 

You're missing both my points though. A user doesn't care if it's a native app or a PWA, they care if it does what they want it to do.

And again, I'm not saying native apps aren't good or worth having. I'm saying that in this specific situation it appears to be a waste of resources when considering the amount of improvement which could and needs to be made to Invisions core, web based products. Particularly since PWA is moving quickly and could do everything native does inc notifications in 6 months time.  

Share this comment


Link to comment
Share on other sites
19 minutes ago, Dll said:

A user doesn't care if it's a native app or a PWA, they care if it does what they want it to do.

I agree 100%. (And that’s why this pwastats site is completely nonsense or dishonest in suggesting that improved metrics are due to the use of PWAs.)

But the difference between “add to homescreen” vs. “installing an app“ might make a difference at the moment, as The Heff suggested. That matches my observations and was also my point in the last post. IPS can’t distribute all our apps directly, but every IPS website owner can’t become an app distributer because of the costs and complexity. That’s the problem (as I mentioned earlier) and the multi-app solution is a good compromise to overcome this very problem. 

The only complaint left is the supposed wasted resources, but IPS has already explained that the app uses web technology(!) and as such it is not wasted but can be reused for 5.x or inform future developments directly. 

Edited by opentype

Share this comment


Link to comment
Share on other sites
1 hour ago, opentype said:

I agree 100%. (And that’s why this pwastats site is completely nonsense or dishonest in suggesting that improved metrics are due to the use of PWAs.)

But the difference between “add to homescreen” vs. “installing an app“ might make a difference at the moment, as The Heff suggested. That matches my observations and was also my point in the last post. IPS can’t distribute all our apps directly, but every IPS website owner can’t become an app distributer because of the costs and complexity. That’s the problem (as I mentioned earlier) and the multi-app solution is a good compromise to overcome this very problem. 

The only complaint left is the supposed wasted resources, but IPS has already explained that the app uses web technology(!) and as such it is not wasted but can be reused for 5.x or inform future developments directly. 

I'm not sure why you think the pwastats info is incorrect, but never mind.

Regardless of what framework Invision use for their apps, it's still a new skill set and will still use time and resources better spent on existing web based products.

Anyway we're going in circles here. I hope ips makes their app a success and their web based software development doesn't stall further because of it. I also hope they don't bail on it 12 months down the line and create problems for community owners. Time will tell.

As a final thing, an interesting tweet from a recent presentation.

 

 

Share this comment


Link to comment
Share on other sites
27 minutes ago, Dll said:

I'm not sure why you think the pwastats info is incorrect

Do not put words in my mouth. I did not say “incorrect”. I said it suggests PWAs as cause of improvements, when that causal connection cannot be made this easily. It’s the classic post-hoc-ergo-propter-hoc fallacy. 

Quote

Regardless of what framework Invision use for their apps, it's still a new skill set and will still use time and resources better spent on existing web based products.

And that’s where your argument is objectively flawed. They ARE building a web-based product, which just happens to be delivered in an app wrapper. That’s why it is NOT a waste of time and you are defeated by your own arguments, since you yourself argued that no one cares about what is working under the hood. Yet you blame them for going with an app instead of PWA, when you yourself admit that it is irrelevant. Just read again what IPS staff said. This discussion is only going in circles because you keep repeating a point while ignoring the facts defeating this very point. 

Edited by opentype

Share this comment


Link to comment
Share on other sites
29 minutes ago, opentype said:

Do not put words in my mouth. I did not say “incorrect”. I said it suggests PWAs as cause of improvements, when that causal connection cannot be made this easily. It’s the classic post-hoc-ergo-propter-hoc fallacy. 

And that’s where your argument is objectively flawed. They ARE building a web-based product, which just happens to be delivered in an app wrapper. That’s why it is NOT a waste of time and you are defeated by your own arguments, since you yourself argued that no one cares about what is working under the hood. Yet you blame them for going with an app instead of PWA, when you yourself admin that it is irrelevant. Just read again what IPS staff said. This discussion is only going in circles because you keep repeating a point while ignoring the facts defeating this very point. 

I know in your mind you're correct and everything I say is down to my lack of understanding of what you're saying, what ips are saying and whatever else. But clearly I disagree, and really don't accept that my argument is so obviously flawed at all.

The way you have twisted my argument about people not caring what's under the hood is a case in point, since your interpretation is entirely different to my meaning and out of context with the point I was making. That was in the context of people wanting 'proper apps' not PWA's, but in actuality many people won't or don't know the difference when it comes to actually using them anyway. If you're not deliberately misinterpreting and genuinely are misunderstanding my point, I'll put it in a simpler to understand way: If Invision ironed out the flaws in their web apps and maxed out what is available in terms of a PWA right now, their core product would clearly benefit, and very few people (members or community owners) would need or want a native app. So, they could achieve their goals without investing time in a new framework in order to create native apps.

React Native is still a new framework, they are not using it to create anything other than a native app (that's what it's for). Yes, it's a 'web technology' - eg javascript, but it's still a distinct product solely for creating native apps, with its own learning curve even if they're already using react.js. And regardless of that, it's still time taken up creating an app, which whatever way you want to paint it, has to be time taken away from other things.

There aren't limitless hours in the day, or a new team looking at this (as far as I'm aware), so clearly something has to give. They say they will learn from it and feed that back into the main web product, which is very different to them creating some sort of miracle development that'll go into the web product and simultaneously get plugged in to native apps too. 

Edited by Dll

Share this comment


Link to comment
Share on other sites
18 minutes ago, Dll said:

There aren't limitless hours in the day, or a new team looking at this (as far as I'm aware), so clearly something has to give.

If the argument boils down to this, then I don’t disagree. Yes, there are costs. And there are benefits. Weighing those against each other is subjective—and guess work, since there are variables about the future we can’t even know. 

Share this comment


Link to comment
Share on other sites
29 minutes ago, opentype said:

If the argument boils down to this, then I don’t disagree. Yes, there are costs. And there are benefits. Weighing those against each other is subjective—and guess work, since there are variables about the future we can’t even know. 

To a point. We can get an idea of the direction of travel right now. We can see where experts are recommending publishers and developers concentrate their efforts on. We can also see Apple coming round to PWA and supporting more of the features. 

We can also see what Invision does as a product, and what PWA can do. And the only thing missing? Notifications on IOS, that's pretty much it...

Quote

Why not a PWA (progressive web app)?
Invision Community 4.4 already supports several PWA features. However, until iOS supports Push Notifications (and other features) in PWAs, we don't feel they are a fully-rounded solution to using communities on a phone. Building native apps allow us to experiment with new interfaces and approaches. As PWA support improves in the years to come, we'll feed what we learn back into the main product for the benefit of all users.

So, right now, the only real unanswered question is whether or not Apple will support that soon. Many people think they will, and their direction of travel suggests they may, as their usage is growing dramatically and developers love them. Developers tend to lead in this sort of thing as it becomes pretty difficult for a single platform to fight against the tide when everyone else is going all-in. 

Put it this way. If Apple opened up notifications on IOS PWA's next week/month, would you want a native app as described above (eg slim feature set, no themes, no plugins, no monetisation, just forums, no gallery, blogs, clubs etc until hopefully some point in the future)? Or would you prefer Invision to move fast and get PWA on the web kicked into gear across the entire suite?

It looks like (to me at least) we're on the cusp of Apple joining Google and MS and embracing PWA fully, So it is potentially the worst moment to start playing about with a native app, even if it is much simpler using a framework like react. If Apple don't do what most people expect and IPS do develop their native app, then great they'll look like geniuses having bucked the trend and got ahead of the curve, but that'd be more luck than judgement as it doesn't look especially likely.

Yes, it's a guess, but it's an educated one. And in 6/12 months time, if Apple still aren't playing ball, I would assume the air may start to drain out of the PWA balloon to an extent, and then, native would start to look like the right route to head in again. But now, for me at least, the idea is either 5 years too late or (maybe) 12 months too early. And while they've waited this long, those extra months won't hurt & it's not like there's nothing else for them to be getting on with. 

Edited by Dll

Share this comment


Link to comment
Share on other sites

If Apple add full push notifications to web apps before the end of 2020, I'll eat not only my hat, but yours too.*

I love your passion, DII but we have given this a LOT of thought. We haven't just gone "OMG lets do an app LOL". It's been something we've been discussing for about 2 years. We've been waiting and waiting and waiting for Apple to take PWA seriously and while they are inching forward with service workers and other things, it's still a long way off.

So we've had no choice but to go the native app route. Don't worry about resources though, we're fine. There's like 18 of us now.

*If you are showing a screenshot of this in 2020 from your push notification from a PWA on your Apple device, I regret everything.

Share this comment


Link to comment
Share on other sites
1 hour ago, Matt said:

If Apple add full push notifications to web apps before the end of 2020, I'll eat not only my hat, but yours too.*

I love your passion, DII but we have given this a LOT of thought. We haven't just gone "OMG lets do an app LOL". It's been something we've been discussing for about 2 years. We've been waiting and waiting and waiting for Apple to take PWA seriously and while they are inching forward with service workers and other things, it's still a long way off.

So we've had no choice but to go the native app route. Don't worry about resources though, we're fine. There's like 18 of us now.

*If you are showing a screenshot of this in 2020 from your push notification from a PWA on your Apple device, I regret everything.

I enjoy the sarcasm, but if you're so well resourced please hurry along with sorting the pwa features which are available (inc notifications for Android!) And give the gallery and blogs a bit of time as they're really lacking these days.

Share this comment


Link to comment
Share on other sites
2 hours ago, Dll said:

We can also see what Invision does as a product, and what PWA can do. And the only thing missing? Notifications on IOS, that's pretty much it...

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. 

Share this comment


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...