Live webapps run in the cloud. That's where our high performance native code lives, only our user interface is in the browser. We built our browser hosted admin panel so that our adminstrative user types can control whats going on in the cloud. The level of access and control is dependent on your user rights. Normal signed up users or guests, of course, have no access to this functionality. So, privilege allowing, admin users can control our cloud webapps to the degree of their authority. Let's take a look at our user types and their access rights differences.
Our admin panel is split neatly into functionality groupings. Above is the view for an admin mechanic user type, we'll get to the other user types next
Normal & Guest Users
These core user types have no access to the admin panel and are included only for completeness. A guest is a user who has visited a webapp but hasn't signed up yet. A normal user has signed up and can create friendship networks. Guests and Normal users share a similar user experience by design.
Our lowest level of administrative user. Has access to main menu admin functions like web statistics, customer database, take orders, add/update new product and use the live CMS to update webapp literals/text. Admin panel access is restricted to users (manage users at the same level or below) and manage automatic twitter posting. A moderator user can also moderate newfeeds. Moderators can be optionally interactive, meaning that they show online when logged in so clients can converse via instant messaging. Moderators can also optionally choose to receive email notifications about system alerts like sales, newsfeed responses or customer questions. Generally a shop assistant/employee would have this level of access.
All the rights of a Moderator user. Administrator users have additional rights pertaining to webapp configuration. These include system & configuration section to maintain the access PIN code, configure outgoing email settings and configure service API keys. In the social & users section the twitter oAuth keys and secrets can be maintained for the auto tweeter. Full control of the SEO web indexing service to enhance search engine results and build an automatic static website version (mobile friendly) for indexing and rendering in older browsers. Webapp type dependent options, in the case of a retail webapp then the payment options configuration and specific retail configuration like currency, shop location, sales tax, etc. In general a shop owner/director would have this level of access.
All the rights of an Administrator and Moderator user. Mechanic users have addition rights relating to the technical webapp configuration. These include extended system & configuration rights to manage the system, track the connection information and full control over the performance via the thread pool configuration. The errors & logging section provides live alerts on the state of the webapp, both from a client (browser perspective) and a cloud webapp point of view. All errors and alerts are dispatched to the mechanic in the form of alerts or optionally emails. The Database section controls performance related alerts fine tuned to the hosting, slow or SQL syntax errors are reported. There's also an adhoc, interactive SQL client that can store useful queries. Everything a service / coder / mechanic needs to know when the system is performing well or is wobbling right down to the line of code that's causing the issue. Project Peach engineers or onsite technical support would generally have access at this level.
Our user types and filtering inside the admin panel. Administrator privilege users are being shown here
We'd need to be writing a user manual to describe all our amazing admin panel function. So let's go through a few select examples of what we consider to be our nicest and slickest admin function. Remember we can always give you a demo of this at your desktop, we're coders not sales people, so no pressure. Remember that the admin panel is what we consider to be your companies domain. For our centralised error logging we have our Application Instance Manager and our Project Peach Dashboard where we centrally collect ALL mechanic messages to individual webapps. We know as soon as your mechanics know if there's a wobble.
Our security log picks up any unusual activity on our smart connections. We've a initial secret soft handshake and we monitor our incoming messages for type, parameters and length. Anything unusual makes it into our logging for investigation. We can drill down to the detail
Our mechanic users can simulate errors on the fly. They're actual errors that we've coded in that get run in the webapp. It proves that our centralised dashboard, emailing and soft alerts work. We don't wait for them to happen to find it isn't working. We've even got a thread deadlock test in there, yes we monitor absolutely everything possible. It's not just our frontend that improves over time we catch our cloud hosted, native code errors down to the line number in the source. Better than it's broken and where to start? Is that your world?
We've built in twitter promotion via the twitter APIs. Just set up the oAuth details like the ID, tokens & secrets and the interval and bingo 365/24/7 promotion without lifting a finger. It's pretty cool. In our retail version we can finely tune which products to tweet along with images. Using this technique we've managed to build followings of 100k plus without so much as a manual tweet. Remember this is just the start of our social media integration, if there's an API then we can add it. Taking the burden of manual social media once and for all
Cash Clamber specific gaming extensions
Retail specific extensions
As with everything we do we've a hierarchical, layered approach with the admin panel. There's our core functionality that can be specialised dependent on the 'TYPE' of webapp. We can never really break free of our programming object orientated view of the world. So, Cash Clamber will add it's own features like games played, game specifics, AI parametised bot control. Whilst our retail offering adds in an eCommerce and Payment sections. They all add unique functionality to the underlying core.