23 / 23
Oct 2019

Half of all of my visitors are mobile and that number is growing. I split mobile 50/50 between tablet and smart phone. The cart looks fine on a tablet but when viewed on a smart phone it's nearly impossible to read unless I pinch the screen and zoom in. I get roughly 6000 visitors a month. Split mobile in half and that leaves 3000 on mobile devices. Now split mobile in half between tablet/phone and roughly 1500 current visitors will have issues viewing the shopping cart. I see a much higher rate of drop-off on the mobile cart side over desktop.



I'm still very happy with e-junkie but the mobile version would definitely benefit all of us with a new and improved responsive design.

We are well aware of the need for responsive design; in fact, we're redesigning our site and Seller Admin with this in mind, and there should already be nothing inherently unresponsive about our current button codes or cart.



Our box.js script, which is normally loaded into your page as part of your standard View Cart code, manages our overlay-style cart display "inside" your page and detects when the buyer is using a mobile device; in that case, your cart buttons would work in "fallback" mode by opening a separate window/tab to display the cart (rather than displaying the overlay inside your page), to take best advantage of the available screen size and support the standard touchscreen pan/zoom/scroll gesture functionality. I did just now spot a couple minor tweaks we could apply to significantly improve the fallback cart's layout responsiveness, so I've sent that request to Development.



If your site is displaying the overlay-style cart inside your page when viewed on mobile devices, please reply with the URL of a page where that is happening and provide any details you can about which device and browser app produces that problem behavior.

In every smartphone browser I've used to test your site, I'm seeing your cart display in a separate tab/window, rather than as an overlay "inside" your own page. If you're seeing the overlay-style cart on your phone, please clarify which type of device (e.g., iPhone, Android, Windows Phone) and which browser app you're using.

Yes, correct. Thanks for checking so thoroughly.



Separate tab/window: People have to zoom in to see the fine print.



I don't know what more can be said, here. Responsive sites with responsive shopping cart buttons would be soooo cool so that people do not need to zoom in.



If you folks ever develop true responsive cart buttons (and check-out window), then you'd be way ahead of all the other cart services.



Please bear in mind... We absolutely appreciate E-Junkie!

One of the tweaks I recommended to Development was adding a meta-tag:

<meta name="viewport" content="width=device-width,initial-scale=1">

...to the popup/fallback cart that would tell mobile browsers to render it "as-is", rather than zoomed-out on a larger page canvas. This would actually produce better results than zooming-in on the current zoomed-out cart page does.



Our cart button codes in your page inherit CSS from your own page, so you're free to apply whatever responsive treatment you wish to those, which is probably better than imposing a one-size-fits-most responsive approach on everyone that may run afoul of what their site CSS is already doing. Note that the Add to Cart button for items using Variants/Variations is actually an <input type="image"> tag -- CSS selector input[type="image"] -- rather than the linked <img> tag we use for View Cart and normal Add to Cart buttons.



BTW, also note that you really only need one block of View Cart code on each page with any number of cart buttons; you don't need a View Cart next to every single Add to Cart on a given page.

<QUOTE> - BTW, also note that you really only need one block of View Cart code on each page with any number of cart buttons; you don't need a View Cart next to every single Add to Cart on a given page. </QUOTE>



Yes, we understand the redundancy with all those VIEW CART buttons. But try explaining this to our customers... whoo-boy.



We are working on installing the VIEW CART code to one of our menu buttons.



We will work on adapting YOUR CODE to OUR CSS CODE. Yes, inherit. I get that. Could be a great solution here. Glad you pointed that out.



Got to get through this Christmas week. Then back at it.



P.s. Even if I get this to work for our site, this "Responsive" issue won't go away for you good people at E-Junkie. You'll probably need to "Go Down This Road" for all other E-Junkie customers. Thanks.

1 month later

Where does this issue stand for 2014?



Are you guys working on moving ejunkie to the Responsive side?



Can we get an update on this, please?



Thanks.

We are currently on track to have the new Admin live within Q1 2014. We're also working with an outside firm on developing a responsive reskin for our site in general, to go along with the new Admin, which can go live as soon as it's ready regardless of progress on the broader site revamp.

3 months later

Good morning.



Anything happening with the "Responsive" issue?



Thanks

Development is still working on wrapping up the new Admin, with the broader site reskin (incorporating responsive design principles) soon to follow, but they have already implemented the viewport meta-tag I recommended for our popup/fallback cart as used for mobile devices, so the cart display on such devices is now notably improved (to the extent it could be readily improved, short of radically restructuring the cart itself).

8 months later

I apologize for the delay in replying to your request for an update on the status of this matter. I'd just reminded Development a couple weeks ago about the responsive cart improvements I'd proposed and was waiting on a followup from them, or some face time to discuss it with them, neither of which have occurred yet, so I've remind them about it via email again today.

2 months later

Any new news

With google making mobile friendly very important we need a functioning mobile friendly cart

Unfortunately, I cannot predict when Development will be able to implement the responsive cart improvements I prepared for them.

1 month later

As starter of this thread I appreciate the improvements to the mobile cart. We've been extremely happy with eJunkie since day one.

4 years later

Responsive design is incredibly and badly needed on this platform if it going to be sustainable. We are talking about user experience here. Now that we are almost in November of 19, I've been thinking all along that within a few months of the first of this year that it would be a non-issue and life would be good.

So can you guys please come clean? (technically speaking) Will this issue be resolved this year? A simple yes or no will suffice. I'm not attacking anyone. I am simply building a business and have been building my business based on the functionality of E-Junkie and it's fit for my vastly growing network of affiliates.

The scary thing for me is that I'm afraid I'm going to have to go back to college and learn code just to stay alive or drive people away because of the level of difficulty of their user experience.

So, seriously, what's the scoop here?

Looks like you replied to a very old thread from 2015. Since then, much progress has occurred in our mobile-responsive design implementation:

Our new responsive cart v.2 entered public beta testing in February 2017, was significantly improved later that May and ended its beta phase to became the default cart for all new clients, then was overhauled yet again to an all-new responsive cart v.3 back in March of this year, which became the standard cart for all clients, new and old alike, effective this past June.

If you are not seeing our responsive new cart in your site, you may have taken steps to deliberately override it with our classic cart v.1 if your site had issues with an early beta version of the new cart, or if you were using cart-customization code to alter the appearance of that classic cart v.1 (most of which the new cart v.3 now supports via other means, with settings in your Dashboard). Make sure the E-junkie Cart Script code in your site's sales pages load our standard box.js cart-overlay script, rather than the box_fb_o.js alteration you may have made to force-load the classic cart v.1. This is our standard Cart Script code you should have in your sales pages to display the responsive new cart:

<script type="text/javascript">function EJEJC_lc(th) { return false; }; </script>
<script src="https://www.e-junkie.com/ecom/box.js" type="text/javascript"></script>