Is it possible to have different implementations for Phone and Desktop? - reactjs

I understand that different layouts can be designed for Mobile Phones and Desktop Websites. But is it possible to implement two different approach implementations for Mobile Phones and Desktop.
For instance, is it possible to have one page designed as drag and drop for websites
and the same can be designed as,
select stepwise for mobile phones.
Any clue or library or implementational approaches will be greatly appreciated. At the last, i am trying to implement the same website page in ReactJs.

You can have Platform specific code with different file extensions as follows
dragndrop.native.js//mobile platform
dragndrop.js//web platform
More info here Platform React-Native Docs

Related

Mobile emulators

I'm developing a new Responsive layout for different smart phones, tablets etc, so i require a single emulator to test for all the devices. Like to know if any one have used any thing.
Note: I have used media queries and flexible layout for my design
First i would recommend you test your applications/websites or real devices.
If it's not possible for you to get those then there are few suggestions.
Opera Mobile Emulator ( It provides significant varieties of different view-ports. You can also test on your own custom View-port.)
There are some online tools also to test your websites/applications.
Responsinator ( Just put your live URL there and get your website's responsiveness on different devices' view-ports. )
Hope you'll have better ideas.

Desktop Browser to Mobile Browser?

I already have a website with huge database which is good for Desktop browser my site is on Joomla base. Now i want to develop for Smartphone (like iphone, android, nokia) and mobile browsers. So how can i achieve this goal what is the best way of doing this.
Mobile Sites like Yahoo, Youtube i want to developed something like this because i'm new to developing mobile sites so any one can suggest me the right way for developing the mobile version for my current Desktop Site.
Thanks in advance
There are extensions for Joomla that style your site for mobile usage here: http://extensions.joomla.org/extensions/mobile.
It makes sense to test your site using the emulators for iPhone, Android and Symbian at some stage before you release. Each software development kit includes the ability to use the mobile browser.
Note that this is not the whole story. You'll want to consider:
Mobile users have much smaller displays. You'll need to rework your UI to take account of this.
Mobile users have large fingers. You'll need to rework your buttons and links to take account of this.
Mobile users tend to consume content rather than create it. Optimise accordingly.
Searching for data with e.g. traditional search boxes is tricky; you may need to rework to use scrolling through lists.
Above all: test, test, test!
Have a look at http://www.mobilejoomla.com/

Mobile Development: Same or Different Sites?

I am considering developing a mobile edition of a web site for an application, and I'm considering whether to revamp my existing site to work for mobile, or create separate web sites. It seems to me even though some tout the benefits of CSS's capabilities, separate web sites is the way to go. Although devices like the IPAD and other 10" devices can support a full screen view, handling support for a limited view for devices with a 4" or 7" screen is a good way to go?
Factoring in phones, tablets, notebooks, and other third party devices, do you think its possible to use the same site across web and mobile environments, or definitely consider a separate site?
Ultimately, this will come down to the individual preferences of your site's visitors.
Personally, when I visit a site on my phone, I get annoyed when I'm automatically redirected to some mobile version. When I access the site in such a manner, I'm usually trying to look up something quickly -- not looking to learn how to navigate around an essentially different site.
So, I would say that if you do design a different site for mobile users, attempt to stay true in some ways to your original layout, and don't vastly change the reorganization or URLs.
Having said that, I'd still say the better route would be to change your current design slightly so that it works well on both. Good luck.
Factoring in phones, tablets, notebooks, and other third party devices, do you think its possible to use the same site across web and mobile environments, or definitely consider a separate site?
Absolutely, yes. Lots of great examples at http://responsivewebdesigns.tumblr.com/

How to adapt mobile site for different mobiles?

I am developing a mobile site for iphone, and i want it to be used in other mobiles, for example, gphone, blackberry, sumsong, motorola etc.
what should i do for adapting the mobile site for so many different mobile devices?
Thanks for any advice.
Unfortunately I do not think there is an easy answer to this, other than to say that the simpler you make your mobile site the more likely it is to appear correctly/consistently across multiple devices/networks. You also need to consider the 'app' mindset with iPhone, where something that previously might have been presented simply as a web site, is now frequently presented in an app instead. Finally, bear in mind that many phones do not support flash (iPhone famously..), silverlight, javascript etc. If your site loses too much of its look and feel without these than you may have to redirect to targeted sub-sites per phone type.
See this similar question which may help you get a feel first for how your web site looks on different devices and in different networks:
Testing Mobile Sites
If you do need to change the look and feel for different phones, then you will need some way to detect the phone types - there are many articles etc about this which you should be able to find with Google - for example:
http://www.hand-interactive.com/resources/detect-mobile-php.htm
Again, it would be good to test whatever one you use in your target network to check it works as expected (operators may use devices, for example proxies and optimisers, which may affect how things arrive at your webserver or phone...).

Which platform is used in companies now-a-days to implement mobile applications?

Basically i would like to know which platform is currently used to develop mobile applications i.e. J2ME etc etc...
Also any new ideas on mobile applications would be quite helpful.
Generally, the approach is to go for a website, if possible, and adapt it to each phone using a 'device detection layer'. We use DeviceAtlas.
If you want to write native applications for each phone, then you need to do it in each of the native languages (and there are a lot).
Symbian/Java: Greatest 'penetration'
iPhone/iPod Touch: Latest trend, objective-c for this.
Android: I think this is a variant of Java, and will be a very marginal component of the market for a long time, though maybe high among a certain type of techies.
Basically, you are going to need to profile your market, and determine the best approach. But as I said, in general, you'd prefer a website, and mostly, a website is all you need.
There is a framework called Rhodes by Rhomobile that allows development of native applications for all major smartphones. See my answer to a similar question earlier this year.
We are primarily targeting the iPhone, but don't always make an iPhone-specific application. The web browser on the iPhone is good enough that a lot of our web apps just run there ok. So many of the apps we're writing continue to be done using the same platforms we've always used. We're a big institution so this runs the gamut from J2EE and .NET to Php and Ruby.
Mobile-only apps are developed in XCode (or web versions in DashCode).
If you need to cover multiple mobile (esp. smartphone) platforms, Javascript (with HTML and CSS) may be the only way to go, despite all its limitations. You get under the radar of Apple's iPhone app vetting, it's the only way to target Pre, you can also cover Blackberry, Android, Windows Mobile, AND Nokia on a single codebase... unless the limitations are just TOO stifling for your specific purposes, it sure seems like the way to go!

Resources