OXID Community Forum

> Archive > Redesigning the OXID eShop default frontend > Redesigning the OXID eShop default frontend
Login
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Thread: Redesigning the OXID eShop default frontend


Reply
 
Thread Tools Search this Thread Display Modes
#Top   #1  
Old 02-05-2010, 10:16 AM
Andrea Seeger Andrea Seeger is offline
Junior Member
Join Date: Jun 2008
Posts: 22
Andrea Seeger is on a distinguished road
Default Redesigning the OXID eShop default frontend - some food for thougth

We’d like to invite OXID partners, shop owners, developers and eCommerce experts at large to discuss with us the objectives and requirements of the next generation OXID eShop graphical user interface that caters end users.

Here is some food for thought:

1) Consider technologies as part of an enhanced templates set providing a rich user experience, e.g. through AJAX and Flash.

2) Additionally, provide a stripped-down templates set for customization from scratch or to serve eCommerce scenarios that must conform to simple technical requirements.

3) Meet diverse global expectations in usability by shop visitors as well as world-wide eCommerce standards.

4) The default frontend is supposed to render various types of products.
For example, tangible products as well as digital products (for download), or visually appealing products mainly being marketed with images (such as fashion items) as well as gadgets where a shop will provide more text, e.g. tech specs.

5) Having said that, the new default frontend should of course also be flexible enough to sell products from various industries, e.g. fashion as well as car parts.

6) Let's make sure the default frontend serves the main purpose of an online shop: provide a sales and marketing platform for strong brands.
We intend to value this goal higher than any technology that will not serve this purpose, no matter how cool it is.

We initiated related threads in this forum. For the first phase of evaluation, please provide your best practice input until end of February. You can share with us your criteria for successful shop designs, show us your analyzes of successful shops and let us know what the convincing keys are.

We’re looking forward to get this going with you!

Last edited by Andrea Seeger; 02-05-2010 at 10:21 AM.
Reply With Quote
#Top   #2  
Old 02-13-2010, 04:48 PM
cpjolly's Avatar
cpjolly cpjolly is offline
Member
Join Date: Jun 2009
Posts: 74
cpjolly is on a distinguished road
Default AW: Redesigning the OXID eShop default frontend

As well as asking for recommendations from the developer community, I think there is also a lot to be learned by taking a close look at the capabilities and user interface of other modern platforms, such as Wordpress MU.

After using a lot of different platforms for a wide variety of client project types, my observation is that you need to provide 2 very different types of capabilities: one for the developer community and one for their clients.

For the developer community, it really doesn't matter what solution you provide, so long as they have full control. Smarty templates and the OXID management interface are fine for this - yes they could be improved, but they do the job.

The clients (i.e. the developer's customers) are usually much less technically sophisticated, but they still want to do their own basic customisation without running back to the developer every time. I find that my clients are happy to work with the management interfaces of platforms like Wordpress MU, iGoogle and SharePoint. They understand how to select options and move items around on the screen, but they are completely lost if they need to edit a css file etc.

Clients are also often looking for more than just a webshop. Many of them are looking to upgrade the whole of their web presence, of which the webshop is one part. Again, something like Wordpress MU offers a lot more flexibility than OXID, with it's add-on modules from which to build for example a community website. Perhaps an option would be to provide an OXID interface via a Worpress or OpenSocial module.
Reply With Quote
Reply

Bookmarks

Tags
default, eshop, frontend, redesigning

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Nicht Sichtbar
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Express-Kaufabwicklung über OXID eFire in meinen OXID eShop einbinden Nafissa Khayar OXID eFire 0 04-09-2010 10:11 AM
Actual forum discussion about the redesigning of the OXID eShop default frontend Andrea Seeger OXID Announcements 0 02-08-2010 02:27 PM
New extensions for OXID eShop available: OXID-to-Sugar Connector, Celebros and Template Sets Marco Steinhaeuser OXID Announcements 0 09-21-2009 09:14 AM
Frontend von OXID shop unter XAMPP mdmnet Installation und Konfiguration 7 06-29-2009 09:14 PM
Update OXID eShop PE 3 to OXID eShop PE 4 Roland Fesenmayr OXID Announcements 1 11-03-2008 06:32 PM

All times are GMT +1. The time now is 03:35 PM.