Supporting the Multi-Device User.
If a customer is visiting your site looking for information or using a specific feature, and they return later on a different device but cannot find that same information (perhaps because you decided to not include it on a “mobile-only” version of the site), then you run the very likely risk that that person will simply leave your site and take their business elsewhere. By ensuring consistency of information across all devices, but with a layout and experience suited to each individual screen size, you do your best to support your customers and do not give them any reason to abandon your site halfway through their overall experience.
One Site to Rule Them All.
It’s hard enough to keep one website updated and relevant. Trying to keep multiple sites up to date and consistent with messaging is even more of a challenge. This is why a responsive website is much preferred over separate websites for desktop displays and mobile phones.
One Website, Many Devices.
One of the most appealing aspects of responsive web design is that a responsive website can provide a great user-experience across many devices and screen sizes. This is an important characteristic, since it is impossible to anticipate all the devices and screen sizes searchers will use to access your site. A site that works well regardless of these variables will provide a better and more consistent user-experience than a separate mobile site that is designed for a specific device and screen size.
Future Scalability.
One of the best things about a responsive website is that this approach gives you the best chance to support newer devices and screens in the future. Responsive sites are fluid, scaling up or down as needed to best fit the screens being used to access the site. This means that as new devices hit the market with screen sizes unlike what we have seen before, our responsive websites will already be prepared to meet those new devices with a design and experience best suited to whatever screen sizes they throw at us.
Figure 3.7 Desktop view.
Figure 3.7 Tablet view.
Figure 3.7 Smartphone view.
4. Implementation of the project
As a result, the system contains 9 controllers:
IndexController:
Responsible for displaying the home page. It caused virtually all database tables in one function, and all data are transmitted to the “dashboard” model.
<?php
namespace
App\Http\Controllers;
use
App\Blackboard; use
App\Chat; use
Illuminate\Http\Request; use
App\Http\Requests; use
App\User; use
App\Project; use
App\Task; use
App\Client; use
Illuminate\Support\Facades\Auth;
class
IndexController extends
Controller {
public
function
index()
{
$managers
=
User::where('position',
'Content
manager')->lists('name',
'id');
$designers
=
User::where('position',
'Designer')->lists('name',
'id');
$programmers
=
User::where('position',
'Web
developer')->lists('name',
'id');
$projects
=
Project::lists('title',
'id');
$projects->prepend('No
project',
'0');
$bbitems
=
Blackboard::where('onboard',
'1')->get();
$tasks
=
Task::where(['completed'
=>
0,
'user_id'
=>
Auth::user()->id])->get();
$client_lists
=
Client::lists('title',
'id');
$chats
=
Chat::orderBy('created_at',
'desc')->take(50)->get();
return
view('dashboard')
->with('projects',
$projects)
->with('managers',
$managers)
->with('designers',
$designers)
->with('programmers',
$programmers)
->with('bbitems',
$bbitems)
->with('tasks',
$tasks)
->with('client_lists',
$client_lists)
->with('chats',
$chats);
} }
namespace App\Http\Controllers;
use App\Blackboard;
use App\Chat;
use Illuminate\Http\Request;
use App\Http\Requests;
use App\User;
use App\Project;
use App\Task;
use App\Client;
use Illuminate\Support\Facades\Auth;
class IndexController extends Controller
{
public function index()
{
$managers = User::where('position', 'Content manager')->lists('name', 'id');
$designers = User::where('position', 'Designer')->lists('name', 'id');
$programmers = User::where('position', 'Web developer')->lists('name', 'id');
$projects = Project::lists('title', 'id');
$projects->prepend('No project', '0');
$bbitems = Blackboard::where('onboard', '1')->get();
$tasks = Task::where(['completed' => 0, 'user_id' => Auth::user()->id])->get();
$client_lists = Client::lists('title', 'id');
$chats = Chat::orderBy('created_at', 'desc')->take(50)->get();
return view('dashboard')
->with('projects', $projects)
->with('managers', $managers)
->with('designers', $designers)
->with('programmers', $programmers)
->with('bbitems', $bbitems)
->with('tasks', $tasks)
->with('client_lists', $client_lists)
->with('chats', $chats);
}
}