StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11646631
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-07-25T09:25:41.897
FavoriteCount
0
LastActivityDate
2012-07-25T09:25:41.897
LastEditDate
LastEditorUserId
0
OwnerUserId
1500959
ParentId
11646509
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
There are two approaches you could take which spring to mind; <ol> <li>Encrypt the information You could implement a system (which, as you say, QRDroid does, along with many other such apps) whereby you use the following process; 1 take the information you want to put into your QR, 2 encrypt that information using a standard protocol (Wikipedia can help you get started here if you're completely in the dark about such things) - this can be password protected, or by some other means. Depends partly on the level of secrecy you want here... 3 encode the new encrypted information into a QR code. At the other end, the app reads the QR code, then decrypts it and voila.</li> <li>Develop a different QR-style protocol? This is clearly much more ambitious, and wouldn't necessarily provide any theoretical security (unless you implemented part 1 somehow as well). It would, however, result in a code which was unreadable by other standard apps, since they wouldn't know how to interpret the pattern they were seeing. That said, a lot of careful thought went into developing QR as a useful approach, so this would be an exercise I'd suggest considering only for the techy joy of taking it on :D</li> </ol> Going back to point 1, if you want your app only to be able to read things, but not have to have a user enter a password or anything, you could use a single fixed 'password' that the app knew (perhaps even hard-coded in, at it's most basic). It would use this automatically to encrypt and decrypt at each end. This would obviously represent a massive security flaw under close scrutiny, but if you just want something that'll keep your info reasonably secret from other QR apps currently available, this would do the job. In this case, you'd really just be encoding your information rather than encrypting, I suppose, but in a way that other apps don't know how to *de*code as standard.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGenerating QR code which can be read only by my app
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USunwitting
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.