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 9 years ago.
Improve this question
Responsive web design (RWD) is good for admin side (control panel) of web design?
I have more entries and tables in my admin page. so RWD is good for admin development?
Also it is good for develop mobile application for admin forms?
If you know Responsive Web Design as 'Fluid and adaptive layouts with progressively enhancing features', then I think it's probably safe to say that yes, RWD is good for almost any web project. Be aware however, that building responsively is much more difficult and time consuming (read: expensive) and may not offer the necessary ROI that you need.
For example, consider that much backend software like cPanel and such are used by technically skilled people that understand how to resize their browser and work with less-than-polished software.
Also, when you think about cPanel, you must consider whether much of the utilities and functions it provides are efficient and useful in the mobile context - I doubt that sysadmins really want to do module installation or type large amounts of console code with an iPhone keyboard.
So when considering the merits of RWD for backend web software, be sure to weigh up your target audience, their skills and requirements, their equipment and what (and how) they will use the tools available to them to get things done.
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 9 years ago.
Improve this question
I have no prior knowledge on Mobile application development so these might sound a naive question. Basically my requirement is to develop an application that will work on multiple platforms like Android, Blackberry and iOS. Hence, I wanted to know how well is Worklight suited for the job. Basically I wanted to know:
Q1: What are the technical or functionality concerns of Worklight that one should know before going for it.
Q2: Is it better than PhoneGap?
Q3: What are the basic skill sets required for a person to work on Worklight other than Java.
Q4: Are there any Hardware requirements that might be specific to Worklight applications and might cause the developed mobile app to not function on the phone?
I would be grateful to anyone who could help me out.
Thanks in advance.
You must buy a license if you intend on going to Production; the free Developer Edition may not be used for that purpose. It's not for individuals or small businesses, but for medium to large businesses. Other than that, it depends on your end goal.
Worklight cannot be better than Cordova in the sense that Cordova is bundled within Worklight. So anything you can do in Cordova, you can do in Worklight and add on top of this all the features that Worklight provides you with (and for this, please, just take a look at the Worklight website and Information Center).
You need to know HTML, CSS and JavaScript at a decent to very good level. If you want more, you need to know languages such as Java, Objective-C, C#.
No.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
We've made this monitoring tool at our company.
It's not in our line of business so we might as well opensource the tool, and maybe someone else likes it as well, maybe they'll contribute.
The tool runs on AppEngine, so there are so the are some paths in the appengine configuration, that might be a good idea to keep hidden. Unless someone else wants to start using our appengine qouta.
Is there a best practice for open-sourcing AppEngine applications?
Does anyone have any experience to share regarding opensourcing appengine sites?
You can get some ideas from excellent gae-init. The way its working in order to avoid exposing sensitive information, is moving it in a stand alone project, you can even use gae-init for that ;)
As part of the model is a Config class which holds all the information as it concerns the service and its dependencies. There are some default values there but it can also be easily customized from a web interface called admin. Have a look.
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 9 years ago.
Improve this question
What is the best way to design a website and integrate web design for mobile devices within that website?
I heard the best solution is to simply create a separate CSS file...or redirect to another page that is designed for mobiles...
And are there any tools out there that make this task easier?
A lot depends on the complexity of the site. Many times your best option is to redirect to a mobile specific site. Frameworks like jQuery Mobile can be very useful.
There are multiple ways to achieve this.
You can use responsive CSS media queries to make the same page look different on different device sizes.
In case of standard CMSs like Wordpress/Drupal, there are plugins and themes which automate this for you.
Or you can use a third-party service like MobStac for Developers or Mobify to create a mobile version of your site.
Responsive comes with its own set of limitations; for ex. the markup and content being served to all devices is the same. It does not result in a lighter or faster site by itself. You should look at adaptive instead of plain responsive if you want an optimized experience across devices for your site visitors.
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 4 years ago.
Improve this question
I'm going to create mobile version of website...
What width should I choose for design? I know that every device have it's own screen width and it's really difficult to fit all devices...
I'm really confused (pretty new to mobile websites world), please help.
Thank you.
Your approach will depend on how much effort you want to (or can) put into this and what range of mobile users you want to target. For minimal effort, simply use 100% as KennyTM points out and expect your website to be browsed on screen widths from 128px to 480px . With this approach, you'll also need to avoid 'advanced' xhtml directives such as css and divs (and javascript) because most mobile browsers cannot handle some aspects of these. Plan to use tables to manage layout.
For a more advanced approach, you can use an open source project called WURFL (http://wurfl.sourceforge.net/) which is a database of mobile browsers and their capabilities (screen width, support for div, css, images etc...). It has a jsp tag library called WNG where you write once and the tag lib will render the most appropriate html to match the user's device. I believe there is also a PHP library for this.
Rgds, Kevin.
For this sort of question, I can highly recommend reading the MobiForge developers' guide. Lots of useful advice in there, including how to pick the compromises that inevitably result from mobile development.
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 4 years ago.
Improve this question
I'm evaluating DotNetNuke for a project in which an offshore team is going to be doing the development. In short, the application will be a community blogging platform with many similarities to stackoverflow except no questions, just posts. Posts may include an image or video, tags, use info, title, body, community vote (up or down) comments, hotness, and a few other details. They should be taggable, sortable, categorizeable (beyond what a single set of tags provide) In the future the site will carry forums, a calendar, and a couple of other features for which there are modules available for DotNetNuke. Additionally, this site will incorporate a user experience that will include a lot of custom skinning.
Thoughts?
Using a web application framework (such as DotNetNuke) has a ton of benefits to help you get up and running faster and do less work when creating custom functionality.
However, you have to realize that you're basically incorporating tons of code into your project that you may not be familiar with. No matter how good the code is and how easy the framework is to learn, there's still going to be a significant learning curve for you and your team.
Your decision making process (if you're still deciding whether or not to use DotNetNuke), should include (in addition to reading, talking and other general investigation):
Downloading the application from Codeplex and checking out the source.
Investigating the third party modules that are out there.
Downloading a free module or two that comes with source, and try to reverse engineer the creator's development process. How did she integrate with the framework, what features did she take advantage of, what was written from scratch?
One place where DotNetNuke (or any other framework with tons of extensions) available can really shine is taking existing extensions that are available and customize them. If you need to implement a given feature, check out the solutions in the third party extension community first. You can probably find one that gets you a good percentage of the way there and use it as a foundation for your feature.
For example, if you want a photo gallery on your site, you probably don't want to write it from scratch. There are three major photo galleries out there that sell the source code. The core gallery module is free, simple gallery is cheap, and the source for ultra media gallery is available for a reasonable amount compared to writing it yourself. Any of these could give you a good head start in implementing your features.