Skip to main content

Android OS Redesigned

Imagine the following scenario - you are looking for an application (app) on the Google Store, but the application that you found does 3 or 4 other things that you are not really interested in.   Perhaps it is a photo editor that also syncs with Dropbox, has an online gallery, etc.  All you want is local photo editing.  Today, there is nothing you can do unless the app uses Android 6.0 run-time permissions, but if you had more fine-grained permission control, you could deny or just limit access to those extraneous permissions like web access.

I previously wrote about a solution to many of the problems associated with the Android operating system.  For the rest of this article, I will pretend that the Android community has adopted these design ideas.

A trustworthy OS would give the user full control over each app's ability to run in the background, upload and download data over various connections (mobile, public network, private "home" network), etc.  Before installation, the user would be prompted (as usual) but for each permission there would be a drop-down list of choices - allow full access, prompt every time, deny access, limited access, custom access, or simulated access.

Let us examine the permission "access your contacts".  If the app only needs to confirm your identity, give it "limited access - just me", or a custom list of your work and home contact entries.  If this app had a social media aspect, you could still use it with confidence knowing that they would not be stealing your entire contact list and sending it to their servers.

If this was well implemented, it would not eliminate rogue apps, but would allow the user to de-fang the app by both preventing access, and preventing communication, and even if they tunneled some information out, it could be simulated data.

What does this mean to users? No more ring-tone apps that steal every file, call history, and contacts.  
The next obvious step would be for some trusted authority to provide a list of recommended permissions to grant an app.

This would require Ad-ware apps to redesign themselves to use an official "Advertisement" channel so they could still remain profitable.  Google would be responsible for shutting down abuses like using the advertisement channel to steal data.

Comments

Popular posts from this blog

Updated ActiveRecord Code Generator

Today, I updated the ActiveRecord Code Generator a bit. I checked in changes to use primary and foreign key details from INFORMATION_SCHEMA. The original code used naming conventions to decide what various fields were used for - ID = Primary Key, Field_ID = Foreign Key to table Fields. If you want to use naming conventions, let me know and I can add a setting in App.Config to allow this (along with any "real" key constraints).

How does Rails scaffolding select HTML input tags?

Recently, a reader saw my fix for SQL Server booleans, and asked me a followup question: why does Rails display a yes/no selection instead of a checkbox? The short answer is look in {RUBY_HOME} /lib/ruby/gems/1.8 /gems/actionpack-1.10.2 /lib/action_view/helpers, but your path may vary depending on whether you are using gem, "edge rails", etc. Anyway, look in the file "active_record_helper.rb" for a method called "all_input_tags", and notice that it calls "default_input_block" if you don't supply an input_block. Now notice that "default_input_block" creates a label and calls "input(record, column.name)" which in turn calls "InstanceTag#to_tag" which finally looks at the datatype and maps boolean to a select tag. Perhaps a wiser Rails explorer can provide us with the rationale for this, but I guess we could add a MixIn for InstanceTag that redefines the to_tag() method, or just do a dirty and unmaintainable hack l...

Features of the Code Generator

I just updated my code generator to optionally generate validation attributes. This simple change includes App.config file entries for all check boxes, and a new checkbox for "Validation" - aka validation attibute generation. While I was making this change, I realized that I really need to pass a CodeGenerationContext object to the DbTable, DbField and ModelGenerator classes. The requester can populate the context, and pass it to the code generator. Anyway, enough about the code, let's talk about the templates. I made a simple template this weekend to generate a DataGridView column array, suitable for databinding. I'm sure my new template will need some tweaks to handle Foreign Keys better (it currently just displays them as TextBox). Let's look at a template. ##FILENAME:PR_${table.GetClassName()}_Insert.sql ## ## Generate a SQL stored procedure to insert a record into the ## specified table and return the newly created primary key ## ## FUTURE: The generat...