Tested on my Ipad. The responsive feature works. I guess we will be able to remove the right column and choose the responsive menu items. I like the "story" dropdownlist, The notifications have disappeared :-(. It's probably my most used feature (a sort of what's new). Maybe except the width, IT'S GREAT!
Never mind ... several refresh and cleaning browser cache helped me to get rid of above mentioned issues...Please ignore my earlier comment.
Only problem is see now is ...composer story button displays small menu (Story , Photo, Page) only when clicked on white space on button. If I click on + sign or down arrow or text 'Story' it doesn't work
As we've said before you can't just make a social network mobile friendly by making the template responsive. Anahita needs to render a more simplified and limited version for the mobile browsers. Even then the performance will never be as good as a native iOS or Android app.
Actually, I was surfing Anahitapolis today on my phone and it seemed much snappier. Though, I did notice a strange behavior. As I scrolled down on the Dashboard, I noticed that my scroll bar quickly got smaller and smaller and higher, the page became very long. Several weeks of posts had been loaded before I had even finished looking at the first few. I have a feeling that infinite scroll is not working as it should on mobile devices or, at least, just mine. :P
@Nick I think I know what is causing that behaviour. Anahita preloads records on the InfinitScroll and that preload is triggered within a specific range. On smaller screens you are always within that range. We should perhaps calculate that range based on a percentage of the container height. That could fix the issue for the smaller screen. It's a hypothesis but I'll put it into test.
Great stuff, have only viewed this one post so far, but it makes things so much easier to have a responsive view. I use Anahita perhaps 95% mobile and it already feels far more usable and less of a chore. I'm sure there is more to do to uncover the little changes to make things work smoothly on a mobile now that people are using it en masse, but great start!
I think by the way that people know what to expect from a responsive site versus a native app - in my experience they tend to compare the experience with using another similar responsive site rather than with a native app as they are such different beasts, and even non-techies appreciate that. Just making things fit the screen and eliminitating bugs resulting from use on different devices is all people generally expect... Using methods such as mobile-specific views based on JSON to maximise performance are the icing on the cake and are well worth it once a site is mobile-usable, especially if a native app is not yet available, unaffordable etc.
The main issue for me with native is the fact that you can't just build for iPhone, or even iPhone and Android - you've now got Windows Mobile which is likely to begin to take off now judging by the numbers buying it in the shops this Christmas (a personal observation not statistics). Unless a simple way of building multiple native apps can be found (there are some ways around this such as HTML5-based native apps), a small site can only realistically provide a mobile experience for all its users by going down the HTML/web route. I'm still undecided as to how to deal with this...
Responsive theme for a CMS isn't the same as a responsive UI for an application environment. A CMS layout is far less sophisticated than an application UI because you are essentially rearranging a collection of static elements. Anahita is an application environment and there are many areas that need to be worked on to achieve a better mobile experience. This will be a continuous process. There is no doubt that in the post PC era, having s responsive UI is a must, though judging by the existing technologies I don't think the performance and experience will ever be as good as native mobile apps,
@Rastin: I agree. In particular, I would like to emphasize that the menu for an application environment is something already solved (at least conceptually)... right there, before our eyes: Mac OS.
In my opinion even in a web application environment, the main menu should change according to the current application (pages, todos, photos, etc.) - both on PCs and mobile devices, but with different interfaces.
@Rastin...you are absolutely right. Now I understand why we should have different themes for different devices. If you want to know my opinion then again we should take out the responsive-function to get back the fast loading and working experience. The system-freeze is not nice.
Since Anahita is limited to 940px of width it makes no sence to have the responsive theme on the PC and tablets. And for mobiles and devices similar to Ipad-mini we use a different theme.