Jump to content

Community

Dylan Riggs

Members
  • Content Count

    1,949
  • Joined

  • Last visited

  • Days Won

    4

Dylan Riggs last won the day on January 5

Dylan Riggs had the most liked content!

About Dylan Riggs

  • Rank
    (╯°□°)╯ ლ(ಠ益ಠ)ლ
  • Birthday 11/01/1988

IPS Marketplace

  • Resources Contributor
    Total file submissions: 6

Profile Information

  • Gender
    Male
  • Location
    Suisun City, CA
  • Interests
    Paintball, Web Design, Web Development, Brooke <3, Chess, Running

Recent Profile Visitors

54,962 profile views
  1. Looks good. Nice work for a free theme! Better than anything Design Shopz puts out and his are all mostly 'paid' themes and can mostly be achieved with the inline theme editor buttons. 😂
  2. I'm not too happy with Samsung right now. I recently lost my NAS and moved all my most important files onto a 512gb Samsung 850 evo and it randomly failed. I literally lost everything important to me. Soo, I'm going to boycott Samsung because of it. Just a personal opinion. I do have a 970 pro that's running like a champ. But I think I'm going to invest in a higher state raid array of slow discs with a nightly image backup I can deploy if my M2 drive fails on me. Just so odd that an SSD failed and I only had it for a little over a year. Sure, I can get the drive replaced, but I still lost everything dear to me.
  3. sSDs will continue to drop in price
  4. I like the idea. In our case, we have 2 big groups with a lot of granular control. One group is essentially posting advertisements, the other group is essentially following said people posting the ads. We can convert the follow feature into a paid/vip only feature rather than making it site wide which is only useful to one specific group anyways.
  5. All of this can be done with the custom fields. The ones listed are just examples out of the box. Discord profile can simply be a custom field with the icon and the information.
  6. If I had my pick, which we can discuss offline as well. I like discourse as a well rounded option out of the box. What features were taken away from desktop viewers that you can’t get added back in? Node is something that’s out of the box, powerful in design, but basic in feature set. It’s economy is developer friendly and works well in other applications that have a great approach to mobile first while keeping the footprint small. Here are a couple of my 0.02c IPS is a great ‘forum’ but that’s about all. Anything else added on top are cherries. I have no complaints about the forum aspect, its community features for member control/profiles etc. Then again, most of the ‘forum’ features you have exist in Vanilla, PHPBB, Discourse, Nodebb, flarum and on and on. THe difference is when you start tacking on other applications for a whole ‘community’ suite. IPS has one, but in my opinion, it’s lackluster. 4.x Pages is just about the same in content development as 3.x - I used to be a huge pages guru developing some really cool stuff with it and it had many perks with the fact that you could build things out of it while being contained in your ecosystem. However, support was lackluster, they didn’t have really any documentation about it or anything else. IPS 4.x does have better documentation, but not by much for pages specifically. You have @opentype and another user who have released pages specific content on the marketplace and that’s about it who are publishing things. I would too, but the investment of time etc isn’t worth it for what I can get back out of it hence why I personally ‘lump’ it into niche market. I hate wordpress, but the simple fact that it’s easy to find themes, plugins and developers while still being supported as a way to extend your site is hard to pass up from a user perspective. Now there are CMS’s coming online that are geared towards node or other frameworks that are super fast, light weight, easily extendable, API driven and some forum platforms offer integrations right outside the box. IPS is trying to maintain a self contained ecosystem which isn’t necessrily bad in a sense for niche markets. But statistically, it isn’t what makes sense for most people. If you bought or use this software. You were either already invested into it from years ago (like in my case) or there is just something about the software that you really need and are willing to sacrifice in other areas to have it. Hence why it’s hard to recommend to ‘most’ people. IPS reminds me of one of those all-in-one TV’s that have the TV, VCR, DVD player built in. But usually it’s best to just buy your 3 different components and save face. Lol
  7. Yes, this This is why I actually like Node and a reason I do like nodebb in many cases to clients. It definitely doesn't have all the features that IPS has, but it's much easier to build said features that are missing in node, and much easier to find developers if you need to. It's 'mostly' designed as a mobile designed with keeping more support for mobile devices than what IPS has as the software was designed for more or less phones and scaled up. It's also much much faster out of the box. Though, again - like anything else we pick... has its pro's and con's.
  8. It'll be less than even that. However, it's still the most 'optimal' for the 3xxx series. Your 3200 should be just fine. Have you thought about just overclocking it to 3600? You will have to increase your latency, but should be easy to pull off.
  9. You can go ahead and call me out as if I don't know what a mobile first approach is. Here: https://www.uxpin.com/studio/blog/a-hands-on-guide-to-mobile-first-design/ Read it. Over and over again. This approach doesn't matter if it's a mobile theme or a responsive site - it is simply DESIGNING your site, approaching how to display the content etc while scaling up. Not the other way around. This is irrelevant to HOW you get to it. IPS is using the graceful degredation method in UI/UX design. I can't take you anymore, I've only ever blocked one person from here. Now you make #2 - you lack misunderstanding heavily and after this long conversations we've had here. I have to say that I now realize you've been trolling me this entire time, your arguments hold nearly zero validity, and clearly from a UI/UX perspective, you have absolutely no idea what you're talking about on a professional level. Perhaps one day you can become a UI/UX designer that I'll look up to, but at this point in time. I've determined you've got a LOOOOOOOOOOONG way to go before that day comes. Good luck to you and I wish the best of luck to all the future designers you come into contact with.. May their local drug stores always have coupons available for some migraine medicine and I hope the people you typically interact with on the daily always have a good supply of ear plugs. Annnnd block
  10. Yes. Exactly. Now you take those 2 highlighted bullets and lets focus on the 2nd one. This one: How would you approach the responsive design? IPS is responsive, any widely adopted somewhat modern post 2011-2012 sites following 'responsive' design do this. The question is. Do you design your UI/UX for the lowest common denominator for your feature set, or do you scale down removing features as you go? Or do you find a balance? In 2014ish or whenever IPS 4 was released and released a responsive framework, it focused on Desktop class browsing and then the smaller your screen gets, the more features are removed, but it was responsive. Back then in 2014, it wasn't widely adopted to think "mobile first" and instead, just introducing a responsive site helped many sites as they no longer needed to support a mobile theme. IPS knows what this is - it is called "graceful degredation" or this incorporates all of the complexities right from the start, then strips them away later for smaller devices. The problem with graceful degradation is that when you build the all-inclusive design right from the start, the core and supplementary elements merge and become harder to distinguish and separate. The entire philosophy runs the risk of treating mobile design as more of an afterthought since you’re “cutting down” the experience. My debate is, it's been like that for over 5 years now with little, if any changes made to the responsiveness to battle the ever increasing use in mobile website consumption. It's been stated here and proven here that by each year, more people are using mobile devices (Phones, tablets and phablets) yet this specific software has not kept up with the times in my opinion. Agree or disagree, that's fine. I'm simply pointing it out. Yes - this is true. Mobile themes are separate entities, hence why when you look at statistics, an all in one that 'supports' touch are still lumped with desktops because it is rendered via the OS. A windows 10 2-in tablet is considered a desktop browser even if it's smaller than an iPad Which reinforces what I was saying earlier. I understand that it is hard for IPS to keep up with a mobile theme because it itself is an entirely different theme. They are just the options that you use. I'm perfectly fine with a responsive design. However, I cannot agree with a desktop UI/UX catering and then just removal of features as you scale to the users viewport on smaller screen/resolution devices. There MUST be a balance, but even small improvements to the UI that I've pointed out here will greatly help users on these smaller mobile devices have a better browsing experience, yet there aren't any removal of features, aren't any extra added bloat to the software, no added additional support and so on. Dedicated mobile themes really just come down to the company willilng to work with it. A smaller company, no? I wouldn't want a mobile theme. I wouldn't want IPS to have a mobile theme. Amazon, bigger store fronts etc have them without content loss because they have the ability to support it.
  11. That's because you edit or I don't care to go back and finding it. You mentioned something "about my past here" along the lines of "Given your past here" something like that. Look, I'm done - no point in debating with you. You're not worth my time. 🙂
  12. Chris, feel free to PM me and I'll discuss with you competitive ideas. As it really depends on what your community is geared for and what you're trying to do. In many cases depending on the niche, I will recommend IPS depending on needs. Like I said, it's not that I don't like IPS - but when someone comes to me asking for something more mobile specific for their users and want to extend the functionality. It's hard to do so in many cases.
  13. I promise, I have no beef with him. I don't even know who he is. Somehow he knows me, or something. And talks about my past here, which was never bad. I was always up for debates and I'm passionate about my work, but hey it is what it is. I've said all I need to say in regards to what proof I have to offer. Do with it and what happens. I'm not losing any sleep on it lol. Trust me, I understand. I only offered suggestions in my original thread. It kind of got derailed debating about what is and isn't a mobile device. Lindy is a smart man - I have faith that IPS will hopefully move in a direction that benefits the masses and not the opposite of what you're saying. Regardless, if bigger clients are coming to me and they're telling me that a majority of their users are mobile, I still trust but verify. I run the numbers and see what they're actually using. I've seen where tablets are the majority, desktops and phones. It's great to always keep up with your analytics and develop accordingly. If the entire web is going that direction, and the client I have is 98 years old and never touched a computer in their life, I would advise to follow what is trending from a UI/UX perspective and develop whatever features they're sought after in that scale. Unfortunately, IPS is hard to recommend as a community platform for the reasons I've laid out in my original posts before the derail in favor of the majority of clients that are active. I think any developer or project manager that is looking at software TODAY to provide to a client that is looking at social engagement is going to be hard pressed to recommend IPS (in my opinion) unless there are many features that they need or the platform entirely makes sense. It's a matter of making informed decisions. Sadly, I feel IPS is behind other platforms. I definitely understand where you're coming from. I know it's going to be hard for IPS to choose certain directions when its current user base that has that niche or is fine where they are would possibly be affected and not want to approach something that affects them negatively, again balance. But I also have a gut feeling that over these last few years, more and more clients aren't signing up and some of the bigger boards have switched away entirely from the platform (Bethesda was one) This brings me back to my original discussion to hopefully bring this back on track. I want mobile-first approaches that make sense in scalability. Also, my recommendations aren't to pull all your eggs in one basket using proprietary frameworks as it, in my opinion has hurt our abilities to provide clients 3rd party themes and applications that are fully custom without relying on a small handful of active developers here. Things that I think any community should take a look at. Looking forward to the next UI and many needed improvements and hopefully without the sacrifice of features.
  14. Here, let me break this down for you, simpleton and then I'll be done replying to you. I have said all I need to say. We're not getting any feedback with the debating. And you still fail to comprehend what the suggestions are for anyways as you keep focusing on something that is irrelevant here. 1. Yes I do - What this meant is when you browse MOST "optimized" websites, they have a MOBILE theme, are responsive or they just don't have any support. MOBILE devices will be selected for the mobile theme. Hence why you can open a page and then "Request desktop view" in all browsers in order to get the full experience. That said, there are many sites out there where the mobile theme is just not the same compared to desktop browsing and is lacking features (think mobile theme for 3.x). Sucks for the site, but it's a true statement. Guess which devices do the rendering of mobile themes? phones, tablets and phablets. 😮 because that's what they are.... mobile devices. Sites that are greatly "optimized" either A. Have a mobile theme or are B. The UI has a "Mobile first" approach since a vast majority of its users are using said mobile devices. To prove you wrong about the statement saying that "I'm wrong": iPAD OS made it so that it allowed SAFARI to bypass the "Request for desktop version" and automatically displayed it. See here: https://ios.gadgethacks.com/how-to/ios-13-makes-easier-request-desktop-mobile-sites-for-webpages-your-iphone-0198650/ Or Apples official site: https://www.apple.com/ipados/ - Scroll down to "Safari" and take a little reading leisure. I'm not 100% familiar with Android tablets, but I believe chrome still prompts you to request desktop view and not render it automatically. Prove me if I'm wrong and which Android tablet supports "Desktop class" browsing out of the box. I'll wait. Which also brings me to my next point: This is why I know you lack the understanding - RESPONSIVE sites don't have these requests, therefor IPS's own site that you used as an example is a terrible example as it's a responsive design and solely only changes based on the users viewport. My argument in this ENTIRE thread has been that it does NOT have a Mobile FIRST approach. It has desktop first and then the smaller your screen gets, the more features are hidden out of your view. That is NOT the right approach or the direction that the web is going. Sorry pal, I'm no sheep here. I'm the T-Rex eating it. I will however say, that I think IPS did a great job on the responsive design when viewed in tablet viewports. I am really pleased with tablet, but that's about it. 2. Where is this "fact"? - statistics are simply that, statistics. On our web anaylitcs, we can see the entire breakdown of every OS, and device usage down to what resolution size the browsers people are viewing from. That's why they're broke apart, not because they're classified differently. It's just to help gauge what users are using so that you can plan how to approach the design and functionality of your site. If you want to take the stance that they're separated because they're different devices, fine. But................. Here is proof that I'm right: https://edu.gcfglobal.org/en/computerbasics/mobile-devices/1/ Straight from google: https://www.google.com/search?q=what+are+mobile+devices&rlz=1C1CHBF_enUS881US881&oq=what+are+mobile+devices&aqs=chrome..69i57j69i59j0l6.2888j1j7&sourceid=chrome&ie=UTF-8 In fact, I can find about I don't know... 100 different results in matter of minutes supporting this. Sure, you can interpret the statistics however you want. You can break them up if you want, but look at it this way. That 78% was on TOUCH based devices ;). They are still rendering a mobile theme for sites that support it, or are simply attaching to the responsive viewport. 3. Don't even get me started on that article from business insider - First, it's cast aside as that article was written in 2013 and the quote you provided was for Zuckerberg's comment MADE in 2011. Guess what wasn't widely adopted thing in 2011? Responsive design nor mobile-first as an approach. Everyone was still using mobile themes, including IPS. Heck we were still on 3.x then, lol. Proof: https://thrivehive.com/responsive-design-history/ While you're at it, take a stab at what "mobile-first" approach really is and get a good concept of it. Maybe you should start redesigning your themes for it? ;). And if Steve Jobs says it's a Mobile device vs's Mark in 2010. Let's look at the real fact. What browsing experience do you get with Facebook on a phone, tablet and desktop? You get a mobile theme on phone/tablet/phablet. You get a desktop theme on the desktop. Even Facebook developed by "the man himself" is doing it correctly. Trust me, I don't follow any gimmicks. I'm following exactly how any of this mobile stuff works. You browse the internet and you go to Amazon.com from a desktop, you get a desktop view. You go on a tablet or a phone, you will get a mobile device view. That is a fact. You pulling up IPS is still reinforcing my argument because it is a RESPONSIVE website and that. is. all. You go to IPS from a desktop, you get the full experience, you go on a tablet you have removed features and or a modified look/feel. You go on phone, you have more removed features. Again, with IPS's software, you only get the full browsing experience from the Desktop... unless us UI/UX designers fix it (I'll leave you out of it until you understand it), which is why I keep telling you about the mobile first approach. If you design the UI/UX for the lowest common denominator (phones) and scale up, everyone will be in a much better, happier place. I'm much much more productive on a desktop, there is no argument there. As I'm sitting here picking your post apart, I'm doing it from the comfort of my desktop because it would have taken me a lot of frustration doing it from an iPhone or even a tablet. And to calm your panties. I don't want any features removed out of IPS (I've said this 10x now) - I only want a better approach for mobile users and if you really think that's a bad idea. You might want to reconsider your designz shop. *mic drop* In all fairness. I enjoy the debate and no hard feelings. You can believe what you want to believe, design how you want to design, market however you want to market. The proof is in the pudding. Take a look at even the short amount of posts here and what statistics they offered up and take with it what you will, believe what you want to believe. Don't trust them or trust them. In time, you'll see. Even Matt mentioned they acknowledged a mobile first approach, that seals the deal. I just hope it comes sooner than later
×
×
  • Create New...