- /
- /
- /
PILOT BETA LAUNCH
XOM: PILOT BETA LAUNCH
Today we start integrating core components into the eXperience Over Media application.
TEST FLIGHT BUILD
V1.0.0 (10)
SIGN-UP HERE https://live.xom.app/beta
IPAS INTEGRATION Immersive Product Anchor System.
PAYMENT GATEWAY Access product data from cloud resources.
MOBILE MAPPING Customizable location interactables.
SECTION ONE: XOM DEVELOPMENT
USER AUTHENTICATION – signup/signin – save profile preferences.
We currently leverage Google Firebase for user onboarding which creates access to
realtime database entries along with different options for signing up/in into various
applications and web resources. With that being said we’re continually looking into
alternative options within AWS, Oracle, and other third party cloud integration. The
goal is to have a streamlined system that can work across web frameworks and
native applications as one (cross-platform) solution. Accessible data storage and
manageable entries will be saved via a cloud resource and secondary backup.
PRODUCT API INTEGRATION – access product data cloud resources.
Last year we shared with peers our endeavors to further pursue some of the many
aspects of immersive automation and user experiences that can be made through
game engines and newly defined hardware. In this time we developed a scripting
system that finds and congregates product data within a 3D runtime environment
allowing developers and customers to interact with them in a new way. We use a
number of AWS components to funnel the information into our own environment.
The goal is to have this flow nicely as a part of authentication and overall
methodology in our Implementation.
MAPS API INTEGRATION – location information for real-time delivery.
We also leverage key mapping tools that allows for our XOM application to propagate
digital products at defined geo coordinates using GCP Directions and Places API as a
driving source. This enables the ability for us to congregate millions of set points of
interest based on venue categories along with mapping routes for potential
autonomous delivery routes. As with the product api integration, using an existing
authentication or alternative solution for bringing it all together is key.
INVENTORY MANAGEMENT – a place where an item originates.
This part of implementation in the Immersive automation process is a lot to think
about. Ultimately it would be nice to tap into an existing partnership who are
contenders in the fields that have regional and global distribution fundamentals in
place. Their purpose in partnering would be to hold potential inventory for its digital
counterpart within the shopping environments we create. A future use case could
be attached to a fully integrated supply chain process that facilitates all the
packaging and deployment requirements. This can be an autonomous warehouse or
facility connected to storefronts acting as a distribution location.
ITEM DISTRIBUTION – how customers will receive a product.
The final stage of our Immersive Automation strategy is to tap into new and existing
drones, rovers, and autonomous options currently available on the market. We
personally have built dozens of UAVs over the years and understand the underlying
principles being rovers and other unmanned vehicles. They use similar controllers
and components for navigation and programming. Perhaps down the road it would
be entertaining to design a customized delivery system like something Elon would
pull at Tesla but in the meantime we’re relying on key partnerships to help jump
start a pilot program that can be easily scalable.
ENTERPRISE RESOURCE PLANNING – development stage to solution.
To bring all the aspects of our SaaS enterprise experience together we are working to
adopt and use Oracle’s NetSuite in mitigating all forms of the application concept.
Where processes and steps of growth have already been documented we can follow
guidance and knowledge from others in helping everything play out. The challenges
really stem around not knowing where to continue in development, operational cost,
and overall competitive edge in deploying a new software strategy solution to the
market. Depending on the scope and scale of initial traction and regional growth we
will inspect each milestone to be reached by underlining fundamental goals that are
achieved through each stage.
SECTION TWO: COMPANY GROWTH
XOM EXECUTIVE TEAM – starting leadership roles for eXperience Over Media.
Our immediate needs focus around additional development knowledge and
leadership for scaling the implementation of our Immersive Automation Process.
The two immediate counterparts that come to mind are a solid technology officer to
help lay out the development infrastructure across cloud and mobile resources. On
the flip side with all the facets of our application process being made readily
available, an operational manager to help facilitate the different tasks with ongoing
strategy is crucial. These two leadership roles will help define and articulate the
further growth tactics and team members needed to thrive.
XOM – Active Job Positions
FULL STACK DEVELOPMENT – outsourcing an expert engineering team.
We are in the process of gathering a wide array of developer help. This entails
everything from cloud architecture to mobile implementation of AWS and Google
Maps resources. Listed below are a few common programming languages we are
working with and the challenges we aim to overcome with the right talent involved.
Our development team will work across a web framework and native mobile
environments and will have a core understanding when it comes to user onboarding
and the technicalities of load balancing and scaling of operations to keep a fully
functioning platform.
XOM – Technology Stack
BUSINESS PARTNERSHIPS – strategic outsourcing experts in their field.
The immersive automation process has a lot of steps and procedural hand offs along
the way. We plan to work with industry experts and professionals to regulate set
standards needed in moving the project forward. This can include everything from
hardware solutions such as custom carrier drones and rovers to delivery logistics and
merchant distribution in regions. If done correctly it creates hundreds of new
opportunities for those looking to get involved in the immersive webfront in many
different industries involved. .
XOM – Strategic Partnerships
WORLDWIDE BETA GROUPS – quality assurance advocates in their city.
To start testing some of the working components we’re rolling out regional beta
testers to further improve upon the experience across the overall process. See the
linked page on upcoming and future cities that will help launch future use cases of
our application. As partnerships and regions get mapped from satisfactory client
acquisitions and demand we will expand upon additional possible deployment
locations if need be.
XOM – Beta Testing Cities
SECTION THREE: UPCOMING FEATURES
SOCIAL STREAM – sharing real world experiences on social media.
As a part of the application experience, users will be able to share on location anchor
drops with the surrounding area to showcase real world experiences that can take
place. As we continue developing different IPAS integration and storefront layouts
and use cases it will play upon the types of things people can engage in and
ultimately deploy wherever one chooses. The purpose of this feature is to showcase
uniquely placed and defined location engagement to further excite additional
transactions and user interest.
IMMERSIVE ASSISTANT – helping to find what you’re looking for in XOM.
We use a number of different technologies for a one of a kind user experience.
Included in the environments will be a machine learning chatbot that helps intrigue
specific interests for items within the shopping environments. It can recommend
like minded media and content or give alternatives options to help send users down
the right path. All XOM data collection gives users transparency and full access to
what we store and save to better serve you.
LIVE BROADCAST -promote your storefront in the digital forefront.
As with any hardware and networking technology we continually improve upon
capture tools and devices to share the best of ourselves within these worlds. Using
multiple depth cameras and rigs we integrate a holographic broadcast feature that
will act as a personal host or guide when engaging in specific environmental areas.
It’s up to the account holder to see what they can do with the new capture method.
This newly integrated feature and platform component will also encompass the new
DFX web framework as an alternative to the mobile application with hopefully a
crossed managed sign in feature to share from multiple devices.
SECTION FOUR: FINAL THOUGHTS
PARTNER ENGAGEMENT – distributing facilitative processes.
With everything laid out, we’re looking to onboard an executive team, array of developers
and managers to help facilitate the different areas of operations and hopefully bring new
opportunities for our business and partners we establish along the way. I’ve started
sharing the business strategy and core initiatives with investors and our close peers. We
are currently looking for the right time to get new parties involved and hand off some of
the challenges we face in the process.
MILESTONE TIMELINES – next steps to achieving our goals.
Within the application development timeline we have outlined key goals to reach
within the development and overall process. Deployment and integration is subject
to change as integrated platform functionalities evolve. In addition the scale factors
of user engagement will determine a time scope on when to scale and onboard the
next phases of the integration process. Conceptualized deployment strategies will
further dictate operational cost and turnarounds.
USAGE ACTIVITY – goals for an official application launch.
We know the overall process of onboarding users worldwide will take time and effort to
mitigate the risk of competitive landscapes and interest as experiences and engagement
gets improved upon overtime. We have a goal of 100,000 users for the beta worldwide to
be reached to officially launch a product at full scale. On top of the numbers we want to
expand upon distribution locations when we feel there is a solid userbase to help define
the need and interests with the new application experience.