For organizations that have made existing investments in .NET applications, or have existing .NET code libraries and business logic, that code can often be reused in iFactr applications with minimal refactoring, maximizing the return on investment in intellectual property and proprietary business processes.
See For Yourself
Build your applications in iFactr, and you’ll be a hard act to follow. Take a look at the output options that iFactr supports.
The foundation of iFactr is an abstract mobile application model that all application-specific business logic is developed within. The output for every platform target is generated from a single codebase, independent of whether the business logic is executed natively on the device or remotely on a server. As a result, the cost of supporting the application and any subsequent changes or enhancements is significantly reduced – the codebase is only updated once rather than for each platform target.
Unlike fully native platform-specific development efforts that require Objective-C/Cocoa developers for iPhone, Java developers for Android, a different flavor of Java developers for BlackBerry, C#/.NET developers for Windows Mobile, and so on, the development and on-going support of iFactr applications only requires a single profile of developer capabilities: C# and .NET.
C# and .NET is the technology stack used in the development of applications within iFactr. The framework code from server to device is standardized on the C# .NET programming language for maintainability, and is abstracted away from any app-specific business logic.
As the mobile device market continues to expand and new platforms enter the space, the iFactr framework provides organizations with the ability to “future-proof” their mobile apps. Because all UI code is held within an abstract application model, the existing UI code base can be leveraged to generate apps for new platforms as they arrive on the market.
The ability to support such a wide array of platforms derives from the iFactr strategy of utilizing an abstract UI application model, along with clean separation of business logic – automatically generating an optimal user experience for each platform according to industry best practice UI design guidelines.
Enterprise Data Client
Full Disconnected Support
Enterprise Data Server
Reflection Based API
HTML 5 Cache Manifest
The iFactr Cache and Queue manage all interactions with data services on the server. Retrieval requests are handled by the Cache, including durable persistence, resource pre-fetch, and the refresh of stale objects. Transaction requests are managed by the Queue, including connection management, requests for execution, and transaction conflict resolution.
The server is the source of truth. Any item in the cache will reflect a valid state, as available from the server at the time of the request. The client application can request a refresh, but cannot directly modify the Cache. Any new data, or changes to an item on the client is sent to the server for processing before the Cache will be refreshed with updated information.
Abstract Utility Interfaces
The iFactr Abstract Utility Interfaces give you access to all the functions you need to secure and deploy your applications, without the need to learn the details of every platform. Things like device storage, encryption, logging, network access, and analytics are all available from your shared application code. So as new devices enter the market — and your environment — your applications just work. We worry about the new platform details so you don’t have to.
Enterprise Grade Technology
With new mobile devices hitting the marketplace every day, you need a solution to manage the ever-changing list of devices entering your environment. iFactr provides the tools you need to respond to the changing landscape of corporate IT. With our Enterprise Data Client and Server, you get enterprise grade synchronization between your mobile workforce, and your data center — even when they’re offline.
Abstract Application Model
A powerful toolbox of controls to enable sharing of your business logic and data access code across platforms. You write once and deploy to whichever platforms you choose. URI-based routing and navigation brings the flexibility to support complex workflows and deployment to the native device, the web, or anywhere in between.