Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a quick question about "mobile". I must add the mobile version to my website and I'm exploring all the solutions. Here are my choices:
1) Add media queries to css and trasform my fixed layout in a responsive layout.
Good: one layout only, code for Google bot is the same
Not good: code is heavier, on mobile I load all the js and CSS, impossibile to go to the desktop version
2) Rails 4.1 Variants
Good: i can create a lightweight mobile website, I can have desktop version, I can optimize the mobile experience, using the layout I can also create mobile apps with Cordova
Not Good: the HTML for the same page is different for desktop and mobile. I'm worried about SEO
Any idea?
There is no single best way. The answer depends on your specific needs and case. This is mostly an opinion-based question.
Both solutions are correct. However, the main difference is that the case (1) is more limited compared to case (2). The CSS-based layout makes sense when you just want to make sure the main version works well on mobile devices. It's not a real optimization, because the device will have to load the entire page in any case.
The second option (2) is a real optimization. By providing device-optimized templates, you can skip the pieces that the mobile device doesn't need (such as big images, unnecessary item listing, etc) effectively reducing the weight of the page. You can also inject mobile-specific features.
The SEO issue is a non-issue. You can instruct the search engines to ignore the SEO content using the appropriate meta tags or you can also use the canonical tag if you should decide to provide the content under a different path or domain (for instance if you add a specific extension for the mobile-optimized pages).
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am currently developing an iOS app that can be used by different clients keeping pretty much the same interface for all of them. I would like to make this interface somehow “customisable” without having to change the storyboard for every client but I am not sure how to do so.
I thought that maybe I could have some sort of XML file that would contain the value of the UI elements, modify it and have the app read the value of the UI elements from it at compile time so the final app would contain the desired messages, images, etc.
To make the changes easier I also thought of some kind of “wizard” that would show the UI elements that can be changed, allow me to edit and write them to the xml file and after all that, compile the app from the command line (running a script from inside the wizard).
Is my idea viable? If so, how can I accomplish it or what tool are out there that might help me?
Is there another option that would help me accomplish this “customisable” interface?
Note: this is my first iOS app and is still being developed, I searched for related topics and info but found nothing useful so I am not sure if I am asking even possible to do for iOS or if it is out there under another "name".
Edit: by customisable I mean being able to change the text of the messages, the labels, the banner, the clients img logo, color of some elements and that kind of things.
Edit 2 what I would like is to develop a "wizard" that will modify an xml file and maybe replace some images in my app before it is compiled (that is my current idea). After that I would compile it and all the customisation would be done and the app would be ready for the client.
I would suggest that you look at targets http://www.itexico.com/blog/bid/99497/iOS-Mobile-Development-Using-Xcode-Targets-to-Reuse-the-Code
You could generate your XML file for each "Target", but only include the correct one for each target. Then when the app is compiled it should include all the relevant information. If you are producing multiple apps, you also need to consider that the app bundle Id would need to be different for each. Again Targets handles this
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
EDIT:
This is a very old question, when escaped_fragment was necessary for search engines, but nowadays, search engines do understand Javascript very well, so this question becomes irrelevant.
===========
I was wondering how much SEO friendly could Polymer be.
As all the code is fully dynamic like Angular, how can the search engines pick up the information of the page? Because also doing things in Angular, I really had a hard time making it SEO friendly.
Will there be a tool to generate the escaped_fragment automatically to feed the search engines?
I guess Google may have thought of the solution, but I wasn't able to find it (even on Google).
According to the Polymer FAQ all we have is
Crawlers understand custom elements? How does SEO work?
They don’t. However, search engines have been dealing with heavy AJAX based application for some time now. Moving away from JS and being more declarative is a good thing and will generally make things better.
http://www.polymer-project.org/faq.html#seo
Not very helpful
This question has bothered me also. The polymer team has this to say about it, looks promising!
UPDATE
Also figure it's worth adding some context from the conversation on the polymer list, with some helpful information as to the status from Eric Bidelman.
Initial examination of the structure of the Polymer site suggests that it serving up static content with shadow-DOM content already inlined in the page. Each HTML file can be loaded from the server directly, via HTTP GET, and subsequent navigation uses pushState (documentation) to inject pages into the current DOM if pushState and JavaScript is supported.
It's recommended to use pushState over _escaped_fragment_, since it's slightly less messy, but you'll still need to do regular templating on the server. See The Moz Blog for more information on this.
DISCLAIMER
I may have missed or misinterpreted some things here, and this is just a quick peek at the guts of the page, but hopefully this helps.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm using Sundown on my backend to store and render markdown text. Now I would like to edit this text in a browser with some basic formatting. I'd prefer WYSIWYG but can live with a preview panel on a separate element.
But: I fear that editing on mobiles might just be something that one should avoid and fallback to basic text editing. This will be annoying to the non-techie users if we force them to learn Markdown just because they want to "Enter pretty text on my iPhone"... :-/
I've been looking around at some editor components and at the moment I'm testing CKEditor. Works fine but seems to be a bit buggy on the iPhone (at least the version I'm testing). Did not find a way to force it to only edit Markdown.. yet.
Another one is TinyMCE. Back in 2010 it seemed the same story when it came to mobile devices... just wondering if it's still the case today. It seems to work ok on my device but the layout does not seem optimized for small factor screens... sigh.
Thus:
I think that a basic editor can work on mobile devices, but I've seen that some sites disable this and gracefully fall back to standard text edits (As StackOverflow does when visting from an iPhone device)
I just need basic formatting with bold, underline, Header 1 etc and keep the format Markdown - like the SO editor
Any suggestions or comments?
tinyMCE version 4 actually works just fine on my iPhone, I've put together a small scaled down example for you on their fiddle-site:
http://fiddle.tinymce.com/Ppdaab
I highly recommend https://stackedit.io/. It converts html (or text) into markdown and doesn't require using Git. You can access it on their website or using the Chrome app. It's lightweight and completely WYSIWYG. Simply type away, it will show you a preview in markdown format. You can then save, publish, share, sync or download the file.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I know it sounds crazy but I'm sitting here with various phone on different networks and all the phones on the sprint network are failing to work correctly.
It looks as if the LESS style sheet is not being applied. Has any one ever ran into any thing like this?
Also just visited the LESS website figuring all there styles would be created with LESS and its doing the same thing. Failing to load/apply the LESS.
The specific phones I have tried on the sprint network are two iphones and one android optimus V.
I would strongly suggest pre-processing your LESS file into CSS and serving that on your site.
It is considerably more efficient as even a medium sized less file can take hundreds of milliseconds to process during page load. It is also one less javascript file to download in production. Finally, it is a lot less processor overhead on mobile devices that need to not only parse the javascript, but then parse the less file as well. Some mobile devices don't have caching or local storage so there is a potential for them to be re-processing the less file every time the page loads.
Either use the lessc compiler (requires Node.js) or SimpLESS to pre-compile your css files.
You could try to see if it's blocking the download of the less javascript or the stylesheet itself by loading their URLs directly.
For lesscss.org that would be http://lesscss.org/less/main.less and http://lesscss.org/js/less.js
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
We have different forms of documentation for our desktop apps, but until now most iOS apps have been fairly self-explanatory so we've been able to get by with simple hint strings in settings etc.
But for a more complex app I'd like to be able to create a few HTML pages that look approximately like native iOS UI and are easy to maintain.
Dashcode has a browser template that seems to fit the bill, but it's terribly buggy under Lion. I could start from scratch using something like iUI, but I'm wondering if there isn't something readymade already out there that would fit the bill?
Requirements:
- One or possibly two levels of hierarchy
- Display short formatted text with images
- Preferably HTML so the documentation authors can create and format the content on their own without touching the dev side of things
Any ideas or tips would be appreciated!
I use CSS formatted HTML pages that can either be included in the project or served from the web or actually both (you can do a check so see if the app has a connection to the server and if so serve them up from there or serve them from a local resource).
I personally think the Static Cell UITableView is the ultimate way to display those help options. That and Storyboard were the two big favorites for me in iOS5.