Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This development and the published app is based on extremely old iOS functionality. #1

Open
abetancort opened this issue Feb 9, 2018 · 0 comments

Comments

@abetancort
Copy link

abetancort commented Feb 9, 2018

Most iOS users no longer use iTunes for anything, and many don’t even have a computer, because it has already passed a few years since iTunes became a redundant to do anything with an iOS device. But your app hasn’t been updated to conform to the new standards and does not support the iOS share sheet which at least during the past 2 years has been Apple recommended and preferred iOS method to share structured data (files/archives or other) between Apps, in this case certificates. But your App only implements the outdated method of going through iTunes, forcing the user to use an external App, iTunes, running on a Computer to implement just part of the functionality included by iOS share sheet. Forcing the users of your App to get a hold of a Computer that is not actually needed in iOS for anything else each time they need to import/load their certificates to your App.

For most people (casual to medium users), if they have an iPad that supports iOS 11 or above, they won’t need to own or use a computer (as long as they don’t need use eGovernment/eAdministration in Spain that requires the use of this Apps that unnecessary requires a computer).

I believe it’s time for an overhaul of all the iOS apps related to autofirma or @firma to set them at par with the rest of the 2018 iOS Apps with regards to accessibility, usability, functionality and support of the iOS platform standards.

An outdated App, one which does not meet the current usability standards, becomes a barrier for the expansion and widespread use by the general population of what the resources of what is commonly known eGovernment or eAdministration in their interactions with the Administration(s).

The issue of not addressing mobile platforms correctly because there are no Apps available when they are required to by the backends of the eGovernment platform or the ones available do not meet the expectations set by the mobile platform to its average user has already been recognized as one of the major barrier to the widespread adoption of the eGovernment by the citizens in their interaction with the administration. The main reason cited is the near universal penetration of smartphones and tablets with Internet and the much lower penetration of computers connected to Internet.

The importance of issue mentioned in the previous paragraph has been acknowledged by the EU on many of the its recommendations regarding how the member States should proceed in advancing towards the goals and complying with the mandates set by the Directives of the Council and the Parliament of the EU regarding this matter.

luis-abamobile added a commit that referenced this issue Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant