Jump to content

Community

Rikki

Invision Community Team
  • Content Count

    24,136
  • Joined

  • Days Won

    74

 Content Type 

Profiles

Downloads

IPS4 Documentation

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Everything posted by Rikki

  1. Iโ€™ve been following tailwind closely for a while. I canโ€™t say for sure weโ€™ll use it in future but I definitely like the approach ๐Ÿ˜Š
  2. It uses the normal language system, allowing you to translate the UI via the ACP ๐Ÿ™‚
  3. Not in the iOS App Store, no - Apple's policies have become much stricter around thin wrapper apps and white-label apps. Android is more open, though.
  4. First and foremost, you aren't allow to have App Store apps that are just thin wrappers around responsive webpages, so that's a motivation to do a proper native experience. We also want to keep a consistent UI between communities once the multi-community app launches (customization will be possible, but the overall structure will be consistent).
  5. The first blog entry contained a bunch of screenshots, but we will do a review of the app soon ๐Ÿ™‚
  6. It is unfortunately slower on Android than iOS right now, due to a low-level difference between the environment our app is built on. However, there's an updated environment coming for Android soon and I anticipate this will greatly improve the experience for Android users.
  7. Since we announced native Invision Community apps for iOS and Android, the response has been incredible. Hundreds of customers registered interest in joining the testing process, and for the initial round we selected around thirty users, roughly split between iOS and Android. Thank you to those testers for their work in reporting issues and providing feedback over the past couple of months. Open Beta I'm pleased to report that we are now ready to begin an open beta of the app, allowing everyone to install it and test it. See below for information on installing the apps. As this is still a testing process, we'd welcome any bug reports or feedback you have. Instructions on doing that can also be found below. The app going into open beta today is essentially a 'white label' version for our own community here. This enables us to test the basic community functionality more widely before we release the free 'multi-community' app that customers will be able to use with their own communities. Already signed up for beta testing via our survey? Thank you! Once we begin testing the multi-community app we will select a new group of testers from those that signed up, and invite them to offer the app to their own users on their own communities. This stage will come once Invision Community 4.5 is released later this year. Installing the app iOS iOS users will need to install TestFlight from the App Store. This is an app provided by Apple that allows developers (such as ourselves) to issue test versions of applications. Once installed, sign up for the beta test by going HERE on your iPhone. Android Android users should go HERE on their device to sign up for the beta. Reporting issues/providing feedback If you would like to report an issue with the app, we are managing issues via a special GitHub repository. You will need a free GitHub account to report new issues, if you don't already have one. Click the Issues tab, then the New Issue button and follow the steps. Please provide as much information as you can. If you'd like to provide feedback via a private channel, or if you have a sensitive bug to report, please email us at a dedicated email address: mobilesupport@invisionpower.com Disclaimers The app you will be installing is a beta version and we offer no guarantees with it. If you are not comfortable using beta software and the inherent risks in doing so, please don't install the app yet. We reserve the right to suspend testing or exclude individual testers at any time if necessary.
  8. The 'grid' idea is interesting. Know of any other product that does localization with that method?
  9. I just wanted to note that we've improved the error message for this error in 4.5, so users at least won't see a mysterious "-200" message when it happens.
  10. We aren't planning to update FA in this release, no. We don't consider the cost/benefit to be worthwhile at the moment, given that it'd impact backwards compatibility with themes (unless the javascript swap technique is used, which is less than ideal). We'll consider the available options at the time of the next major release.
  11. No need to hold your breath - it's already fixed and merged into the next release ๐Ÿ‘
  12. I've logged an issue for this and we'll look at getting it changed for 4.5 ๐Ÿ™‚
  13. A fix for this was actually merged this past week. It should be included in the next major release (not the next 4.4 point release, since it's a higher impact change).
  14. Platforms that use reverse order do so to show feeds - individual items not related to each other. We do that for the topic listing and for streams. I canโ€™t think of any platforms that actually show conversations in reverse order. Twitter replies, iMessage, WhatsApp, Facebook and Instagram comments - theyโ€™re all in regular chronological order (aside from when โ€˜intelligentโ€™ ordering is employed, such as Facebook showing 'relevant' messages or Reddit sorting by most-upvoted). In fact, the only medium I can think of that uses reverse order is, ironically, good old-fashioned email (and even that depends on your client).
  15. The only app being tested right now is a 'white-label' app for this community. The multi-community test will come later. We're gradually expanding the number of testers, so sit tight ๐Ÿ™‚
  16. Whoops, you're right. Text isn't a 'child' in CSS, so actually I don't think there'd be a way to do this with CSS alone. Sorry for the confusion!
  17. You could actually do this already - add this to your custom.css theme file: .ipsType_richText span.ipsEmoji:only-child { font-size: 48px; }
  18. We anticipate it'll be available with v4.5, or shortly afterwards ๐Ÿ™‚
  19. Luckily, thanks to our work on the native app, we now have a services infrastructure that can register user devices and send notifications - when we feel the time is right. That's an example of the work we're doing on the app feeding back into the main product. You are obviously welcome to voice an opinion, but I feel like we're going in circles a bit. We've explained why we're going this route and why we don't feel PWA should be a sole focus right now, so repeating "but why?" in every reply won't get a different answer at this point.
  20. My personal recommendation is use a password manager, preferably one that stores the encrypted passwords on your own storage (e.g. your own cloud account) rather than a central server. That way you can generate extremely good passwords and maintain a different one for every site without any hassle.
  21. 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.
  22. We have a fix ready and it should be in the next release ๐Ÿ˜Š
  23. Yes, but we don't do that right now. I just don't want to completely rule it out from ever happening, because doing that tends to bite us later ๐Ÿ™‚ It's not something we have on the roadmap at the moment.
  24. Yes, that's a fair comment. When I use TapaTalk I get much more of a 'platform' vibe from it, as if I'm using TapaTalk first and foremost, and the actual community is secondary to that. We've tried hard to do the reverse and make sure each community feels like it's separate from the others. Right now for example, there's no central login system, central activity feed or central notifications, no cross-promotion of communities and so on (though I can't say those things will never appear - I do think there's justification for some of them). Each community is entirely standalone once you tap into it from the directory.
ร—
ร—
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy