Topic / Question

Installation
Is your software is a standard SAINT add-on?
Is your add-on certified for Business Suite and S/4HANA? Which versions / releases?
Design Time / Tooling
Is your development environment completely implemented in ABAP? Integrated into the ABAP workbench?
Do you offer a web-based IDE in additon?
Can you think of a potential integration into the SAP WebIDE in future?
Do you use the SAP TMS to transport a Neptune application?
Do you have an own (logical) transport object or do you use a standard tranport object of SAP?
How many and which development artefacts does a Neptune application have?
How do you ensure locking of the development artefacts?
Is collaborative development of multiple developers possible within one project? How is this achieved?
Design Time / Modeling and Implementation
Do you leverage the UI5 resources stored / installed with the ABAP platform?
Do you define your UI WYSIWYG and with drag and drop?
You can bind the UI data model either to an OData service or to a data provider (DP) class data?
Properties of the data model are taken from the OData property data types in the OData use case?
Properties of the data model are taken from the ABAP and DDic data types in the DP use case?
UI breakouts can be done via java script?
There is no further implementation support in the DP use case (e.g. mapping to a database table etc.)?
Is internationalization (translation of all end-user texts, ltr, ...) supported?
Can you package the application as native device app?
Runtime / Protocol
In the OData use case you use the standard infrastructure (SAP Gateway)?
In the DP use case you use an own optimized JSON-protocol with an own ICF-handler (end point)?
In the OData use case with SAP Gateway you support all the protocol qualities of SAP Gateway?
In the DP use case what functional qualities and capabilities do you support?
Examples: filtering, sorting, grouping, paging, feature control, transactional capabilities, value helps, …
In the DP use case what security qualities and capabilities do you support?
Examples: security session, cross-site requests forgery, read access logging, start authoritzation, …
What extensibility qualities and capabilities do you support for industries, partners, customers?
Examples: extension of fields, entities, actions, …
In the DP use case do you store additional runtime metadata (in the persistence or shared memory)?
If yes, how do you manage the lifecycle, i.e. invalidation of caches.
Do you support stateful consumption for both use cases, OData and DP?
As you offer two options, what disadvantages do you see or OData compared to your JSON-approach?
Can you name concrete disadvantages and are those of general purpose or is it about effort to get both on the same level?
As you offer stateful and stateless (default), what disadvantages do you see for the stateful approach?
Runtime / UI
Do you render the UI in the backend? For both use cases, OData and DP?
Where do you get the UI resources during runtime?
What works out of the box and where are breakouts needed?
Assumption: breakout are implemented with JavaScript.
Can apps built with Neptune also be integrated into the SAP Fiori Launchpad?
Do you support intent-based navigation?
Do you also support offline scenarios? For both use cases, OData and DP?
Do you support also stateful consumption? How is this reflected in the UI?
Can I define a multip-step UI (e.g. a guided activity) with backend interaction after each step?
Is "stateful" supported in combination with offline?
When launching various apps you keep them open in your launchpad and you keep the UI state.
Does this also work with stateful applications? How do you handle timeouts, locking, etc.?
What kind of flexibility, e.g. personalization etc. do you support for the end user?
Runtime / Backend
In the DP use case, what is the contract that the DP classes have to fulfill?
Especially how is the interaction /orchestration in stateful scenario?
Do you leverage / support stateful also for the OData binding?
What is the runtime (ms) of your backend infrastructure in the DP use case?
In the DP use case, what works out of the box and where are breakouts needed? Example: Sorting, Filtering, etc.
Assumption: breakout are implemented with ABAP.
Do you support optimistic concurrency control (e.g. eTag handling) for the DP use case? If yes, how is this achieved?
Do you support exclusive locking in a stateless applications? If yes, how is this achieved?
How do you handle session timeouts, especially for stateless applications if you handle a certain state (e.g. locks)?