Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
|||||||||||||||
Photo/Image Count: 15
|
|||||||||||||||
|
|||||||||||||||
|
Notes:
|
Meeting with Jonathan to go over some progress. We haven't met in a few weeks due to holidays and what not. The meeting went well. Jonathan and I were on the whole meeting. Steve joined us in the middle for a part of it. Here are a few of the things that we did and covered: - Review of the education mode - see the screenshots. The education mode allows a user to turn on/off additional helps, tips, help files, verbiage, videos, graphics, etc. The user can turn things on/off to keep the interface more clean and streamlined. If they need more help, it is available at the touch of a button. Side note, added this link to a small video on the education mode on 8/14/23. - Review of the invoice interface with some fake data. Jonathan is working on showing mock-up data and how it may look and flow, as the user interacts with the system. - Talking about style guides and standards - design systems - This is how we will end up standardizing the look and feel over multiple pages, components, reports, and features. - Components and using consistent assets (visual and code resources). Both in the design and in the code - design/code once, use many. - Talking about mobile development and more needs for mobile ready pages. - We also talked about the placement of certain eye candy pieces such as graphs, charts, and other stats. Leaning towards the reports pages and/or section. - We briefly talked about Jonathan's research on fracture and breaking up the system into smaller pieces. Being able to have the mountain of tools and options (features and benefits - current adilas system) but only showing what is needed (turned on/off and properly configured) and streamlined per industry and per company within that industry (making custom software easy). Basically, the ice-burg model. As we got into this, we ended up talking about the core product (the main adilas platform) and how we could allow for industry specific interfaces and settings to play over the top of the skeletal type model. - The skeletal type model deals with the underlying systems... imagine a person with just a skeleton structure. You could then put normal clothes on that skeleton structure. Pretend this is core adilas (plain jane vanilla). Then you could dress that person with industry specific clothing to get all types of different outputs. Every industry has a different look and feel, verbiage, style, flow, etc. That is like putting on specific clothing on the skeletal system. - Towards the end, Jonathan and I were talking about the shopping cart and how that part of the system really needs some loving. So many pieces converge on the shopping cart and point of sale interface (POS). It is pretty awesome. Here is a small help file on the shopping cart - click here. We talked about some of the known pieces that converge inside of the cart such as smart cart logic, customer loyalty points, tiered pricing structures, discounts and discount engine stuff, inventory tracking, sub inventory, mini conversions, labeling, coupons, payment solutions, sales and promotions, etc. Once it hits the cart, it gets put into the database and starts its life cycle. We talked about how the shopping cart and things that flow into it and out of it are kinda like the heart of the application. |