Hey there,

unfortunately I got the same problem with the delay at switching to mobile view. It is too bad because only because of this delay I had to buy the app over at Appcarvers becaues my users are very low on patience.

I had started a thread about this topic here in case you are interested:
http://stackideas.com/forums/delay-on-mobile-before-switching-to-mobile-view

Hey lan,

I am sorry for the delay of this reply,

Actually that was known issue, we are still looking for the better solution for this, but I would recommended you to use Easysocial mobile app so it will not getting slow page render issue. Because this Easysocial mobile app was developed by partnership AppCarvers.

http://appcarvers.com/stackideas-appcarvers-promo/

You can download from here :
https://play.google.com/store/apps/details?id=com.techjoomla.easysocial&hl=en
https://itunes.apple.com/us/app/easysocial-for-joomla/id922884839?mt=8

By the way, thanks for sharing Sabih

Hi Sabih and Arlex,

thank you for the quick response. This is indeed a problem...:-( I will be very glad if you solve the problem as soon as possible. Smartphone and tablet here have almost everyone. We have many approaches to the our website via mobile devices (according to statistics from our website). Surely you have your road map, but please to find a solution. This problem we don't have with any other extensions.

about Appcarvers:
I tried this app to download and install. I was scared , but it looks interesting. Thanks for the tip.

Sabih, what are your experience with this application? Speed, freezing, etc. It is possible to "your" application to download and try?

Once again, thank you for your answers and help.

Have a nice day.
Best regards
Jan

Sabih, what are your experience with this application? Speed, freezing, etc. It is possible to "your" application to download and try?

I bought it but it is not yet ready to use. Many bugs, many things missing. They are working on it but honestly I would prefer a fast responsive website over the app for sure!

There are more people who bought the app already, they share their experience in another thread here:
http://stackideas.com/forums/easysocial-mobile-app-thread-v4-1

I can only agree with most of them. I appreciate the work of the developer of the app, no doubt about it, but I also have to admit that I am not convinced of the app itself and bought it because I had to...

Thank you for the link.

If I want to have own social network (eg. from EasySocial) is for me problem this delay. It's not a small thing, it is at first glance a mistake.

This application (Appcarvers) I see as a bonus, something extra. It is certainly necessary this problem on EasySocial removed. Why? Two applications (EasySocial and Appcarvers) generate twice as many potential bugs. I can not imagine how many people will use this app, but I think it will not be even one percent. We are not and never we will not be Facebook. For Facebook, similar application is understandable, but for our "social networking"?

I've done your research. I asked about 10 people (colleagues and family) to tell me opinion on this problem. When they saw the delay, absolutely everyone said it was bad. Today is not year 2010.

What to do? EasySocial looks nice. I believe that guys from Stackideas correct the bug. Soon :-)

I have worked with many developers so far and I can not say that Appcarvers are bad but I have to say that the app is far from being a replacement for the website itself. As I said before there are still many things missing in the app.

Additionally I MUST say that Stackideas is the by far best developer with support I have ever worked with. I can agree that the delay is bad, no doubt about that fact. But I would strongly suggest going with Stackideas instead of any other developer for the support.

I am not sure yet if Appcarvers are not behind their product with all of their heart or they made the mistake of publishing it too early. My hopes are that it was just too early and with time they will have a great product too.

Hi Guys,

I am really sorry for the delay of this reply.

Can you try to download my attachments below and place it inside the respective file path below and see how it goes?
/media/com_easysocial/scripts/responsive.js
/plugins/system/easysocial/easysocial.php

Hi Ezrul,

thank you very much for your effort, but for me there was no difference so far. I recorded the effect so you can see it how it looks on my mobile. It is recorded with a OnePlus One at home in WLAN with 50mbit internet connection.

https://www.youtube.com/watch?v=hdJDqXkc51E

You can see after reloading the page, the posts of my members are already there but it takes many seconds until the layout switches to mobile view. Your patch was already uploaded before this recording.

Forgot to say I am still on EasySocial 1.4.1 maybe this is important.

Hi Sabih,

Can you try using the attachment below instead and see how it goes? Place it inside your /plugins/system/easysocial/ folder.

Hi Ezrul,

thank you very much for your help. Files responsive.js and easysocial.php I tested. Now it works better. But I tested EasySocial a short time. On the test I created about 10 posts (text, photos, videos). The delay is still, but smaller.

Have a nice day.

Best regards, Jan

Note: But I do not know how it will look when there will thousands of reports, thousands of users, other template, other extensions etc.

I agree that it works better but not good yet. I have to admit that I am not sure if the delay is because of EasySocial only. It is hard for me to specify if it is about the component or about the template.

I am very thankful for your support Ezrul, thank you very much.

Hey guys,

Just to keep you in the loop, we are still trying to find the best way to speed up the detection of "mobile screens". What is actually going on behind the scenes is extremely tricky. Let me just try to explain to you guys briefly of the problems that extensions like us face:

ISSSUE #1
1. We cannot determine if your Joomla template is mobile ready (The biggest fail of all)
2. Because of reason #1, we had to take this into our own hands and rely on detecting the width of the screen.
3. To do that, the only way is to use javascript because there is no way to determine screen size in php (which introduces the next set of issues)

ISSUE #2
1. Because we have to rely on javascript to determine screen size, we also need to rely on a lot of other libraries (jquery in particular)
2. Because we rely on jquery, we need to add our own dependency layer
2.1 What if joomla is not loading jquery.
2.2 What if your Joomla template explicitly does not want jquery.
2.3 What if jquery was loaded after the extension loaded.
3. Because of #2, we resulted in creating "foundry" which is a dependency layer by itself escaping all the conflicts above.
4. Because of "foundry", we have to wait for jquery to be available to our responsive script to kick in.
5. When foundry / jquery is available, we then perform the screen checking sizes and only then the layout get's adaptive.

Okay, enough of my rants The only solution right now is to inject a snippet of the code to the head of the site (that does not rely on jquery / mootools . Having said that, you will still notice a very slight delay because the following codes were injected on the head of the page:

The script still needs to wait for the complete DOM to be loaded before it is able to inject the necessary classes to it. The ideal / best way to fix this is to add your css media queries on your Joomla template's css file but this again opens up another can of worm because not all template supports this

Hey Mark,

thank you VERY much for this extended description of the problem. As a non-programmer I find this very interesting and helpful for understanding the problem. I think understanding the problems of the background gives very much understanding for waiting for the solution to take time.

The only solution right now is to inject a snippet of the code to the head of the site

At first glance I thought, I will try it, second time I have to admit, that I have no clue where to put this snippet. I tried to put it with gantry5 framework into the head properties but that did not work.

I think I have to say that I thought it might be way easier as it is. Nevertheless I am very thankful for your explanation even though it gave no solution I know that you would give us a solution if you were able to.

Hey Sabih,

The best solution that we have right now is what Ezrul already provided with the system plugin where it injects the javascript on the < head > portion but there is still a slight delay because the script can only execute when the entire html elements are rendered on the page.

Hello,
I want to ask, there is already solution to this problem? The latest version still has the same delay on the mobile device The same is true for your demo...
New features are great, but this delay and deformation is a big problem.
You looking for solution to this problem ???
Thanks for the reply.

I have already outlined the problems above and this is not something that we can fix immediately. You can add the js codes above into your template's index.php file under the head section.