The AR Viewer app is available free of charge for iOS (Apple) and Android devices in the App and Play Store. The app can only be used if the device used supports augmented reality.

To use the AR Viewer, a device that supports augmented reality (or ARCore for Android devices and ARKit for Apple devices) is required. 

A list of all AR-enabled devices can be found here: https://developers.google.com/ar/discover/supported-devices

The following file formats are supported on Android: GLTF 2.0/GLB

On iOS, the following file formats are supported: USDZ, OBJ, MTL, GLTF 2.0, SCN, STL, 3DS, FBX

The following formats support textures: 

USDZ, OBJ, MTL, GLTF 2.0, SCN, 3DS, FBX, GLB, SFB

If the file format used supports textures and they are not displayed in the model in AR Viewer, pay attention to the following:

Texture file names must not contain spaces. Underscores (_) can be used instead of spaces. Umlauts (ä,ö,ü) in the name of the texture file can also cause problems and should be avoided. 

Also the MTL file, which belongs to the OBJ file, should be checked. If “Ka 1.000000 1.000000 1.000000” is specified in the materials, this can lead to problems in the display of the textures. If you delete this line, the materials will be displayed correctly and without white haze.

If you try to import a model and an error message appears, this can have several causes.

1. wrong file format: Please make sure that you use one of the file formats supported by AR Viewer. Since AR Viewer is an augmented reality tool and not a 3D model (conversion) tool (like Cinema4D or Blender), we only support the default file formats. Feel free to use your 3D tool or one of the many (free) online converters to convert.

2. faulty model file: Please make sure that your model is exported without errors. For your glb/gltf files you can use this page to see if your model was exported correctly: https://gltf-viewer.donmccurdy.com/

In this case, please check the size of your model in advance. If the model is abnormally large (e.g. meters instead of centimeters in reality), the model will be loaded and displayed in the size you specified in the 3D program. This means that you may be standing in the middle of your model and can no longer see it.

If the model is supernaturally small, you may not be able to see it at all at a greater distance from the surface.

In this case, try scaling your model. If this does not bring the desired effect, please check whether your modeled 3D model was created in correct, realistic dimensions and adjust them if necessary.

Scale:

By pulling apart or pushing together with two fingers on the display, the size of the object can be changed.

Rotate:

By rotating with two fingers on the display, the object can be rotated.

Position:

To position the object at a different place on the surface, it must be moved with one finger on the display.

In order to be able to image an object on a vertical surface, this surface must be very rich in structure for successful surface recognition. The AR Viewer is specifically designed for horizontal surface recognition.

In marker recognition, unlike normal surface recognition, the 3D model is only displayed in augmented reality when the marker is detected by the device camera. The model is permanently connected to the marker.

All images and pictures can be used as markers. It is important that the marker image is unique and high-contrast. 

Marker recognition is particularly well suited for displaying a company’s own products in augmented reality in combination with a real advertising medium (e.g. print). Product images, for example in a magazine or on a poster, can be stored as markers in the AR Viewer app and linked to the appropriate model so that (potential) customers can view the products directly in their own environment.

To test the marker detection, we have created a sample marker. If the device camera detects the marker in marker detection mode (preferably printed on a horizontal surface), the model defined for the marker appears on it.

The sample marker is available here: PDF

It is not possible to include your own markers with models in the AR Viewer. Feel free to contact us with your request – you can use the contact form or send an email to hallo@sevend.de.

It is difficult to make a general statement here. The performance of the model depends much more on the number and complexity of the materials and textures. The performance of the device used for the display in augmented reality is also decisive. 

As fist shapes, we would advise: 

Models with up to 100,000 polygons should display fine on all devices.
Models with up to 500,000 polygons should still work fine on most devices.
Models with up to 1,000,000 polygons should still work on at least the newer devices.
Models with over 1,000,000 polygons become problematic even on newer devices.

It is best to test the models directly in the AR Viewer.

After we have received your request, we start with a first detailed discussion about what you want to achieve with the app, who the app should be targeted at and clarify some basic technical details. For the conception, we usually create a common specification sheet, if necessary with first design drafts for individual areas that are needed in addition to the AR Viewer base.

Afterwards, we coordinate internally with our development department to be able to provide you with an offer for your individual app solution. 

After the approval of the offer, we start with the implementation. We regularly provide you with test versions of the app for review via the stores.

Once the app has reached the final stage, our quality assurance department tests all functions with an individual, professional test list on various devices of the supported operating systems (Android/iOS). 

After approval from both sides, the apps are then submitted to the respective store (Apple App Store/Google Play Store) for publication.

How long a project takes depends on many factors and cannot be answered in a general way. The time required depends heavily on the individual requirements of the app. If only the AR Viewer functionality with small individual color and content changes is required, we would give a rough time estimate of 1-2 months.

If additional areas/features are needed in addition to the existing AR Viewer base, this will contribute accordingly to the extension of the project time. Since these adjustments are usually very individual, the effort is also to be estimated individually.

In addition to your own app in the App and/or Play Store, we also offer you the option of using your own model directory within the AR Viewer app – the so-called directory solution.

With the directory solution, we offer you the possibility to make your own models available via the AR Viewer without developing your own app. 

For this purpose, we create a separate directory for you in the AR Viewer app (comparable to the directory of our example models). To access the directory, your target group needs the link (e.g. in the form of a QR code). We share this with you and you can share it as often as you like. If the link is called by a user in the AR Viewer, we count one call. The directory remains with the user until they manually remove it. 

Once the user has called the directory, the models stored there are available to them. If the user selects a model to view in augmented reality in his own environment, we count one model call. If the user looks at the model again at a later time by selecting it again in the directory, another model call is counted. 

Interested in having your own directory in the AR Viewer app? – Great! We are looking forward to your request! Based on the number of directory and model calls, we have put together different pricing models. So we can find the perfect plan for every project!